CVE-2026-72151
Linux kernel TPM KPP async use-after-free may cause kernel crash or privilege escalation
Is CVE-2026-72151 being exploited?
Not confirmed. CVE-2026-72151 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-72151?
CVE-2026-72151 is rated High with a CVSS score of 8.4. 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-72151?
Yes. A fix has been recorded for CVE-2026-72151. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72151 affect?
CVE-2026-72151 affects Linux kernel (tpm2-sessions), atmel-ecc, HPRE, keembay-ocs, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72151?
Install vendor kernel security updates that fix tpm2-sessions KPP async handling.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Async KPP backends can dereference a freed kpp_request causing kernel memory corruption, enabling local DoS or potential privilege escalation.
Patch when possible
- affected>= 1085b8276bb4239daa7008f0dcd5c973e4bd690f and < 111e520efbe82b324bc42b1999b723c0619eea6d
- affected>= 1085b8276bb4239daa7008f0dcd5c973e4bd690f and < 934d1cd40e2893bf7a041b54f6afd1c008d7a21c
- affected>= 1085b8276bb4239daa7008f0dcd5c973e4bd690f and < 493333f167926c7adab8e7563e21ad71d8af84fa
- affected>= 1085b8276bb4239daa7008f0dcd5c973e4bd690f and < 73851a7c43dfa52d2ed9415889b33daf85da0ed9
- affected6.10
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.