From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72258: ASoC: mediatek: mt8183: Release reserved memory on cleanup
Date: Sat, 15 Aug 2026 15:05:37 +0900 [thread overview]
Message-ID: <2026081554-CVE-2026-72258-538c@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ASoC: mediatek: mt8183: Release reserved memory on cleanup
The MT8183 AFE probe can assign reserved memory with
of_reserved_mem_device_init(), but the assignment is never released on
driver removal or later probe failures.
Register a devm cleanup action so the reserved memory assignment is
released consistently, matching newer Mediatek AFE drivers.
The Linux kernel CVE team has assigned CVE-2026-72258 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.6.102 with commit aa771d2928fedd7fb10aa373601eeee0ed8ccfae and fixed in 6.6.145 with commit 48b6c39883637b444c2f976e7b8ca964b1889561
Issue introduced in 6.12.42 with commit 3b13b5a4f29e50bbc3c464823cf8c94b93a16367 and fixed in 6.12.97 with commit e2d05ab62614162797fee28925279d9e8c2f200a
Issue introduced in 6.17 with commit ec4a10ca4a68ec97f12f4d17d7abb74db34987db and fixed in 6.18.40 with commit e42d8322b67f21493a832ec338aad1c93bd01ea7
Issue introduced in 6.17 with commit ec4a10ca4a68ec97f12f4d17d7abb74db34987db and fixed in 7.1.5 with commit 03009465312ca35137f84cf84c95686137608deb
Issue introduced in 6.17 with commit ec4a10ca4a68ec97f12f4d17d7abb74db34987db and fixed in 7.2-rc1 with commit bee65e00c0924ebecf97718d95dcf4a05ee36471
Issue introduced in 6.15.10 with commit c2ab521120eb83103bc5927bb7b7aa84043f495f
Issue introduced in 6.16.1 with commit 40bff79f167ff700cf1f203b1ad54b389d0e7189
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-72258
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/mediatek/mt8183/mt8183-afe-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/48b6c39883637b444c2f976e7b8ca964b1889561
https://git.kernel.org/stable/c/e2d05ab62614162797fee28925279d9e8c2f200a
https://git.kernel.org/stable/c/e42d8322b67f21493a832ec338aad1c93bd01ea7
https://git.kernel.org/stable/c/03009465312ca35137f84cf84c95686137608deb
https://git.kernel.org/stable/c/bee65e00c0924ebecf97718d95dcf4a05ee36471
reply other threads:[~2026-08-15 6:21 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=2026081554-CVE-2026-72258-538c@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.