CVE-2026-99663: mm/gup: fix clearing folios in memfd_pin_folios()

Published Nov 20, 2026
·
Updated

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

mm/gup: fix clearing folios in memfdpinfolios()

memfdpinfolios() pins folios obtained directly from the page cache without checking whether they are uptodate. However, shmem fallocate() can leave newly allocated folios uncleared and not uptodate. Callers such as udmabuf can then expose uninitialized memory to userspace.

Clear non-uptodate folios and mark them uptodate under the folio lock before returning them to the caller.

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

[ david: simplify description and comment ]

Affected Software

6 affected componentsFixes available
linux/kernel>=6.11.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<=6.12.107-1, <=6.12.117-1, <=7.3.4-1
6.1.176-16.1.192-27.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 6.1.176-1Fixed in 6.1.192-2Fixed in 7.3.5-1

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:18 AM
Description

Frequently Asked Questions

1

Which environments are most likely to be exposed?

Exposure requires a kernel path that pins folios through memfd_pin_folios(), with udmabuf identified as an example caller. The issue can arise when shmem fallocate() has created newly allocated folios that remain uncleared and not uptodate.

2

What would an attacker need to trigger the issue?

They would need access to a userspace-accessible path, such as one involving udmabuf, that obtains folios pinned from the page cache after the relevant shmem fallocate() condition. The resulting risk is exposure of uninitialized memory to userspace.

3

How can I identify a fixed kernel from the supplied information?

No affected or fixed kernel version ranges are provided. The supplied references identify three stable-tree commits associated with the fix; the fix clears non-uptodate folios and marks them uptodate while holding the folio lock.

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