CVE-2026-72152

tpm: tpm_tis_spi: Use wait_woken() in wait_for_tmp_stat()

N/A
Published: August 15, 2026 at 05:53 AM UTC
Updated: August 23, 2026 at 01:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: tpm: tpm_tis_spi: Use wait_woken() in wait_for_tmp_stat() wait_event_interruptible_timeout() evaluates its condition after setting the current task state to TASK_INTERRUPTIBLE. With CONFIG_DEBUG_ATOMIC_SLEEP this triggers a warning when the IRQ wait path is used: tpm_tis_status() tpm_tis_spi_read_bytes() tpm_tis_spi_transfer_full() spi_bus_lock() mutex_lock() Address this with the following measures: 1. Call wait_tpm_stat_cond() only while tasking is running. 2. Use wait_woken() to wait for changes.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 4.14.71v ≥ 4.18.9v ≥ 4.9.1284.14.71 ≤ v < 4.154.18.9 ≤ v < 4.194.19 ≤ v < 5.10.2664.19 ≤ v < 5.15.2174.19 ≤ v < 6.1.1784.19 ≤ v < 6.12.974.19 ≤ v < 6.18.404.19 ≤ v < 6.6.1454.19 ≤ v < 7.1.54.19 ≤ v < 7.24.9.128 ≤ v < 4.101a339b658d9dbe1471f67b78237cf8fa08bbbeb54.14.714.18.94.194.9.128cd4ae0b05126cc9461a2e50ccb745e5583cc91e2cf503dbe5c22c6ab9797e1cf864a11597d711c3ad229e7ecc0cb29996688f0fa98c5eb6128b81e3a
Vendor states this is fixed in 45ceeb08bf1f4f7353ffb529d8682a0cf5506318 (fixed)
Vendor states this is fixed in 4bb3e1bc142dc9c3240ceed1b3ab031aa9cb1723 (fixed)
Vendor states this is fixed in 6b068a97958aa00a901a9b5083d74114b21f7b66 (fixed)
Vendor states this is fixed in ba33b4f9d3423accd2c91a0b0b0680cd589922f2 (fixed)
Vendor states this is fixed in bb63a0530e8e6de3aaf29cd5ba487db2490128ef (fixed)
Vendor states this is fixed in c0c9cfb3b75def8bf200a2d4db09015806acfeaf (fixed)
Vendor states this is fixed in c9acbe38797bc1aa3c22a1ab72452e210af6e0ff (fixed)
Vendor states this is fixed in eef71c01deb08547956df3634a0d34c6bdbcecb8 (fixed)
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.19 (unaffected)
Vendor states this is fixed in 5.10.266 (unaffected)
Vendor states this is fixed in 5.15.217 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card