CVE-2026-99704: mm/page-writeback: avoid 32-bit overflow in dirty threshold shares

Published Nov 20, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

mm/page-writeback: avoid 32-bit overflow in dirty threshold shares

The ratios used by wbcalcthresh() are scaled to parts per million, but the threshold and ratio operands are unsigned long. On 32-bit kernels, their multiplication can wrap before the result is assigned to u64.

For example, with a threshold of 25600 pages and the default maximum ratio of 1000000, wbmaxthresh becomes 4125 pages instead of 25600. The shared threshold and minimum share calculations can overflow in the same way, producing incorrect per-writeback dirty limits.

Use a u64 threshold for the three ratio multiplications and divu64() to retain the existing division order and rounding.

Affected Software

6 affected componentsFixes available
linux/kernel>=6.2.0<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5
debian/linux*
debian/linux*
debian/linux<=6.12.107-1, <=6.12.117-1, <=7.3.4-1
6.1.176-16.1.192-27.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  4. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.192-2Fixed in 7.3.5-1

Event History

Nov 20, 2026
CVE Published
via MITRE·05:50 AM
Data Sourced
via MITRE·05:50 AM
Description
Data Sourced
via OSV·05:50 AM
DescriptionAffected Software
Data Sourced
via NVD·06:18 AM
Description

Frequently Asked Questions

1

Which systems are affected by the overflow?

The overflow affects 32-bit Linux kernels, where unsigned long operands can wrap during dirty-threshold ratio calculations. The described example uses the default maximum ratio of 1000000.

2

What is the practical effect of the issue?

The kernel can calculate incorrect per-writeback dirty limits. In the provided example, a 25600-page threshold produces a wb_max_thresh of 4125 pages rather than 25600 pages; shared-threshold and minimum-share calculations can also be wrong.

3

Is a non-default configuration required to trigger the problem?

No. The description demonstrates the overflow with the default maximum ratio of 1000000 on a 32-bit kernel.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203