CVE-2026-99740
What it is
In the Linux kernel, the following vulnerability has been resolved: mm/shmem: stop retrying folios that cannot be split A fault or collapse can insert a large folio crossing EOF after shmem_undo_range() has handled the boundary folios. If splitting that folio fails, truncate_inode_partial_folio() retains it when it is dirty. The final scan then repeatedly finds it because it restarts from an unchanged start. Truncation keeps the inode lock and ignores fatal signals while looping. A concurrent unlink() can then block other directory operations while holding the directory lock and waiting for the file's lock. Advance start past the retained folio, whose truncated part has already been zeroed. Do not move start backwards if the failed split has shrunk the folio. Fix generated by an LLM and sent by Chris Mason in private. [ david: split fixes, simplify descriptions, adjust comments ]
At a glance
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: not scored yet.
- Severity: not scored yet.
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Record status
- Received
Affected
- Linux < dfedff4a9f0abcd985dcdfbd721dcd9374d6ff12
- Linux < 1360e0f9a188cfede01d0df81119d925bbfff165
- Linux < b3239a5a37bba078d83cfb864d47a0cc122f17cd
- Linux < a842a1f947da8a7020e72f885ffbf2ce6a93685f
- Linux da9b7c651c6517c2de1099136ed87c0c24f864dd
- Linux 7a4ae7acd20805940307be98b304871a43288a01
- Linux < 6.2
- Linux < 6.7
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-99740.md and follow it. Check whether this project is affected by CVE-2026-99740. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.