CVE-2026-98373: Linux kernel · mm/hugetlb: preserve mremap address delta when skipping page tables
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in cf73ef2a761df9329af116c905a7a94b317921e4 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:16 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in cf73ef2a761df9329af116c905a7a94b317921e4, 850cc4a84b36a0062dcd0391acd2450e20ab0767, 480a39b0a12c977ed6e755f3d12a23424c57d11f +2
Exploitation evidence
Disclosed: evidence found.
CVE published 7 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: preserve mremap address delta when skipping page tables move_hugetlb_page_tables() optimizes mremap() by advancing to the last entry in the page table when the source page table does not exist, either initially or after unsharing a PMD table. The common loop increment then steps to the first entry in the next page table. However, the code advances both the source and destination addresses to the last entries in their respective page tables, which is wrong. The destination address must be advanced only by the same amount as the source address. If the source and destination offsets within their page tables differ, the destination address can be advanced too far, causing follow-up issues. Fix this by advancing the destination address by the source advance distance. With a reproducer, we were able to trigger a kernel panic on x86-64. With this fix in place, we can no longer reproduce the issue.
References
- git.kernel.org/stable/c/cf73ef2a761df9329af116c905a7a94b317921e4 (opens in a new tab)
- git.kernel.org/stable/c/7a96b0f657c8d799ea5b8e02fc9ec7cca0e6e7ff (opens in a new tab)
- git.kernel.org/stable/c/850cc4a84b36a0062dcd0391acd2450e20ab0767 (opens in a new tab)
- git.kernel.org/stable/c/480a39b0a12c977ed6e755f3d12a23424c57d11f (opens in a new tab)
- git.kernel.org/stable/c/9bdad082d44bdcf93716973dcba6be77e8a06e7b (opens in a new tab)