CVE-2026-97909: ASoC: sti: initialize IRQ lock before requesting IRQ

CVE-2026-97909: ASoC: sti: initialize IRQ lock before requesting IRQ

[Greg Kroah-Hartman]

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

ASoC: sti: initialize IRQ lock before requesting IRQ

uni_reader_init() registers the shared IRQ before initializing
reader->irq_lock. A pending interrupt can invoke the handler while the
lock is still uninitialized.

Initialize the lock before registering the IRQ so the interrupt path
always sees valid lock state.

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


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

	Issue introduced in 4.11 with commit d05d862ead8eca5e7d4ccf82d39d9189579ee5b1 and fixed in 6.12.111 with commit f1e7b74512164314d0550ec5b62e3d40b95b0986
	Issue introduced in 4.11 with commit d05d862ead8eca5e7d4ccf82d39d9189579ee5b1 and fixed in 6.18.53 with commit 998ca92f69bc43499705016d02ffaf0663126d57
	Issue introduced in 4.11 with commit d05d862ead8eca5e7d4ccf82d39d9189579ee5b1 and fixed in 7.2.7 with commit a42dd4dae4c9191caa017cf54cc40b6bb125be65
	Issue introduced in 4.11 with commit d05d862ead8eca5e7d4ccf82d39d9189579ee5b1 and fixed in 7.3-rc3 with commit 04405aeef4f8d7bcac6dcb1947acafdb4420c2c3

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-97909
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:
	sound/soc/sti/uniperif_reader.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/f1e7b74512164314d0550ec5b62e3d40b95b0986
	https://git.kernel.org/stable/c/998ca92f69bc43499705016d02ffaf0663126d57
	https://git.kernel.org/stable/c/a42dd4dae4c9191caa017cf54cc40b6bb125be65
	https://git.kernel.org/stable/c/04405aeef4f8d7bcac6dcb1947acafdb4420c2c3