CVE-2026-99742

Source
https://cve.org/CVERecord?id=CVE-2026-99742
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99742.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-99742
Published
2026-11-20T05:51:14Z
Modified
2026-11-20T07:01:15Z
Summary
mm/mempolicy: charge shared policy nodes
Details

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

mm/mempolicy: charge shared policy nodes

Any local user can bypass memory.max with mbind() on a tmpfs file, and allocate unbounded kernel memory.

mbind() sets a NUMA memory policy for a range of a mapping. If the mapping is of a shmem and friends, the kernel also stores the policy on the inode, in a tree with one entry per range of the file.

Each mbind() on a single page of a mapping can add one shared policy node (struct sp_node) and one struct mempolicy to that tree. They outlive the mapping and stay around until the inode is destroyed. The tree is not bounded by the file size, so the file can be empty.

Memory that user space can allocate must be charged to a memory cgroup. A slab cache does that for all of its objects if it is created with SLAB_ACCOUNT. numa_policy_init() creates the slab caches for both structs without SLAB_ACCOUNT, so they are not charged to any cgroup.

Reproduced with mbind() on single pages of an empty tmpfs file, from a cgroup with memory.max=8M: the global OOM killer killed tasks owned by root, and the machine panicked.

Fix this by creating both caches with SLAB_ACCOUNT. This change implies that mbind() can now fail when running into memcg limits. Further, the policy_cache also serves task and VMA policies, so they are similarly accounted now.

Note that per-file limits are not really helpful, as the user could simply use many files; having limits per user is tricky as well.

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

[ david: smaller description tweaks ]

Database specific
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99742.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
5d097056c9a017a3b720849efb5432f37acabbac
Fixed
d500c37437cce47e492c561757ece2596e21446a
Fixed
40e340bab4d07958b2077c16650c3da5c76d5820
Fixed
0109fa404651e20493ca35a9a7d4f87861148064
Fixed
68b2aa37afa390f08de13bc0bac61a9ded3318bc

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99742.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
4.5.0
Fixed
6.12.118
Type
ECOSYSTEM
Events
Introduced
6.13.0
Fixed
6.18.64
Type
ECOSYSTEM
Events
Introduced
6.19.0
Fixed
7.3.5

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99742.json"