CVE-2026-72132NFS: Charge unstable writes by request size, not folio size
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: NFS: Charge unstable writes by request size, not folio size nfs_folio_mark_unstable() and nfs_folio_clear_commit() charge and uncharge NR_WRITEBACK/WB_WRITEBACK by folio_nr_pages(folio) once per *request* added to or removed from a commit list. This is correct only when a folio has a single associated request. When pg_test splits a folio into N sub-folio requests (e.g. pNFS flexfiles striping with a stripe unit smaller than the folio size, or plain wsize-limited splitting), each of the N requests independently charges the whole folio's page count, inflating the accounting by a factor of N per folio. With large folios and small stripe units this reaches multiple orders of magnitude: a 2 MiB folio split into 512 4 KiB requests can charge up to 512x its real size, pushing global dirty+writeback accounting past the system's dirty threshold and forcing every buffered writer on the host into the hard-throttle path, including unrelated in-kernel NFS server threads sharing the box. Charge each request only for the pages it actually covers.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 2 days later
· 2 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 0c493b5cf16e28d761b6e77c7c32aa0e7af70813 – < a442c258320b689f13d2205eaeeddf8b0e630288
- affected 0c493b5cf16e28d761b6e77c7c32aa0e7af70813 – < 1f646e23372f3444dc5f0bcb5404a49d26756add
- affected 0c493b5cf16e28d761b6e77c7c32aa0e7af70813 – < 0ffc032294a29601b1019dba91aa1a930d90df17
- affected 0c493b5cf16e28d761b6e77c7c32aa0e7af70813 – < a192b6c149c6ea10cc88869accb78165eb454456
- affected 0c493b5cf16e28d761b6e77c7c32aa0e7af70813 – < 27934d02cbeb8a957dd11c985a579e58d30c5270
- affected 6.3
- unaffected < 6.3
- unaffected 6.6.148 – ≤ 6.6.*
- unaffected 6.12.97 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References5
- https://git.kernel.org/stable/c/a442c258320b689f13d2205eaeeddf8b0e630288 (opens in a new tab)
- https://git.kernel.org/stable/c/1f646e23372f3444dc5f0bcb5404a49d26756add (opens in a new tab)
- https://git.kernel.org/stable/c/0ffc032294a29601b1019dba91aa1a930d90df17 (opens in a new tab)
- https://git.kernel.org/stable/c/a192b6c149c6ea10cc88869accb78165eb454456 (opens in a new tab)
- https://git.kernel.org/stable/c/27934d02cbeb8a957dd11c985a579e58d30c5270 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-58890 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-72132)Record last updated .