Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-72132NFS: Charge unstable writes by request size, not folio size

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

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 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)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 0c493b5cf16e28d761b6e77c7c32aa0e7af70813 – < a442c258320b689f13d2205eaeeddf8b0e630288
    • affected 0c493b5cf16e28d761b6e77c7c32aa0e7af70813 – < 1f646e23372f3444dc5f0bcb5404a49d26756add
    • affected 0c493b5cf16e28d761b6e77c7c32aa0e7af70813 – < 0ffc032294a29601b1019dba91aa1a930d90df17
    • affected 0c493b5cf16e28d761b6e77c7c32aa0e7af70813 – < a192b6c149c6ea10cc88869accb78165eb454456
    • affected 0c493b5cf16e28d761b6e77c7c32aa0e7af70813 – < 27934d02cbeb8a957dd11c985a579e58d30c5270
  • Linux · Linux

    • 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

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-72132 badge
[![CVE-2026-72132](https://cveledger.app/badge/CVE-2026-72132.svg)](https://cveledger.app/cve/CVE-2026-72132)

Record last updated .