Quick answers
- Is CVE-2026-98923 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-98923 being exploited in the wild.
- How severe is CVE-2026-98923?
- Informational severity, published 23 October 2026.
- Which products and versions are affected?
- Linux kernel Multiple versions prior to fix commit bb756b11ad63832ebee58caf9e8f9381eaecff9f.
- Is there a fix for CVE-2026-98923?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-98923 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-98923?
- Check whether you run Linux kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A spurious WARN_ON_ONCE() fires in ioremap_prot() when generic_access_phys() passes user page table entries with PROT_NONE or execute-only protections that lack the PTE_USER bit set. The fix changes the warning to a silent rejection, preventing the warning while maintaining the user-protection contract by cleanly failing such accesses.
Affected products
- Linux kernel Multiple versions prior to fix commit bb756b11ad63832ebee58caf9e8f9381eaecff9f
Timeline
- 2026-10-23: disclosed