From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72486: mailbox: mtk-adsp: fix UAF during device teardown
Date: Sat, 15 Aug 2026 15:09:25 +0900 [thread overview]
Message-ID: <2026081538-CVE-2026-72486-4bac@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
mailbox: mtk-adsp: fix UAF during device teardown
When the SOF audio driver fails to initialize (e.g. firmware boot
timeout), its devres unwind frees the snd_sof_dev object that the
mailbox client (mtk-adsp-ipc) reaches via chan->cl->rx_callback.
The mtk-adsp-mailbox shutdown clears the mailbox command registers
but leaves the IRQ line unmasked, so a late interrupt can still
queue a threaded handler after mbox_free_channel() had cleared
chan->cl, and mbox_chan_received_data() would then trigger UAF:
BUG: KASAN: slab-use-after-free in sof_ipc3_validate_fw_version
sof_ipc3_validate_fw_version
sof_ipc3_do_rx_work
sof_ipc3_rx_msg
mt8196_dsp_handle_request
mtk_adsp_ipc_recv
mbox_chan_received_data
mtk_adsp_mbox_isr
irq_thread_fn
Freed by task ...:
kfree
devres_release_all
really_probe
... (sof-audio-of-mt8196 probe failure)
The crash was observed roughly three seconds after the failed probe.
disable_irq() in shutdown and enable_irq() in startup. disable_irq()
also waits for any in-flight interrupts, so by the time
mbox_free_channel() proceeds to clear chan->cl no rx_callback can run.
In addition, request the IRQ with IRQF_NO_AUTOEN so it stays masked
between probe and the first client bind — otherwise an early interrupt
can crash on chan->cl == NULL in mbox_chan_received_data().
The Linux kernel CVE team has assigned CVE-2026-72486 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.18 with commit af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 and fixed in 6.1.178 with commit b6337a08a63eef8efcffe3c01d479badda6bbbdb
Issue introduced in 5.18 with commit af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 and fixed in 6.6.145 with commit e519c1d8c5efb5cd8d4c5bb3fe39b1bbb812bdb9
Issue introduced in 5.18 with commit af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 and fixed in 6.12.97 with commit fc6c3deb1d4c0adebf7dee0b8af4082af3f17690
Issue introduced in 5.18 with commit af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 and fixed in 6.18.40 with commit 7d881615fb6373f71fc628b3f00186aeca87a3d5
Issue introduced in 5.18 with commit af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 and fixed in 7.1.5 with commit 25d6ea6c76e1b1b7c57337b2f8f1b6fc8d5c52bc
Issue introduced in 5.18 with commit af2dfa96c52d042df5deb29fb6e32d3ff4d76a61 and fixed in 7.2-rc1 with commit b57d1a40bc43258372fa1f4d39305e093947a262
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-72486
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/mailbox/mtk-adsp-mailbox.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/b6337a08a63eef8efcffe3c01d479badda6bbbdb
https://git.kernel.org/stable/c/e519c1d8c5efb5cd8d4c5bb3fe39b1bbb812bdb9
https://git.kernel.org/stable/c/fc6c3deb1d4c0adebf7dee0b8af4082af3f17690
https://git.kernel.org/stable/c/7d881615fb6373f71fc628b3f00186aeca87a3d5
https://git.kernel.org/stable/c/25d6ea6c76e1b1b7c57337b2f8f1b6fc8d5c52bc
https://git.kernel.org/stable/c/b57d1a40bc43258372fa1f4d39305e093947a262
reply other threads:[~2026-08-15 6:30 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=2026081538-CVE-2026-72486-4bac@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.