From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80743: ASoC: xilinx: formatter_pcm: pass aud_drv_data to irq handlers
Date: Thu, 3 Sep 2026 10:26:40 +0200 [thread overview]
Message-ID: <2026090337-CVE-2026-80743-14b5@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ASoC: xilinx: formatter_pcm: pass aud_drv_data to irq handlers
The irq handlers take a struct device pointer and call
dev_get_drvdata() to obtain the driver data. However, the driver
data is only set at the end of probe, after devm_request_irq(),
so an interrupt taken in between causes the handlers to pass a
NULL pointer to readl() and crash.
Pass the private data directly as the devm_request_irq() argument
instead of the device pointer, matching what the handlers expect.
The Linux kernel CVE team has assigned CVE-2026-80743 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.1 with commit 6f6c3c36f0917be24587eeba818ab4fdfcb5465a and fixed in 5.10.266 with commit 7d857aec162fb02d10ce326aecc1ac7509c31f43
Issue introduced in 5.1 with commit 6f6c3c36f0917be24587eeba818ab4fdfcb5465a and fixed in 5.15.217 with commit a85315f2eb06adc5597a7103e1910fc7d0d35ffd
Issue introduced in 5.1 with commit 6f6c3c36f0917be24587eeba818ab4fdfcb5465a and fixed in 6.1.184 with commit 721cfeb0b9572084435695ae535411b921d1ea68
Issue introduced in 5.1 with commit 6f6c3c36f0917be24587eeba818ab4fdfcb5465a and fixed in 6.6.153 with commit b4ef887bee4d3c177adac5d1eab8b2de31b08ac3
Issue introduced in 5.1 with commit 6f6c3c36f0917be24587eeba818ab4fdfcb5465a and fixed in 6.12.105 with commit 0d58a70b6dc7b65772e3ef7c43beb91882cf9ed5
Issue introduced in 5.1 with commit 6f6c3c36f0917be24587eeba818ab4fdfcb5465a and fixed in 6.18.46 with commit f51a540b14eecb8667bbe450192318271b87631e
Issue introduced in 5.1 with commit 6f6c3c36f0917be24587eeba818ab4fdfcb5465a and fixed in 7.1.10 with commit 09e4c486348e176c083f8bee9169ae8f408cf8d1
Issue introduced in 5.1 with commit 6f6c3c36f0917be24587eeba818ab4fdfcb5465a and fixed in 7.2 with commit f12afefb7b01f94d6d66d397f323a9914edbf70e
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-80743
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/xilinx/xlnx_formatter_pcm.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/7d857aec162fb02d10ce326aecc1ac7509c31f43
https://git.kernel.org/stable/c/a85315f2eb06adc5597a7103e1910fc7d0d35ffd
https://git.kernel.org/stable/c/721cfeb0b9572084435695ae535411b921d1ea68
https://git.kernel.org/stable/c/b4ef887bee4d3c177adac5d1eab8b2de31b08ac3
https://git.kernel.org/stable/c/0d58a70b6dc7b65772e3ef7c43beb91882cf9ed5
https://git.kernel.org/stable/c/f51a540b14eecb8667bbe450192318271b87631e
https://git.kernel.org/stable/c/09e4c486348e176c083f8bee9169ae8f408cf8d1
https://git.kernel.org/stable/c/f12afefb7b01f94d6d66d397f323a9914edbf70e
reply other threads:[~2026-09-03 8:27 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=2026090337-CVE-2026-80743-14b5@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.