System-wide write throttling via NFS over-accounting
Published Aug 15, 2026 · Updated Aug 15, 2026
Improper writeback accounting in the Linux NFS client allows local users to force system-wide buffered-write throttling. The nfs_folio_mark_unstable() and nfs_folio_clear_commit() functions charge the full folio page count for every sub-folio request instead of only the pages that request covers. NFS writes that split a large folio into multiple requests can inflate dirty and writeback counters until all buffered writers on the host enter the hard-throttle path, interrupting write service without corrupting data.
Summary
What happened
Improper writeback accounting in the Linux NFS client allows local users to force system-wide buffered-write throttling. The nfs_folio_mark_unstable() and nfs_folio_clear_commit() functions charge the full folio page count for every sub-folio request instead of only the pages that request covers. NFS writes that split a large folio into multiple requests can inflate dirty and writeback counters until all buffered writers on the host enter the hard-throttle path, interrupting write service without corrupting data.
The record
- CVE
- CVE-2026-72132
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-911, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0c493b5cf16e28d761b6e77c7c32aa0e7af70813 <0ffc032294a29601b1019dba91aa1a930d90df17
- Affected versionversion=0c493b5cf16e28d761b6e77c7c32aa0e7af70813 <1f646e23372f3444dc5f0bcb5404a49d26756add
- Affected versionversion=0c493b5cf16e28d761b6e77c7c32aa0e7af70813 <27934d02cbeb8a957dd11c985a579e58d30c5270
- Affected versionversion=0c493b5cf16e28d761b6e77c7c32aa0e7af70813 <a192b6c149c6ea10cc88869accb78165eb454456
- Affected versionversion=0c493b5cf16e28d761b6e77c7c32aa0e7af70813 <a442c258320b689f13d2205eaeeddf8b0e630288
- Affected versionversion=6.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo