CVE-2026-99661: mm/gup: check for overflow when converting nr_pages to bytes in GUP-fast
In the Linux kernel, the following vulnerability has been resolved:
mm/gup: check for overflow when converting nrpages to bytes in GUP-fast
The overflow check in gupfastfallback() only covers the addition to start. The preceding nrpages << PAGESHIFT can already have truncated the length on 32bit.
Users such as RapidIO's riodmatransfer() can derive such page counts from a 64-bit userspace length.
Let's just checkshloverflow() to reject any such overflow with -EOVERFLOW early.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 5.11 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.118 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.64 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.3.5
Frequently Asked Questions
Which systems are exposed to this issue?
The issue affects 32-bit Linux kernel environments where GUP-fast handles a page count that is converted to bytes. It is particularly relevant to callers that derive page counts from a 64-bit userspace length, such as RapidIO's rio_dma_transfer().
What input is needed to trigger the overflow?
A caller must supply or derive an nr_pages value large enough that shifting it by PAGE_SHIFT overflows during conversion to a byte length on 32-bit systems. A 64-bit userspace length that is converted into a page count can provide such a value.
What happens after the fix is applied?
The kernel checks the shift conversion for overflow before using the resulting byte length. Requests that would overflow are rejected early with -EOVERFLOW.