From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2023-54052: wifi: mt76: mt7921: fix skb leak by txs missing in AMSDU
Date: Wed, 24 Dec 2025 13:26:45 +0100 [thread overview]
Message-ID: <2025122425-CVE-2023-54052-302d@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
wifi: mt76: mt7921: fix skb leak by txs missing in AMSDU
txs may be dropped if the frame is aggregated in AMSDU. When the problem
shows up, some SKBs would be hold in driver to cause network stopped
temporarily. Even if the problem can be recovered by txs timeout handling,
mt7921 still need to disable txs in AMSDU to avoid this issue.
The Linux kernel CVE team has assigned CVE-2023-54052 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.12 with commit 163f4d22c118d4eb9e275bf9ee1577c0d14b3208 and fixed in 6.1.52 with commit 1cd102aaedb277fbe81dd08cd9f5cae951de2bff
Issue introduced in 5.12 with commit 163f4d22c118d4eb9e275bf9ee1577c0d14b3208 and fixed in 6.4.15 with commit e74778e91fedc3b2a0143264887bbb32508c5000
Issue introduced in 5.12 with commit 163f4d22c118d4eb9e275bf9ee1577c0d14b3208 and fixed in 6.5.2 with commit bf5d3fad7219b8de7d3a9cb59f0ea5243b018f07
Issue introduced in 5.12 with commit 163f4d22c118d4eb9e275bf9ee1577c0d14b3208 and fixed in 6.6 with commit b642f4c5f3de0a8f47808d32b1ebd9c427a42a66
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-2023-54052
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/net/wireless/mediatek/mt76/mt76_connac_mac.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/1cd102aaedb277fbe81dd08cd9f5cae951de2bff
https://git.kernel.org/stable/c/e74778e91fedc3b2a0143264887bbb32508c5000
https://git.kernel.org/stable/c/bf5d3fad7219b8de7d3a9cb59f0ea5243b018f07
https://git.kernel.org/stable/c/b642f4c5f3de0a8f47808d32b1ebd9c427a42a66
reply other threads:[~2025-12-24 12:28 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=2025122425-CVE-2023-54052-302d@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.