CVE-2026-98373: mm/hugetlb: preserve mremap address delta when skipping page tables
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Fixed version: Linux Linux 480a39b0a12c977ed6e755f3d12a23424c57d11f, 7a96b0f657c8d799ea5b8e02fc9ec7cca0e6e7ff, 850cc4a84b36a0062dcd0391acd2450e20ab0767.
Low priority for now. Upgrade to Linux Linux 480a39b0a12c977ed6e755f3d12a23424c57d11f, 7a96b0f657c8d799ea5b8e02fc9ec7cca0e6e7ff, 850cc4a84b36a0062dcd0391acd2450e20ab0767 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 7, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.0affected
- e95a9851787bbb3cd4deb40fe8bab03f731852d1 and later · before ab4f0f68cf4773dc0513baccbbe790c80a301773affected · git
- e95a9851787bbb3cd4deb40fe8bab03f731852d1 and later · before cf73ef2a761df9329af116c905a7a94b317921e4affected · git
- e95a9851787bbb3cd4deb40fe8bab03f731852d1 and later · before 7a96b0f657c8d799ea5b8e02fc9ec7cca0e6e7ffaffected · git
- e95a9851787bbb3cd4deb40fe8bab03f731852d1 and later · before 850cc4a84b36a0062dcd0391acd2450e20ab0767affected · git
- e95a9851787bbb3cd4deb40fe8bab03f731852d1 and later · before 480a39b0a12c977ed6e755f3d12a23424c57d11faffected · git
- e95a9851787bbb3cd4deb40fe8bab03f731852d1 and later · before 9bdad082d44bdcf93716973dcba6be77e8a06e7baffected · git
- before 6.0not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.9-1 | 7.2.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98371Oct 6, 2026 · xfrm: iptfs: fix runt reassembly panic from short inner tot_len0Monitor
- ← EarlierCVE-2026-98372Oct 6, 2026 · xfrm: iptfs: fix stack OOB read in iptfs_skb_reset_frag_walk()0Monitor
- Later →CVE-2026-98374Oct 7, 2026 · tcp: fix use-after-free of retransmit_skb_hint in tcp_send_synack()35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 480a39b0a12c977ed6e755f3d12a23424c57d11f | Vendor (CNA) |
| Linux Linux | 7a96b0f657c8d799ea5b8e02fc9ec7cca0e6e7ff | Vendor (CNA) |
| Linux Linux | 850cc4a84b36a0062dcd0391acd2450e20ab0767 | Vendor (CNA) |
| Linux Linux | 9bdad082d44bdcf93716973dcba6be77e8a06e7b | Vendor (CNA) |
| Linux Linux | ab4f0f68cf4773dc0513baccbbe790c80a301773 | Vendor (CNA) |
| Linux Linux | cf73ef2a761df9329af116c905a7a94b317921e4 | Vendor (CNA) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.9-1 · Debian:14 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 12, 2026+36 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/7a96b0f657c8d799ea5b8e02fc9ec7cca0e6e7ff
- git.kernel.org/stable/c/850cc4a84b36a0062dcd0391acd2450e20ab0767
- git.kernel.org/stable/c/9bdad082d44bdcf93716973dcba6be77e8a06e7b
- git.kernel.org/stable/c/ab4f0f68cf4773dc0513baccbbe790c80a301773
- git.kernel.org/stable/c/cf73ef2a761df9329af116c905a7a94b317921e4
Vendor advisories and official records. Exploit/PoC links are deliberately left out.