mm: migrate_device: fix pte_pfn/pte_dirty called on non-present PTE
In the Linux kernel, the following vulnerability has been resolved: mm: migrate_device: fix pte_pfn/pte_dirty called on non-present PTE pte_pfn() and pte_dirty() have undefined behaviour when called on a non-present PTE. In migrate_vma_collect_pmd(), these functions may be invoked on non-present entries (e.g., device-private entries), leading to potential crashes from pte_pfn() or incorrect dirty folio accounting from pte_dirty(). Fix both by guarding with pte_present() checks.
- Published
- Aug 28, 2026
- Updated
- Aug 28, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpAffected systems
—
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.19affected
- 6c287605fd56466e645693eff3ae7c08fba56e0a and later · before 26f9ca8ed42cba25d2c75daff13561cce6019395affected · git
- 6c287605fd56466e645693eff3ae7c08fba56e0a and later · before 5b948706f11a950bc73c5304630d0a7eafc40dafaffected · git
- 6c287605fd56466e645693eff3ae7c08fba56e0a and later · before 86d55447de3738620b9a8272ff167ce97e7f7203affected · git
- 6c287605fd56466e645693eff3ae7c08fba56e0a and later · before 2be94d6b20789b8865b1864dae5fe458ca85e019affected · git
- 6c287605fd56466e645693eff3ae7c08fba56e0a and later · before 42f30fa5481a1f90571ccdfbb20d2e25e47ae76eaffected · git
- 6c287605fd56466e645693eff3ae7c08fba56e0a and later · before 63867c82d0c0c2d182016a32b1cc0103116b0ea5affected · git
- before 5.19not affected · semver
- 6.1.184 and later · up to and including 6.1.*not affected · semver
- 6.6.153 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 | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.8-1 | 7.1.8-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
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
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 | 26f9ca8ed42cba25d2c75daff13561cce6019395 | Vendor (CNA) |
| Linux Linux | 2be94d6b20789b8865b1864dae5fe458ca85e019 | Vendor (CNA) |
| Linux Linux | 42f30fa5481a1f90571ccdfbb20d2e25e47ae76e | Vendor (CNA) |
| Linux Linux | 5b948706f11a950bc73c5304630d0a7eafc40daf | Vendor (CNA) |
| Linux Linux | 63867c82d0c0c2d182016a32b1cc0103116b0ea5 | Vendor (CNA) |
| Linux Linux | 86d55447de3738620b9a8272ff167ce97e7f7203 | Vendor (CNA) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-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.
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-0945 · Aug 31, 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
- git.kernel.org/stable/c/26f9ca8ed42cba25d2c75daff13561cce6019395
- git.kernel.org/stable/c/2be94d6b20789b8865b1864dae5fe458ca85e019
- git.kernel.org/stable/c/42f30fa5481a1f90571ccdfbb20d2e25e47ae76e
- git.kernel.org/stable/c/5b948706f11a950bc73c5304630d0a7eafc40daf
- git.kernel.org/stable/c/63867c82d0c0c2d182016a32b1cc0103116b0ea5
- git.kernel.org/stable/c/86d55447de3738620b9a8272ff167ce97e7f7203
Vendor advisories and official records. Exploit/PoC links are deliberately left out.