NVD / CVE Program· CNA Linux

CVE-2026-80685: mm/util: don't read __page_2 for order-1 folios in snapshot_page()

Noroxi assessment

Priority: Monitor (action score 28/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).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 6.13, 7441d6348c70738e9ed307510db171c7a9b3f4bf, 9668ffe0e2a5e2399dce281620198a2e415871fc.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 6.13, 7441d6348c70738e9ed307510db171c7a9b3f4bf, 9668ffe0e2a5e2399dce281620198a2e415871fc 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/util: don't read __page_2 for order-1 folios in snapshot_page() snapshot_page() currently reads __page_2 after checking nr_pages > 1, but it should only do so when nr_pages > 2. If an order-1 folio is allocated at the end of a vmemmap section, __page_2 will not exist and reading it will cause a fault. During DLPAR memory remove on a 22 TB ppc64le LPAR, snapshot_page() oopsed on the page isolation path while reading an order-1 folio's __page_2 from an adjacent absent section (unmapped vmemmap). Fix this to avoid reading memmap that doesn't exist (e.g., a vmemmap hole).

HighCVSS 7.1 · v3.1—No exploit Fix available

EUVD-2026-67561

Published: Aug 28, 2026
Updated: Sep 21, 2026
EPSS: 0.1% · 5th percentile
CWE: —

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 28 / 40 · 7.1 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CNA vs NVD score

NVD: —
CNA · Linux: 7.1; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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

Is your version affected? Check it

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 help

Affected 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
- 4117738bd42c8ab58090729daf0f8472a936f662, 6.15affected
- 31a31da8a6187f1e5448ec73222e01d7d3fed4aa and later · before 9668ffe0e2a5e2399dce281620198a2e415871fcaffected · git
- 31a31da8a6187f1e5448ec73222e01d7d3fed4aa and later · before c649324571206a30949765320b91ccdb4c1722dcaffected · git
- 31a31da8a6187f1e5448ec73222e01d7d3fed4aa and later · before 7441d6348c70738e9ed307510db171c7a9b3f4bfaffected · git
- 6.12.111 and later · before 6.13affected · semver
- before 6.15not affected · semver
- 6.18.44 and later · up to and including 6.18.*not affected · semver
- 7.1.8 and later · up to and including 7.1.*not affected · semver
- 7.2 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:14	linux	before 7.1.8-1	7.1.8-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
40Plan
CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
40Plan
CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
40Plan

Published before and after this one in the same product

← EarlierCVE-2026-80680Aug 28, 2026 · i2c: amd-mp2: Unregister callback on adapter add failure
31Monitor
← EarlierCVE-2026-80682Aug 28, 2026 · riscv/mm: use physical alignment for vmemmap_start_pfn
31Monitor
Later →CVE-2026-80686Aug 28, 2026 · mm: migrate_device: fix pte_pfn/pte_dirty called on non-present PTE
0Monitor

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	6.13	Vendor (CNA)
Linux Linux	7441d6348c70738e9ed307510db171c7a9b3f4bf	Vendor (CNA)
Linux Linux	9668ffe0e2a5e2399dce281620198a2e415871fc	Vendor (CNA)
Linux Linux	c649324571206a30949765320b91ccdb4c1722dc	Vendor (CNA)
debian:linux	7.1.8-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.

EPSS, last 120 days

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 researchers

Finders, 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-0945 · Aug 31, 2026(Linux Kernel Güvenlik Bildirimi)

All national notices →

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

nvd-secondary

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✗ → ✓Sep 28, 2026, 10:08 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/7441d6348c70738e9ed307510db171c7a9b3f4bf

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records