llamaCVEVulnerability Intelligence
/
Linux kernel

CVE-2026-99664

Linux kernel race condition in GUP PUD walk for DAX mappings

An attacker racing page table zaps and refaults on DAX mappings can make page walks read inconsistent state.

Sin parche publicadomm/gup
Descargar PNG JSON
CVSS
—
N/D
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
ParcheSin parcheEl fabricante no ha publicado corrección
Exposición1 dDesde 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.
01:36 a. m.
12:50 a. m.
07:01 a. m.
01:13 p. m.
07:24 p. m.
01:36 a. m.
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-99664 divulgada
Monitoreo Detectada Ingresó al índice
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Resumen generado por IA · CC-BY 4.0 · 20 nov 2026

The Linux kernel's page-walk code in `follow_pud_mask()` reads a PUD entry without holding the page table lock, so a concurrent zap and refault can leave it inconsistent. This only affects device-dax mappings that use PUD entries.

Descripción original del registro (Linux)

In the Linux kernel, the following vulnerability has been resolved: mm/gup: recheck the PUD under PTL in follow_pud_mask() follow_pud_mask() reads the PUD without a lock. If it is a leaf, it takes the lock and calls follow_huge_pud(), which reads the entry again, but only tests whether it is present. A leaf can be zapped concurrently and a page fault can fill the empty entry with a page table. This currently only applies when device-dax makes use of PUD entries, and the fault after e.g., MADV_DONTNEED would find THPs to be disabled. That requires a sequence like 1) Fault in the PUD 2) Disable THP 3) Have GUP race against concurrent MADV_DONTNEED + refault Which is rather unlikely to happen in practice, which is why we never received a report about such a problem. Before commit 1b1676180246 ("mm/gup: handle huge pud for follow_pud_mask()"), we performed that check in follow_devmap_pud() by testing for pud_devmap(). Let's fix it by just structuring follow_pud_mask() similar to follow_pmd_mask(), minus protnone stuff that does not apply and minus FOLL_SPLIT_PMD handling. That makes it much easier to spot any such inconsistencies. Perform the pud_bad() check early in follow_pmd_mask() and just forward the PUD value. We can drop the pud_present() check in follow_huge_pud(), just like we have in follow_huge_pmd(). Even though we are performing more changes than strictly necessary, the fix should be easy to backport.

Versiones

Versiones afectadas

6.10
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
Linux
Sin parche — — —
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/da57b6bce646946c083a48df644d43bb9d011f5f
Otrahttps://git.kernel.org/stable/c/9eaedd598cd25eb0e18958e2456153a4c1f3db03
Otrahttps://git.kernel.org/stable/c/79cb51d538abc459f74e046d27797d36b133ce0e

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