[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2026011345-CVE-2025-71100-537f@gregkh>
Date: Tue, 13 Jan 2026 16:35:59 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-71100: wifi: rtlwifi: 8192cu: fix tid out of range in rtl92cu_tx_fill_desc()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
wifi: rtlwifi: 8192cu: fix tid out of range in rtl92cu_tx_fill_desc()
TID getting from ieee80211_get_tid() might be out of range of array size
of sta_entry->tids[], so check TID is less than MAX_TID_COUNT. Othwerwise,
UBSAN warn:
UBSAN: array-index-out-of-bounds in drivers/net/wireless/realtek/rtlwifi/rtl8192cu/trx.c:514:30
index 10 is out of range for type 'rtl_tid_data [9]'
The Linux kernel CVE team has assigned CVE-2025-71100 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.9 with commit 8ca4cdef93297c9b9bf08da39bc940bd20acbb94 and fixed in 6.12.64 with commit 9765d6eb8298b07d499cdf9ef7c237d3540102d6
Issue introduced in 6.9 with commit 8ca4cdef93297c9b9bf08da39bc940bd20acbb94 and fixed in 6.18.4 with commit 90a15ff324645aa806d81fa349497cd964861b66
Issue introduced in 6.9 with commit 8ca4cdef93297c9b9bf08da39bc940bd20acbb94 and fixed in 6.19-rc4 with commit dd39edb445f07400e748da967a07d5dca5c5f96e
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-2025-71100
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/realtek/rtlwifi/rtl8192cu/trx.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/9765d6eb8298b07d499cdf9ef7c237d3540102d6
https://git.kernel.org/stable/c/90a15ff324645aa806d81fa349497cd964861b66
https://git.kernel.org/stable/c/dd39edb445f07400e748da967a07d5dca5c5f96e
Powered by blists - more mailing lists