Skip to main content
VulnerabilityPublished

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

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99734· Medium

Not known to be exploited : upgrade to ea5cc241113f7820ce037dbcf8b7eb959fbf1c0d or d3710111839d11339e414b1bb3fea3d05ab83f6e when convenient.

Data as of 20 Nov 2026, 07:34 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in ea5cc241113f7820ce037dbcf8b7eb959fbf1c0d, d3710111839d11339e414b1bb3fea3d05ab83f6e

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Linux kernel to ea5cc241113f7820ce037dbcf8b7eb959fbf1c0d or d3710111839d11339e414b1bb3fea3d05ab83f6e.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ c49fcfcda8b5b06529103664f0291f433f5e6d24, < ea5cc241113f7820ce037dbcf8b7eb959fbf1c0d
Fixed in
  • ea5cc241113f7820ce037dbcf8b7eb959fbf1c0d
LinuxLinuxAffected
  • ≥ c49fcfcda8b5b06529103664f0291f433f5e6d24, < d3710111839d11339e414b1bb3fea3d05ab83f6e
Fixed in
  • d3710111839d11339e414b1bb3fea3d05ab83f6e
LinuxLinuxAffected
  • =4.18
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: mm/shmem: make shmem_file() check the file's inode shmem_file() only checks if file->f_mapping 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 shmem_file() 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 shmem_mapping() in collapse_file() instead to not change the behavior of collapse_file(): it operates on the page cache and uses mapping->host for shmem inode operations. Focusing on the file does not seem relevant.

References

Community reviews

Loading reviews…