All reports
High

kernel: kernel: Out-of-bounds write in GUP-fast via zero page count

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-99662

Probability of exploitation in the next 30 days: 0.17%

FIRST EPSS · 2026-11-20

Description

In the Linux kernel, the following vulnerability has been resolved: mm/gup: fix out-of-bounds write for nr_pages == 0 in GUP-fast With nr_pages == 0, GUP-fast still enters its page table walk and can write past the caller's page array. The old end <= start check caught empty ranges, but was replaced with an overflow check. Users such as OrangeFS can pass a zero page count derived from a userspace-supplied length. So let's return zero for nr_pages == 0 before starting the walk, just like GUP-slow. Fix generated by an LLM and sent by Chris Mason in private. [ david: simplify description ]

A flaw was found in the Linux kernel's memory management subsystem. When the fast user-space page pinning mechanism (GUP-fast) processes a request with a page count of zero, it fails to exit early before traversing page tables, leading to an out-of-bounds memory write past the allocated page array. A local attacker can trigger this issue by providing a zero-length parameter through supported kernel interfaces, potentially leading to kernel memory corruption, a denial of service (DoS), or privilege escalation.