CVE-2026-64153
Linux kernel drm/msm IOMMU return-value bug can cause kernel WARN/DoS.
Is CVE-2026-64153 being exploited?
Not confirmed. CVE-2026-64153 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.14% probability of exploitation in the next 30 days.
How severe is CVE-2026-64153?
CVE-2026-64153 is rated High with a CVSS score of 8.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-64153?
Yes. A fix has been recorded for CVE-2026-64153. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-64153 affect?
CVE-2026-64153 affects Linux kernel (drm/msm), Qualcomm MSM GPU drivers, Devices running affected kernels (embedded/Android/servers using msm drivers). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-64153?
Apply vendor/kernel patch or update to patched kernel and reboot affected systems.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Improper IOMMU mapping error handling can trigger kernel WARN/oops causing local denial-of-service; may enable privilege escalation via driver interfaces.
Patch when possible
- affected>= ad8f36e4b6b1c826a0daa5fda2c5839205b5aa8b and < 3c2cdb7c07f664b77e2a75b50793b845d5742efa
- affected>= ad8f36e4b6b1c826a0daa5fda2c5839205b5aa8b and < 3e3c3c95ef4fe17231a9149e27bcfc9dae2dd89f
- affected>= ad8f36e4b6b1c826a0daa5fda2c5839205b5aa8b and < 7256e54583aee21e23929e7554278c2f5c1a08b1
- affected>= ad8f36e4b6b1c826a0daa5fda2c5839205b5aa8b and < 3457807aeb88077712f0a7cb65c3ca5120773d75
- affected>= ad8f36e4b6b1c826a0daa5fda2c5839205b5aa8b and < f4e37f3df436c2bdd2621c21f9c72c8f149a221d
- affected>= ad8f36e4b6b1c826a0daa5fda2c5839205b5aa8b and < 3a45af37733446e114bf19b0209fe7d8089bdb8b
- affected>= ad8f36e4b6b1c826a0daa5fda2c5839205b5aa8b and < 55e0f0d1c1a4ee1e46da7da4d443eb3044fb3851
- affected5.15
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.