Skip to main content
VulnerabilityPublished Updated

CVE-2026-45871: Linux kernel · tpm: st33zp24: Fix missing cleanup on get_burstcount() error

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in ec15eb67fe9df87981b4829b901ec254273ca483 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:06 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in ec15eb67fe9df87981b4829b901ec254273ca483, e0ce3da82341fcd6194175f1837946b2a894c625, cc09d55f519e15355de343264a22ac6682b8305e +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ bf38b8710892333cec2d8069644eb36ff435fd6f, < ec15eb67fe9df87981b4829b901ec254273ca483
Fixed in
  • ec15eb67fe9df87981b4829b901ec254273ca483
LinuxLinuxAffected
  • ≥ bf38b8710892333cec2d8069644eb36ff435fd6f, < e0ce3da82341fcd6194175f1837946b2a894c625
Fixed in
  • e0ce3da82341fcd6194175f1837946b2a894c625
LinuxLinuxAffected
  • ≥ bf38b8710892333cec2d8069644eb36ff435fd6f, < cc09d55f519e15355de343264a22ac6682b8305e
Fixed in
  • cc09d55f519e15355de343264a22ac6682b8305e
LinuxLinuxAffected
  • ≥ bf38b8710892333cec2d8069644eb36ff435fd6f, < a51cff9be046e13e1c1b2fe45d5c48b582ec9b8c
Fixed in
  • a51cff9be046e13e1c1b2fe45d5c48b582ec9b8c
LinuxLinuxAffected
  • ≥ bf38b8710892333cec2d8069644eb36ff435fd6f, < 7687133509cf66ced120b667fefd21f80bf17993
Fixed in
  • 7687133509cf66ced120b667fefd21f80bf17993
LinuxLinuxAffected
  • ≥ bf38b8710892333cec2d8069644eb36ff435fd6f, < 1256c6dc96d1e687e6e9b63088156ed07411b00c
Fixed in
  • 1256c6dc96d1e687e6e9b63088156ed07411b00c

AI-suggested

A fix is available in the Linux kernel as indicated by the fixed commit versions. Users should update to a kernel version that includes these fixes to ensure proper cleanup on get_burstcount() errors.

Description

A vulnerability in the Linux kernel's TPM driver for the ST33ZP24 chip was fixed. The issue involved missing cleanup when get_burstcount() returned an error, causing the function st33zp24_send() to return without releasing a previously acquired locality. This could lead to resource locking issues.

References

Community reviews

Loading reviews…