# CVE-2026-72152: tpm: tpm_tis_spi: Use wait_woken() in wait_for_tmp_stat()

> A kernel bug in the TPM SPI driver causes warnings and potential instability when debug options are enabled, requiring a patch to fix.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 23 Aug 2026
- **Also known as:** BELL-CVE-2026-72152, DEBIAN-CVE-2026-72152, GHSA-f425-2m93-59fc, UBUNTU-CVE-2026-72152

## What is CVE-2026-72152?

CVE-2026-72152 is a denial of service vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-72152?


## How do I fix CVE-2026-72152?

Apply the vendor's patch.

## Is CVE-2026-72152 being exploited?

There is no known exploitation of CVE-2026-72152 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-72152 and fix it if it is affected.

What it is: CVE-2026-72152 is a denial of service vulnerability in Linux, published on 15 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72152 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-72152/ (Markdown: https://insights.sbomify.com/CVE-2026-72152/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-72152
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-72152
- OSV: https://osv.dev/vulnerability/CVE-2026-72152

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-72152/
Summaries are generated and may contain mistakes; the official description above is the record.