CVE-2026-99658
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 ]
Properties
- Last source
- FIRST EPSS
- Nvd fetched at
- 2026-11-22T12:30:49.958423+00:00
- Epss score
- 0.00168
- Cve id
- CVE-2026-99658
- First seen by Signal
- 2026-11-20T07:38:10+00:00
- Name
- CVE-2026-99658
- Retrieved at
- 2026-11-22T12:32:29+00:00
- Published at
- 2026-11-20T06:17:59.807
- Last modified
- 2026-11-20T06:17:59.807
- Epss percentile
- 0.06238
Related research
Explore deeper with Ninja Signal's threat intelligence graph