All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72152: tpm: tpm_tis_spi: Use wait_woken() in wait_for_tmp_stat()
Date: Sat, 15 Aug 2026 15:03:51 +0900	[thread overview]
Message-ID: <2026081534-CVE-2026-72152-2462@gregkh> (raw)

From: Greg Kroah-Hartman <gregkh@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.

The Linux kernel CVE team has assigned CVE-2026-72152 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 4.19 with commit 1a339b658d9dbe1471f67b78237cf8fa08bbbeb5 and fixed in 6.1.178 with commit c9acbe38797bc1aa3c22a1ab72452e210af6e0ff
	Issue introduced in 4.19 with commit 1a339b658d9dbe1471f67b78237cf8fa08bbbeb5 and fixed in 6.6.145 with commit 6b068a97958aa00a901a9b5083d74114b21f7b66
	Issue introduced in 4.19 with commit 1a339b658d9dbe1471f67b78237cf8fa08bbbeb5 and fixed in 6.12.97 with commit bb63a0530e8e6de3aaf29cd5ba487db2490128ef
	Issue introduced in 4.19 with commit 1a339b658d9dbe1471f67b78237cf8fa08bbbeb5 and fixed in 6.18.40 with commit ba33b4f9d3423accd2c91a0b0b0680cd589922f2
	Issue introduced in 4.19 with commit 1a339b658d9dbe1471f67b78237cf8fa08bbbeb5 and fixed in 7.1.5 with commit 4bb3e1bc142dc9c3240ceed1b3ab031aa9cb1723
	Issue introduced in 4.19 with commit 1a339b658d9dbe1471f67b78237cf8fa08bbbeb5 and fixed in 7.2-rc1 with commit c0c9cfb3b75def8bf200a2d4db09015806acfeaf
	Issue introduced in 4.9.128 with commit cd4ae0b05126cc9461a2e50ccb745e5583cc91e2
	Issue introduced in 4.14.71 with commit cf503dbe5c22c6ab9797e1cf864a11597d711c3a
	Issue introduced in 4.18.9 with commit d229e7ecc0cb29996688f0fa98c5eb6128b81e3a

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-72152
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/char/tpm/tpm_tis_core.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/c9acbe38797bc1aa3c22a1ab72452e210af6e0ff
	https://git.kernel.org/stable/c/6b068a97958aa00a901a9b5083d74114b21f7b66
	https://git.kernel.org/stable/c/bb63a0530e8e6de3aaf29cd5ba487db2490128ef
	https://git.kernel.org/stable/c/ba33b4f9d3423accd2c91a0b0b0680cd589922f2
	https://git.kernel.org/stable/c/4bb3e1bc142dc9c3240ceed1b3ab031aa9cb1723
	https://git.kernel.org/stable/c/c0c9cfb3b75def8bf200a2d4db09015806acfeaf

                 reply	other threads:[~2026-08-15  6:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2026081534-CVE-2026-72152-2462@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cve@kernel.org \
    --cc=gregkh@kernel.org \
    --cc=linux-cve-announce@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.