CVE-2026-99706: Linux kernel · mm: fix address wraparound when scanning large folio PTEs
Affects Linux kernelSource CVE Database V5
Not known to be exploited : upgrade to f681d4580d5c3c749f623cda722a21aefd3147b3 or f6c17bda9b304795a2c284fb6c8a8eaac6248b80 soon.
Data as of 20 Nov 2026, 06:36 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in f681d4580d5c3c749f623cda722a21aefd3147b3, f6c17bda9b304795a2c284fb6c8a8eaac6248b80
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade Linux kernel to f681d4580d5c3c749f623cda722a21aefd3147b3 or f6c17bda9b304795a2c284fb6c8a8eaac6248b80.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available in the Linux kernel, applied in commits f681d4580d5c3c749f623cda722a21aefd3147b3 and f6c17bda9b304795a2c284fb6c8a8eaac6248b80. Users and administrators should update to the patched Linux kernel version 6.10 or later containing these fixes to mitigate the vulnerability.
Description
A vulnerability in the Linux kernel's memory management subsystem allowed address wraparound when scanning large folio page table entries (PTEs). This flaw could cause the kernel to crash when certain large folio pages are mapped near the start or end of the address space, leading to an arithmetic wraparound in address calculations. The issue was fixed by introducing a helper function that correctly handles address ranges and prevents wraparound errors.