CVE-2026-72152: Linux kernel · tpm: tpm_tis_spi: Use wait_woken() in wait_for_tmp_stat()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in eef71c01deb08547956df3634a0d34c6bdbcecb8 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 17:19 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
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 eef71c01deb08547956df3634a0d34c6bdbcecb8, c9acbe38797bc1aa3c22a1ab72452e210af6e0ff, c0c9cfb3b75def8bf200a2d4db09015806acfeaf +8
Exploitation evidence
Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
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.
References
- git.kernel.org/stable/c/45ceeb08bf1f4f7353ffb529d8682a0cf5506318 (opens in a new tab)
- git.kernel.org/stable/c/eef71c01deb08547956df3634a0d34c6bdbcecb8 (opens in a new tab)
- git.kernel.org/stable/c/c9acbe38797bc1aa3c22a1ab72452e210af6e0ff (opens in a new tab)
- git.kernel.org/stable/c/6b068a97958aa00a901a9b5083d74114b21f7b66 (opens in a new tab)
- git.kernel.org/stable/c/bb63a0530e8e6de3aaf29cd5ba487db2490128ef (opens in a new tab)
- git.kernel.org/stable/c/ba33b4f9d3423accd2c91a0b0b0680cd589922f2 (opens in a new tab)
- git.kernel.org/stable/c/4bb3e1bc142dc9c3240ceed1b3ab031aa9cb1723 (opens in a new tab)
- git.kernel.org/stable/c/c0c9cfb3b75def8bf200a2d4db09015806acfeaf (opens in a new tab)