CVE-2026-72298
32-bit Linux QRTR integer overflow allows OOB write and kernel crash
Is CVE-2026-72298 being exploited?
Not confirmed. CVE-2026-72298 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.18% probability of exploitation in the next 30 days.
How severe is CVE-2026-72298?
CVE-2026-72298 is rated High. 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-72298?
Yes. A fix has been recorded for CVE-2026-72298. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72298 affect?
CVE-2026-72298 affects Linux kernel (QRTR module) on 32-bit architectures, Embedded/IoT/Qualcomm-based devices using 32-bit Linux, Any vendor kernels bundling the vulnerable QRTR code. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72298?
Apply vendor/kernel updates with the QRTR fix or disable/isolate QRTR on 32-bit devices
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote crafted QRTR packet can trigger 32-bit integer overflow causing OOB kernel write leading to kernel panic (DoS) and possible kernel memory corruption/execution on 32-bit systems.
Patch when possible
- affected>= 960b08dd36de1e341e3eb43d1c547513e338f4f8 and < 3665e644ea081c4624a1637023b0de3b29f4ae04
- affected>= ad9d24c9429e2159d1e279dc3a83191ccb4daf1d and < b609f7f46916c6b05585ca82455077198a23770f
- affected>= ad9d24c9429e2159d1e279dc3a83191ccb4daf1d and < 242408b5b763c01288adf3113cbce84378a76e1a
- affected>= ad9d24c9429e2159d1e279dc3a83191ccb4daf1d and < d0597074e99731fdad5593e4f6d056a3866f2cab
- affected>= ad9d24c9429e2159d1e279dc3a83191ccb4daf1d and < 689b7267f8632b4661879dc323e26ebb60978afb
- affected>= ad9d24c9429e2159d1e279dc3a83191ccb4daf1d and < 22100a8f73d4ae4f17697dae93d4e2e1d283a6ec
- affected>= ad9d24c9429e2159d1e279dc3a83191ccb4daf1d and < 7f72c285f6d3bf63968a0344beee8ab1b370198b
- affected>= ad9d24c9429e2159d1e279dc3a83191ccb4daf1d and < 20054869770c7df060c5ecee3e8bbf9029c47191
- affectedf8111c0d7ed42ede41a3d0d393b104de0730a8a6
- affected26b8d10703a9be45d6097946b2b4011f7dd2c56f
- affected19892ab9c9d838e2e5a7744d36e4bb8b7c3292fe
- affected>= 5.10.46 and < 5.10.261
- affected>= 4.19.196 and < 4.20
- affected>= 5.4.128 and < 5.5
- affected>= 5.12.13 and < 5.13
- affected5.13
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.