Answer in brief
CVE-2026-43486 records a Medium severity (CVSS 5.5) vulnerability in arm64: contpte: fix set_access_flags() no-op check for SMMU/ATS faults. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4602e5757bcceb231c3a13c36c373ad4a750eddb <05d239f2c95e66e27e7fb4e99ee07eb56e3e34b0 || >=4602e5757bcceb231c3a13c36c373ad4a750eddb <6f92a7a8b48a523f910ef25dd83808710724f59b || >=4602e5757bcceb231c3a13c36c373ad4a750eddb <09d620555e59768776090073a2c59d2bc8506eb3 || >=4602e5757bcceb231c3a13c36c373ad4a750eddb <97c5550b763171dbef61e6239cab372b9f9cd4a2 | 05d239f2c95e66e27e7fb4e99ee07eb56e3e34b0, 6f92a7a8b48a523f910ef25dd83808710724f59b, 09d620555e59768776090073a2c59d2bc8506eb3, 97c5550b763171dbef61e6239cab372b9f9cd4a2 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
May 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jun 26, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 26, 2026
In the Linux kernel, the following vulnerability has been resolved: arm64: contpte: fix set_access_flags() no-op check for SMMU/ATS faults contpte_ptep_set_access_flags() compared the gathered ptep_get() value against the requested entry to detect no-ops. ptep_get() ORs AF/dirty from all sub-PTEs in the CONT block, so a dirty sibling can make the target appear already-dirty. When the gathered value matches entry, the function returns 0 even though the target sub-PTE still has PTE_RDONLY set in hardware. For a CPU with FEAT_HAFDBS this gathered view is fine, since hardware may set AF/dirty on any sub-PTE and CPU TLB behavior is effectively gathered across the CONT range. But page-table walkers that evaluate each descriptor individually (e.g. a CPU without DBM support, or an SMMU without HTTU, or with HA/HD disabled in CD.TCR) can keep faulting on the unchanged target sub-PTE, causing an infinite fault loop. Gathering can therefore cause false no-ops when only a sibling has been updated: - write faults: target still has PTE_RDONLY (needs PTE_RDONLY cleared) - read faults: target still lacks PTE_AF Fix by checking each sub-PTE against the requested AF/dirty/write state (the same bits consumed by __ptep_set_access_flags()), using raw per-PTE values rather than the gathered ptep_get() view, before returning no-op. Keep using the raw target PTE for the write-bit unfold decision. Per Arm ARM (DDI 0487) D8.7.1 ("The Contiguous bit"), any sub-PTE in a CONT range may become the effective cached translation and software must maintain consistent attributes across the range.
Quoted source text, attributed separately from HOL analysis.