CVE-2026-99734: mm/shmem: make shmem_file() check the file's inode

Published Nov 20, 2026
·
Updated

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

mm/shmem: make shmemfile() check the file's inode

shmemfile() only checks if file->fmapping is a shmem mapping. This mapping can belong to another file, however, as with a Coda file backed by a tmpfs container after mmap().

So it does not guarantee that the file inode is an actual shmem inode.

Seal handling and memfd preservation use this check before accessing shmem inode state, so they can access an inode of the wrong type.

Let's make shmemfile() check the inode's file operations instead, to identify shmem inodes reliably. This will identify regular shmem inodes, including memfds and ordinary tmpfs files, independently of wrapper file operations.

Use shmemmapping() in collapsefile() instead to not change the behavior of collapsefile(): it operates on the page cache and uses mapping->host for shmem inode operations. Focusing on the file does not seem relevant.

Affected Software

5 affected componentsFixes available
linux/kernel>=4.18.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 7.3.5
  2. 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

Which systems are realistically exposed to this issue?

Linux kernel systems are affected where seal handling or memfd preservation operates on a file whose mapping is backed by shmem but whose inode is not actually a shmem inode. The described example is a Coda file backed by a tmpfs container after mmap().

2

What condition is required to trigger the incorrect inode access?

An attacker or triggering workload needs a file with a shmem mapping that belongs to a different file, so that checking file->f_mapping incorrectly treats the file as shmem. The vulnerable paths then access shmem inode state through an inode of the wrong type.

3

Are ordinary tmpfs files and memfds themselves misidentified by the corrected check?

No. The revised inode-based check is described as reliably identifying regular shmem inodes, including ordinary tmpfs files and memfds, even when wrapper file operations are involved.

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