CVE-2026-72152

Received Received - Intake

TPM SPI Driver Race Condition in Linux Kernel

Publication date: 2026-08-15

Last updated on: 2026-08-23

Assigner: kernel.org

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-15

Last Modified

2026-08-23

Generated

2026-09-04

AI Q&A

2026-08-15

EPSS Evaluated

2026-09-03

NVD

CVE-2026-72152

EUVD

EUVD-2026-58910

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability in the Linux kernel involves a race condition in the TPM (Trusted Platform Module) SPI driver. The issue occurs because wait_event_interruptible_timeout() sets the task state to TASK_INTERRUPTIBLE before checking its condition, which can trigger a warning under CONFIG_DEBUG_ATOMIC_SLEEP when used in an IRQ wait path. The fix involves using wait_woken() instead to properly handle waiting for TPM status changes.

Detection Guidance

This vulnerability is specific to the Linux kernel's TPM SPI driver and may not have direct network detection methods. Check kernel logs for warnings related to tpm_tis_spi or CONFIG_DEBUG_ATOMIC_SLEEP triggers. Use commands like dmesg | grep -i tpm or journalctl -k | grep -i tpm to inspect TPM-related errors.

Impact Analysis

This vulnerability could lead to system instability or unexpected warnings during TPM operations, particularly in systems using SPI-based TPM devices. While it may not directly cause data breaches, it could affect the reliability of security features that depend on TPM, such as secure boot or disk encryption.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards as it pertains to a low-level kernel issue in the TPM SPI driver. Compliance impacts would depend on system-specific configurations and usage rather than this bug itself.

Mitigation Strategies

Update the Linux kernel to a patched version that includes the fix for CVE-2026-72152. Monitor kernel updates from your distribution and apply them promptly. If immediate patching is not possible, consider disabling the TPM SPI driver if not required.

Hi! I’m here to help you understand CVE-2026-72152. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70