CVE-2026-99657: mm/mmu_notifier: set ->mm only after mmgrab()

Published Nov 20, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

mm/mmunotifier: set ->mm only after mmgrab()

Radeon uses a non-NULL notifier->mm to decide whether to call mmuintervalnotifierremove() when freeing a buffer object. mmuintervalnotifierinsert() sets ->mm before validating the range, so a wrapping userptr range can leave ->mm set after insertion fails. Cleanup then tries to remove an unregistered notifier for which no mm reference was acquired.

Set ->mm only after mmgrab(), once insertion can no longer fail. While we could fix radeon's code instead, setting ->mm on success only makes the code more robust.

Fix generated by an LLM and sent by Chris Mason in private.

[ david: simplify description ]

Affected Software

7 affected componentsFixes available
linux/kernel>=5.5.0<6.12.118
6.12.118
linux/kernel>=6.13.0<6.18.64
6.18.64
linux/kernel>=6.19.0<7.3.5
7.3.5
debian/linux*
debian/linux*
debian/linux*
debian/linux<=6.1.176-1, <=6.1.192-2, <=6.12.107-1, <=6.12.117-1, <=7.3.4-1
7.3.5-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.118
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.64
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.5
  4. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 7.3.5-1
  5. Compensating control

    In __mmu_interval_notifier_insert(), set ->mm only after mmgrab(), once insertion can no longer fail.

Event History

Nov 20, 2026
CVE Published
via MITRE·05:50 AM
Data Sourced
via MITRE·05:50 AM
Description
Data Sourced
via OSV·05:50 AM
DescriptionAffected Software
Data Sourced
via NVD·06:17 AM
Description

Frequently Asked Questions

1

What condition triggers the faulty cleanup path?

A wrapping userptr range causes __mmu_interval_notifier_insert() to fail after notifier->mm has been set. Radeon buffer-object cleanup can then interpret the non-NULL mm pointer as evidence of a registered notifier and call mmu_interval_notifier_remove().

2

Which systems are most relevant to triage?

The described affected path involves the Linux kernel's MMU notifier handling and Radeon buffer-object cleanup. Systems using Radeon functionality with userptr ranges are the relevant exposure area described by the available data.

3

How can this be mitigated if the kernel fix cannot be applied immediately?

The provided information does not specify a configuration workaround. The triggering condition is a wrapping userptr range, so avoiding workloads or inputs that create wrapping userptr ranges avoids the described failed-insertion cleanup path.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203