CVE-2026-99658: Linux kernel · mm/mmu_notifier: finish non-blocking interval invalidation on error
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 00936003341fdb8c526652a9b84f99124616efb9 : update Linux kernel when convenient.
Data as of 20 Nov 2026, 06:04 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 00936003341fdb8c526652a9b84f99124616efb9, 9439da3fa1ac9a7bdc4a2d3729a5bd0c2660c1b9, 6d65925777ecae9d7a571a327e41c63f3940a0c7 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade Linux kernel to 00936003341fdb8c526652a9b84f99124616efb9, 9439da3fa1ac9a7bdc4a2d3729a5bd0c2660c1b9, 6d65925777ecae9d7a571a327e41c63f3940a0c7 or 01ce779d7e598aafd3a02059d100ce66c909bea2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: mm/mmu_notifier: finish non-blocking interval invalidation on error When an ordinary MMU notifier rejects a non-blocking invalidation, the interval invalidation started beforehand is left unfinished: the caller skips mmu_notifier_invalidate_range_end(). Subsequent interval notifier operations can then wait forever. The only in-tree trigger is nouveau SVM, which uses both notifier types and rejects non-blocking invalidations. Reaping via the OOM reaper or process_mrelease() can therefore leave the GPU fault worker stuck, holding a reference that prevents the dying process's address space and memory from being freed. End the interval invalidation when an ordinary notifier fails a non-blocking invalidation, like mn_itree_invalidate() already does when an interval notifier fails. Make that handling clearer in the documentation of mmu_notifier_invalidate_range_start_nonblock(). Fix generated by an LLM and sent by Josef Bacik in private. [ david: simplify description, update function doc ]
References
- git.kernel.org/stable/c/01ce779d7e598aafd3a02059d100ce66c909bea2 (opens in a new tab)
- git.kernel.org/stable/c/00936003341fdb8c526652a9b84f99124616efb9 (opens in a new tab)
- git.kernel.org/stable/c/9439da3fa1ac9a7bdc4a2d3729a5bd0c2660c1b9 (opens in a new tab)
- git.kernel.org/stable/c/6d65925777ecae9d7a571a327e41c63f3940a0c7 (opens in a new tab)