Local data corruption via lost dirty-page state
Published Aug 15, 2026 · Updated Aug 15, 2026
Dirty-page tracking failure in Linux on LoongArch allows local users to corrupt data during copy-on-write page reclamation. With hardware page-table walking enabled, pte_wrprotect() and pmd_wrprotect() clear _PAGE_DIRTY without first preserving it in _PAGE_MODIFIED, so reclaim treats a modified page as clean. The sequence requires a local account, LoongArch hardware PTW, a private anonymous mapping, MADV_FREE followed by a write and fork or clone, and memory pressure; affected pages can be freed without writeback.
Summary
What happened
Dirty-page tracking failure in Linux on LoongArch allows local users to corrupt data during copy-on-write page reclamation. With hardware page-table walking enabled, pte_wrprotect() and pmd_wrprotect() clear _PAGE_DIRTY without first preserving it in _PAGE_MODIFIED, so reclaim treats a modified page as clean. The sequence requires a local account, LoongArch hardware PTW, a private anonymous mapping, MADV_FREE followed by a write and fork or clone, and memory pressure; affected pages can be freed without writeback.
The record
- CVE
- CVE-2026-72043
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-911, T1485
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=09cfefb7fa70c3af011b0db0a513fd80b2f18abc <018e9828eb523c638fa3d9bdf0fd4956b74555b2
- Affected versionversion=09cfefb7fa70c3af011b0db0a513fd80b2f18abc <39bb21a4bff0d70058bf752d7b5aa2e2ccc864a9
- Affected versionversion=09cfefb7fa70c3af011b0db0a513fd80b2f18abc <76f88650763a35cbf1384c65d66d096fa31cc58d
- Affected versionversion=09cfefb7fa70c3af011b0db0a513fd80b2f18abc <a65f49b6f7ece756394f8f0e85570020e7fd0e35
- Affected versionversion=09cfefb7fa70c3af011b0db0a513fd80b2f18abc <e483da960892c41fa7f0cf0d2fc2410d65a483d6
- Affected versionversion=09cfefb7fa70c3af011b0db0a513fd80b2f18abc <e8a916579e427af32f2de8213dfa23c5df6e6664
- Affected versionversion=5.19
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo