CVE-2026-99700

Source
https://cve.org/CVERecord?id=CVE-2026-99700
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99700.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-99700
Published
2026-11-20T05:50:42Z
Modified
2026-11-20T07:01:09Z
Summary
mm/hugetlb_vmemmap: map the shared tail page writable
Details

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

mm/hugetlb_vmemmap: map the shared tail page writable

page_ref_add_unless_zero() reads the refcount and then updates it with a cmpxchg. A lockless get, such as a page cache lookup or a PFN scanner, can read a non-zero refcount from a page that is then freed and reused as a hugetlb tail page. If HVO remaps its struct page to the shared tail page in between, the cmpxchg writes to read-only vmemmap:

CPU0 (lockless get)               CPU1
c = atomic_read(&page->_refcount)
                                  page freed
                                  page allocated as a hugetlb tail
                                  HVO remaps the struct page RO
try_cmpxchg(&page->_refcount, &c, c + 1)
  -> write fault on read-only vmemmap

The refcount is zero by then and the compare fails, but a compare-and-swap instruction needs write access whether or not it succeeds. The kernel oopses when hugetlb pages are allocated at runtime with HVO enabled while a lockless get races with it.

Commit bd225530a4c7 ("mm/hugetlb_vmemmap: fix race with speculative PFN walkers") closed the window with RCU on both sides. The RCU was removed together with fake heads, on the wrong belief that it was only needed for them.

Map the shared tail page writable instead of restoring the RCU. Every struct page on it is a tail with a zero refcount, so a late cmpxchg fails and leaves the page unchanged. RCU would put rcu_read_lock() back around every get and synchronize_rcu() back into hugetlb allocation and freeing.

The cost is the protection against stray writes to tail struct pages. The shared page is shared by all hugetlb folios of the same order in the zone, so such a write now corrupts all of them instead of oopsing.

Bootmem folios optimized when the memmap is set up keep their tails read-only. Nothing does a lockless get on them before hugetlb takes them over.

Database specific
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99700.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
dba93b8cceb0048071389352fc29dcb0a7fe666f
Fixed
f96a68bab26183433ea542dfb29ec41125f9fe39
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
32c440d67e6cd96a715007d0e62eb970b0c49abc
Fixed
e570f2c29fc07a1040c3736bf1a1dfa8065d5099
Fixed
0120a603afadba8ab4954bb1ce60f8195f80efc8

Affected versions

v6.*
v6.18.51
v6.18.52
v6.18.53
v6.18.54
v6.18.55
v6.18.56
v6.18.57
v6.18.58
v6.18.59
v6.18.60
v6.18.61
v6.18.62
v6.18.63

Database specific

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

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
6.18.51
Fixed
6.18.64
Type
ECOSYSTEM
Events
Introduced
7.1.0
Fixed
7.3.5

Database specific

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