Kernel-level memory mapping bug could destabilize or disrupt Linux deployments globally.
CVE-2026-46115
Kernel bio merge across pgmaps may coalesce bvecs from different pgmaps.
Is CVE-2026-46115 being exploited?
Not confirmed. CVE-2026-46115 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.49% probability of exploitation in the next 30 days.
How severe is CVE-2026-46115?
CVE-2026-46115 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-46115?
Yes. A fix has been recorded for CVE-2026-46115. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-46115 affect?
CVE-2026-46115 affects Linux kernel. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-46115?
Apply patched kernel; reboot after update
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Memory mapping could be incorrect after coalescing bvecs from multiple pgmaps; risk of kernel crash or data corruption via DMA.
Patch when possible
- affected>= 49580e690755d0e51ed7aa2c33225dd884fa738a and < 3d2ecbd444b01d6500671d1a582b7393943cf539
- affected>= 49580e690755d0e51ed7aa2c33225dd884fa738a and < a7f3aa8c9df3905fe820ae36b67ba56b81587574
- affected>= 49580e690755d0e51ed7aa2c33225dd884fa738a and < f17d521075325b8afc42d1baa1c28a5e9aca111f
- affected>= 49580e690755d0e51ed7aa2c33225dd884fa738a and < f632dab4b841554cd6416058c61886d7db176581
- affected>= 49580e690755d0e51ed7aa2c33225dd884fa738a and < 13920e4b7b784b40cf4519ff1f0f3e513476a499
- affected6.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.