CVE-2026-98923arm64: io: Reject non-user protection in ioremap_prot()
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: arm64: io: Reject non-user protection in ioremap_prot() Mapping a stack-top page via /dev/mem with PROT_NONE and then reading that process's /proc/<pid>/cmdline triggers a spurious WARN in ioremap_prot() through generic_access_phys(): WARNING: ./arch/arm64/include/asm/io.h:275 at generic_access_phys Call trace: generic_access_phys+0x1c8/0x228 (P) __access_remote_vm+0x2b4/0x398 access_remote_vm+0x14/0x30 get_mm_cmdline+0xf8/0x2a0 proc_pid_cmdline_read+0x68/0x120 generic_access_phys() passes the protection derived from the user PTE to ioremap_prot(). On arm64, a PROT_NONE mapping is represented by a present-invalid PTE, so pte_present() still returns true and the protection reaches ioremap_prot(). A PROT_NONE mapping does not have PTE_USER, causing the existing WARN_ON_ONCE() in ioremap_prot() to fire even though this is a valid user mapping. Execute-only mappings have the same issue and must not be readable through this path either. ioremap_prot() should therefore reject protection values without PTE_USER without warning. This makes the access fail cleanly for PROT_NONE and execute-only mappings while retaining the existing user-protection contract.
Timeline
ID reserved
By Linux
- 28 days later
· 28 days later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 64858b76ec67c5fc40fef8ec1841fecb78c1ebde – < fddc90d4af4550af410f52d11bbf6b5f36443838
- affected eeecafce5afffb4da703666ebefbd4d6e2a5abf6 – < 0b04af3d88bb7fc69b2d92457890608860e42365
- affected 3d64dcc0799c2d6921ba027716b7be721eb19fa8 – < b17aa4955e3a694c663ebe99626e4c76ca4f7cfb
- affected 8f098037139b294050053123ab2bc0f819d08932 – < 9b583795feb51f8d50203228d001760d1344ef01
- affected 8f098037139b294050053123ab2bc0f819d08932 – < bb756b11ad63832ebee58caf9e8f9381eaecff9f
- affected d1ad8fe7f72d73e1617bac79f2ec7a3bedf47e2a
- affected 6.6.143 – < 6.6.158
- affected 6.12.93 – < 6.12.112
- affected 6.18.17 – < 6.18.55
- affected 6.19.7 – < 6.20
- affected 7.0
- unaffected < 7.0
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.112 – ≤ 6.12.*
- unaffected 6.18.55 – ≤ 6.18.*
- unaffected 7.2.9 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References5
- https://git.kernel.org/stable/c/fddc90d4af4550af410f52d11bbf6b5f36443838 (opens in a new tab)
- https://git.kernel.org/stable/c/0b04af3d88bb7fc69b2d92457890608860e42365 (opens in a new tab)
- https://git.kernel.org/stable/c/b17aa4955e3a694c663ebe99626e4c76ca4f7cfb (opens in a new tab)
- https://git.kernel.org/stable/c/9b583795feb51f8d50203228d001760d1344ef01 (opens in a new tab)
- https://git.kernel.org/stable/c/bb756b11ad63832ebee58caf9e8f9381eaecff9f (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-108887 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98923)Record last updated .