CVE-2026-99734

published 20 Nov 2026 · updated 21 Nov 2026

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

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel d3710111839d11339e414b1bb3fea3d05ab83f6e, Kernel ea5cc241113f7820ce037dbcf8b7eb959fbf1c0d and Kernel 7.3.5.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=4.18, >=c49fcfcda8b5b06529103664f0291f433f5e6d24 <d3710111839d11339e414b1bb3fea3d05ab83f6e, >=c49fcfcda8b5b06529103664f0291f433f5e6d24 <ea5cc241113f7820ce037dbcf8b7eb959fbf1c0dd3710111839d11339e414b1bb3fea3d05ab83f6e, ea5cc241113f7820ce037dbcf8b7eb959fbf1c0d
linux-kernel: Kernel>=4.18.0 <7.3.57.3.5

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99734 severity on Zeptric[![CVE-2026-99734](https://zeptric.io/badge/cve/CVE-2026-99734.svg)](https://zeptric.io/cve/CVE-2026-99734)