llamaCVEVulnerability Intelligence
/
Linux kernel

CVE-2026-99700

Linux kernel: mm/hugetlb_vmemmap: map the shared tail page writable

Parche disponiblemm/hugetlb_vmemmap
Descargar PNG JSON
CVSS
—
N/D
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versión6.18.64
Exposición23 hDesde la divulgación, 20 nov 2026, 12:50 a. m.
Detección18 minDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Monitoreo
Detectada +1
12:50 a. m.
01:08 a. m.
12:12 a. m.
12:50 a. m.
06:41 a. m.
12:31 p. m.
06:21 p. m.
12:12 a. m.
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-99700 divulgada
Monitoreo Detectada Ingresó al índice
Monitoreo Verificada Última verificación contra las fuentes
Resumen

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.

Versiones

Rangos afectados

Afectada Corregida
Linux≥ 6.18.51 < 6.18.64
6.18.51
6.18.64
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
Linux
Corregida 6.18.64 — —
Versiones corregidas6.18.64
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Otrahttps://git.kernel.org/stable/c/f96a68bab26183433ea542dfb29ec41125f9fe39
Otrahttps://git.kernel.org/stable/c/e570f2c29fc07a1040c3736bf1a1dfa8065d5099
Otrahttps://git.kernel.org/stable/c/0120a603afadba8ab4954bb1ce60f8195f80efc8

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.