data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-72152 in the interactive tracker

CVE-2026-72152

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

EPSS 0.2%

Published 2026-08-15 (2 months ago) by the Linux kernel CNA. Subsystem drivers/char. Debian urgency: not yet assigned.

What to do, per Debian release

Debian's own status for CVE-2026-72152 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormfixed6.1.180-1Update the kernel and reboot. Fixed in 6.1.180-1. A running kernel keeps the old code until the machine restarts.
Debian 13trixiefixed6.12.100-1Update the kernel and reboot. Fixed in 6.12.100-1. A running kernel keeps the old code until the machine restarts.
Debian 14forkyfixed7.1.5-1Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed7.1.5-1Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

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.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

drivers/char/tpm/tpm_tis_core.c

What this is
TPM DEVICE DRIVERMAINTAINERS section matched on drivers/char/tpm/ · linux-integrity@vger.kernel.org · Maintained
Kernel module
tpm_tis_core

Check it on the machine

grep -wE 'CONFIG_TCG_TIS_CORE|CONFIG_TCG_TPM' /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

lsmod | grep -w tpm_tis_core

Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.

Show whether Debian builds this, per release

Debian builds this code. Every release below compiles the affected file into the kernels it ships.

  • bookworm, trixie, forky, sidb
b
built in on some flavours, a module on others
Build switches
CONFIG_TCG_TIS_CORE, CONFIG_TCG_TPM
Reads as
all on means the file is compiled; any one off means it is not.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published
2026-08-15 (2 months ago)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
0.22%, higher than 11.2% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
not yet assignedsource
Subsystem
drivers/char

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
4.195.10.26645ceeb08bf1f
4.195.15.217eef71c01deb0
4.196.1.178c9acbe38797b
4.196.6.1456b068a97958a
4.196.12.97bb63a0530e8e
4.196.18.40ba33b4f9d342
4.197.1.54bb3e1bc142d
4.197.2c0c9cfb3b75d
4.9.12800
4.14.7100
4.18.900

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2026-72152, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.