{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72132 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72132 is a denial of service vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-72132 and fix it if it is affected.\n\nWhat it is: CVE-2026-72132 is a denial of service vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-72132 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-72132/ (Markdown: https://insights.sbomify.com/CVE-2026-72132/index.md)","id":"CVE-2026-72132","markdown":"https://insights.sbomify.com/CVE-2026-72132/index.md","name":"CVE-2026-72132","record":{"aliases":["BELL-CVE-2026-72132","DEBIAN-CVE-2026-72132","GHSA-hmp9-jxmh-jfh2","UBUNTU-CVE-2026-72132"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Linux kernel NFS","requires_auth":"none","summary":"A Linux kernel NFS accounting bug allows remote attackers to cause system-wide denial of service by inflating writeback metrics via split requests.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nNFS: Charge unstable writes by request size, not folio size\n\nnfs_folio_mark_unstable() and nfs_folio_clear_commit() charge and\nuncharge NR_WRITEBACK/WB_WRITEBACK by folio_nr_pages(folio) once per\n*request* added to or removed from a commit list. This is correct only\nwhen a folio has a single associated request. When pg_test splits a\nfolio into N sub-folio requests (e.g. pNFS flexfiles striping with a\nstripe unit smaller than the folio size, or plain wsize-limited\nsplitting), each of the N requests independently charges the whole\nfolio's page count, inflating the accounting by a factor of N per\nfolio. With large folios and small stripe units this reaches multiple\norders of magnitude: a 2 MiB folio split into 512 4 KiB requests can\ncharge up to 512x its real size, pushing global dirty+writeback\naccounting past the system's dirty threshold and forcing every\nbuffered writer on the host into the hard-throttle path, including\nunrelated in-kernel NFS server threads sharing the box.\n\nCharge each request only for the pages it actually covers.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"NFS: Charge unstable writes by request size, not folio size","id":"CVE-2026-72132","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"spi: uniphier: Fix completion initialization order before devm_request_irq()","id":"CVE-2026-72133"},"packages":[],"prev":{"headline":"nvme-apple: Prevent shared tags across queues on Apple A11","id":"CVE-2026-72131"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A Linux kernel NFS accounting bug allows remote attackers to cause system-wide denial of service by inflating writeback metrics via split requests.","url":"https://insights.sbomify.com/CVE-2026-72132/"}