Bug 2577791 (CVE-2026-99658) - CVE-2026-99658 kernel: kernel: Denial of Service via incomplete MMU notifier invalidation on error
Summary: CVE-2026-99658 kernel: kernel: Denial of Service via incomplete MMU notifier ...
Keywords:
Status: NEW
Alias: CVE-2026-99658
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-20 06:14 UTC by OSIDB Bzimport
Modified: 2026-11-20 11:12 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-11-20 06:14:03 UTC
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 ]


Note You need to log in before you can comment on or make changes to this bug.