CVE-2026-74600: mm/page_table_check: skip special zero mappings
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.17% (FIRST EPSS).
- Fixed version: Linux Linux 084b031a1cc13b1d50b9660baace0b7eba52bebe, 51e16e5adadaa78b56f31a1cb02eb7267787625e, 7755be923e325dc300f4b0c3e1ad7e91b28b3cb9.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 084b031a1cc13b1d50b9660baace0b7eba52bebe, 51e16e5adadaa78b56f31a1cb02eb7267787625e, 7755be923e325dc300f4b0c3e1ad7e91b28b3cb9 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/page_table_check: skip special zero mappings page_table_check_set() and page_table_check_clear() account mappings based on PageAnon(). Shared zero-page PTEs and huge zero PMDs are special mappings, but page_table_check can still account them as file-backed pages. An unprivileged process can populate enough zero mappings to overflow file_map_count and hit the existing BUG_ON(). The PTE path can do this with the shared zero page, and the PMD path can do the same with huge zero mappings. Skip special zero mappings in the user page-table accounting paths. Keep the PTE-side pte_special() check, and identify huge zero PMDs from the mapped folio instead of pmd_special(). That covers architectures where pmd_special() is a no-op without adding huge_zero_pfn checks to the generic counter helpers.
- Published
- Aug 22, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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
- 5.17affected
- df4e817b710809425d899340dbfa8504a3ca4ba5 and later · before 084b031a1cc13b1d50b9660baace0b7eba52bebeaffected · git
- df4e817b710809425d899340dbfa8504a3ca4ba5 and later · before f6cf9832e677ec07b1675782bd2bad472cfd3cdcaffected · git
- df4e817b710809425d899340dbfa8504a3ca4ba5 and later · before 51e16e5adadaa78b56f31a1cb02eb7267787625eaffected · git
- df4e817b710809425d899340dbfa8504a3ca4ba5 and later · before 7755be923e325dc300f4b0c3e1ad7e91b28b3cb9affected · git
- df4e817b710809425d899340dbfa8504a3ca4ba5 and later · before b726eb3c94d23e09da0e0f46b0fa09fb2b5d99ccaffected · git
- df4e817b710809425d899340dbfa8504a3ca4ba5 and later · before 8db4bab826ccc9ec10fa41736a48031cd338d392affected · git
- before 5.17not 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:13 | linux | before 6.12.115-2 | 6.12.115-2 |
| Debian:14 | linux | before 7.1.9-1 | 7.1.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-74598Aug 22, 2026 · ipv6: fix Route Information option length validation30Monitor
- ← EarlierCVE-2026-74599Aug 22, 2026 · mm/ptdump: always stabilise against page table freeing using init_mm0Monitor
- Later →CVE-2026-74601Aug 22, 2026 · ring-buffer: Use current_context for safe per-CPU buffer swap31Monitor
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 | 084b031a1cc13b1d50b9660baace0b7eba52bebe | Vendor (CNA) |
| Linux Linux | 51e16e5adadaa78b56f31a1cb02eb7267787625e | Vendor (CNA) |
| Linux Linux | 7755be923e325dc300f4b0c3e1ad7e91b28b3cb9 | Vendor (CNA) |
| Linux Linux | 8db4bab826ccc9ec10fa41736a48031cd338d392 | Vendor (CNA) |
| Linux Linux | b726eb3c94d23e09da0e0f46b0fa09fb2b5d99cc | Vendor (CNA) |
| Linux Linux | f6cf9832e677ec07b1675782bd2bad472cfd3cdc | Vendor (CNA) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.1.9-1 · Debian:14 | 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.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0893 · Aug 24, 2026(Linux Kernel Güvenlik Bildirimi)
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/51e16e5adadaa78b56f31a1cb02eb7267787625e
- git.kernel.org/stable/c/7755be923e325dc300f4b0c3e1ad7e91b28b3cb9
- git.kernel.org/stable/c/8db4bab826ccc9ec10fa41736a48031cd338d392
- git.kernel.org/stable/c/b726eb3c94d23e09da0e0f46b0fa09fb2b5d99cc
- git.kernel.org/stable/c/f6cf9832e677ec07b1675782bd2bad472cfd3cdc
Vendor advisories and official records. Exploit/PoC links are deliberately left out.