Kernel warning via non-readable memory mappings
Published Oct 23, 2026 · Updated Oct 23, 2026
Incorrect warning handling in Linux arm64 ioremap_prot() allows local users to trigger a kernel warning via /dev/mem mappings. generic_access_phys() forwards protection bits from present-invalid PROT_NONE or execute-only page-table entries lacking PTE_USER, and ioremap_prot() warns before rejecting them. The trigger requires privileged /dev/mem access and reading the process's /proc//cmdline; it causes a warning by default and a kernel crash when panic_on_warn is enabled, not a demonstrated memory-read bypass.
Summary
What happened
Incorrect warning handling in Linux arm64 ioremap_prot() allows local users to trigger a kernel warning via /dev/mem mappings. generic_access_phys() forwards protection bits from present-invalid PROT_NONE or execute-only page-table entries lacking PTE_USER, and ioremap_prot() warns before rejecting them. The trigger requires privileged /dev/mem access and reading the process's /proc//cmdline; it causes a warning by default and a kernel crash when panic_on_warn is enabled, not a demonstrated memory-read bypass.
The record
- CVE
- CVE-2026-98923
- Published
- Oct 23, 2026
- Updated
- Oct 23, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Oct 23, 2026CVE publishedPublication date reported by the CVE source.
- Oct 23, 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=3d64dcc0799c2d6921ba027716b7be721eb19fa8 <b17aa4955e3a694c663ebe99626e4c76ca4f7cfb
- Affected versionversion=6.12.93 <6.12.112
- Affected versionversion=6.18.17 <6.18.55
- Affected versionversion=6.19.7 <6.20
- Affected versionversion=64858b76ec67c5fc40fef8ec1841fecb78c1ebde <fddc90d4af4550af410f52d11bbf6b5f36443838
- Affected versionversion=6.6.143 <6.6.158
- Affected versionversion=7.0
- Affected versionversion=8f098037139b294050053123ab2bc0f819d08932 <9b583795feb51f8d50203228d001760d1344ef01
- Affected versionversion=8f098037139b294050053123ab2bc0f819d08932 <bb756b11ad63832ebee58caf9e8f9381eaecff9f
- Affected versionversion=d1ad8fe7f72d73e1617bac79f2ec7a3bedf47e2a
- Affected versionversion=eeecafce5afffb4da703666ebefbd4d6e2a5abf6 <0b04af3d88bb7fc69b2d92457890608860e42365
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us