From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72133: spi: uniphier: Fix completion initialization order before devm_request_irq()
Date: Sat, 15 Aug 2026 15:03:32 +0900 [thread overview]
Message-ID: <2026081530-CVE-2026-72133-a965@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
spi: uniphier: Fix completion initialization order before devm_request_irq()
The driver calls devm_request_irq() before initializing the completion
used by the interrupt handler. Because the interrupt may occur immediately
after devm_request_irq(), the handler may execute before init_completion().
This may result in calling complete() on an uninitialized completion,
causing undefined behavior. This has been observed with KASAN.
Fix this by initializing the completion before registering the IRQ.
The Linux kernel CVE team has assigned CVE-2026-72133 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.19 with commit 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and fixed in 5.10.261 with commit b9fcf0db433d79648ace74bc2b8b88f91e306304
Issue introduced in 4.19 with commit 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and fixed in 5.15.212 with commit 82a5746c4c9e94f6f816ec7edea6ddc24417c6a5
Issue introduced in 4.19 with commit 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and fixed in 6.1.178 with commit f4bb0a91f7badd6d15ac8d783a1169d9e1e95c17
Issue introduced in 4.19 with commit 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and fixed in 6.6.145 with commit 49f6705d80b5e6175d8435d9c72b66bd516a8e89
Issue introduced in 4.19 with commit 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and fixed in 6.12.97 with commit 8b5798ce0007874c14611b8ee4ce6c749855260e
Issue introduced in 4.19 with commit 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and fixed in 6.18.40 with commit d44b828eb551bd59ba9f22457825cc3db3a39fc1
Issue introduced in 4.19 with commit 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and fixed in 7.1.5 with commit 077a7bc1c32d3da9670c5e282ea3e5ac8a94be59
Issue introduced in 4.19 with commit 5ba155a4d4cc8e4cdd3db6df7d03271a3bd91177 and fixed in 7.2-rc1 with commit f3ad1c87d8201e54b66bd6072442f0b5d5a308ee
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-72133
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/spi/spi-uniphier.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/b9fcf0db433d79648ace74bc2b8b88f91e306304
https://git.kernel.org/stable/c/82a5746c4c9e94f6f816ec7edea6ddc24417c6a5
https://git.kernel.org/stable/c/f4bb0a91f7badd6d15ac8d783a1169d9e1e95c17
https://git.kernel.org/stable/c/49f6705d80b5e6175d8435d9c72b66bd516a8e89
https://git.kernel.org/stable/c/8b5798ce0007874c14611b8ee4ce6c749855260e
https://git.kernel.org/stable/c/d44b828eb551bd59ba9f22457825cc3db3a39fc1
https://git.kernel.org/stable/c/077a7bc1c32d3da9670c5e282ea3e5ac8a94be59
https://git.kernel.org/stable/c/f3ad1c87d8201e54b66bd6072442f0b5d5a308ee
reply other threads:[~2026-08-15 6:14 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=2026081530-CVE-2026-72133-a965@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.