CVE-2026-99730: mm/filemap: finish fault cleanup before dropping the fault lock

Published Nov 20, 2026
·
Updated

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

mm/filemap: finish fault cleanup before dropping the fault lock

On a retried fault, a fatal signal interrupting the folio lock wait makes lockfoliomaybedropmmap() drop the fault lock without pinning the file. However, filemapfault() may still need to release mapping->invalidatelock. A concurrent munmap() can release the last file reference and free the mapping before that unlock.

Defer dropping the fault lock to filemapfault()'s retry cleanup, after releasing invalidatelock. If the fault lock was already dropped for I/O, release the existing file reference instead. Keep the fault lock held for FAULTFLAGRETRYNOWAIT as before.

Affected Software

7 affected componentsFixes available
linux/kernel>=5.15.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

Event History

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

Frequently Asked Questions

1

What conditions are required to trigger this issue?

The affected path requires a retried page fault where a fatal signal interrupts waiting for a folio lock. A concurrent munmap() must then be able to release the last file reference while filemap_fault() still needs to release mapping->invalidate_lock.

2

What is the race condition involved?

The fault lock can be dropped without pinning the file, allowing concurrent munmap() to free the mapping before filemap_fault() unlocks mapping->invalidate_lock. The fix moves fault-lock dropping to retry cleanup after invalidate_lock has been released, or releases an existing file reference when the fault lock was already dropped for I/O.

3

Does the change alter handling of FAULT_FLAG_RETRY_NOWAIT?

No. The stated fix keeps the fault lock held for FAULT_FLAG_RETRY_NOWAIT, as before.

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