UNKNOWNCVSS not yet scoredVulnerability

CVE-2026-99734

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.

Properties

Last source
FIRST EPSS
Nvd fetched at
2026-11-22T12:30:49.958423+00:00
Epss score
0.00156
Cve id
CVE-2026-99734
First seen by Signal
2026-11-20T07:38:10+00:00
Name
CVE-2026-99734
Retrieved at
2026-11-22T12:32:29+00:00
Published at
2026-11-20T06:18:10.753
Last modified
2026-11-20T06:18:10.753
Epss percentile
0.0473

Related research

Explore deeper with Ninja Signal's threat intelligence graph

CVE-2026-99734 — Ninja Signal Threat Intelligence | Ninja Signal