CVE-2026-99727: Linux kernel · mm/huge_memory: properly handle refcounted PUD mappings on fork
Affects Linux kernelSource CVE Database V5
Not known to be exploited : upgrade to e8ebc5a46795cd1fb4333df81f19bbf458467cce or d90bdc02e36ec08d8248ebc6cdc52e12043eb28c when convenient.
Data as of 20 Nov 2026, 06:34 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in e8ebc5a46795cd1fb4333df81f19bbf458467cce, d90bdc02e36ec08d8248ebc6cdc52e12043eb28c
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 e8ebc5a46795cd1fb4333df81f19bbf458467cce or d90bdc02e36ec08d8248ebc6cdc52e12043eb28c.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented in the Linux kernel as indicated by the presence of fixed commit versions. Users and administrators should update to the patched kernel versions containing the fix identified by commits e8ebc5a46795cd1fb4333df81f19bbf458467cce and d90bdc02e36ec08d8248ebc6cdc52e12043eb28c. No additional mitigation actions are specified or required.
Description
A vulnerability in the Linux kernel's memory management subsystem (mm/huge_memory) related to handling refcounted PUD mappings on fork has been fixed. The flaw involved improper copying of device-DAX entries without updating reference counts and memory accounting, which could lead to incorrect memory management in child processes after a fork. The issue was addressed by correctly taking folio references and updating accounting during the fork operation.