CVE-2026-99737
What it is
In the Linux kernel, the following vulnerability has been resolved: mm/shmem: fix truncate loop after boundary swapin failure If swapping in a large entry at the new EOF fails, shmem_undo_range() leaves the entry in place. Its final scan skips the entry, then restarts from the same start index and finds it again. Truncation can loop forever while holding i_rwsem. Advance start past the skipped entry so that a restarted scan can finish, as we already do for folios that cannot be split. Note that this does not fix the missing zeroing when boundary swapin fails, it merely prevents the endless loop.
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 < 7f1bbb9c6a8ed3fed72bf7efc906ebe31e92feeb
- Linux < d4d46430852caf5e7dbca1386fc6621ecf8fe2b0
- Linux < e6e9ba49679e5f33f62615fb57ec103045fbc8f9
- Linux < 5f1ec2cf92a7d655a8eb39711987822f9b1f9d67
- Linux < 6.12.118
- Linux < 6.18.64
- Linux 6.19
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-99737.md and follow it. Check whether this project is affected by CVE-2026-99737. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.