From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80942: wifi: rtlwifi: rtl8192du: Fix possible memory leak in rtl92du_init_sw_vars()
Date: Fri, 11 Sep 2026 21:40:48 +0200 [thread overview]
Message-ID: <2026091137-CVE-2026-80942-6e4c@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
wifi: rtlwifi: rtl8192du: Fix possible memory leak in rtl92du_init_sw_vars()
The memory allocated inside rtl92du_init_shared_data() is not freed in
any of the subsequent error paths in rtl92du_init_sw_vars().
Fix that by adding a call to rtl92du_deinit_shared_data() in the error
path.
The Linux kernel CVE team has assigned CVE-2026-80942 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.11 with commit b5dc8873b6ffebd331e46814e537179eac8b6aa4 and fixed in 6.12.109 with commit 3a5b23e7dbeb00c93ec3b8add97f5de9bb9cbb5c
Issue introduced in 6.11 with commit b5dc8873b6ffebd331e46814e537179eac8b6aa4 and fixed in 6.18.50 with commit dc8b0be0ec4d9b0c80f07b27e656e4a94de5a344
Issue introduced in 6.11 with commit b5dc8873b6ffebd331e46814e537179eac8b6aa4 and fixed in 7.2.4 with commit 7159e1e12468a0b1ac519b296280c0a27f91eab5
Issue introduced in 6.11 with commit b5dc8873b6ffebd331e46814e537179eac8b6aa4 and fixed in 7.3-rc1 with commit 6496ce90845df2d22fb8e8ed235cd2936fad41c8
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-80942
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/rtl8192du/sw.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/3a5b23e7dbeb00c93ec3b8add97f5de9bb9cbb5c
https://git.kernel.org/stable/c/dc8b0be0ec4d9b0c80f07b27e656e4a94de5a344
https://git.kernel.org/stable/c/7159e1e12468a0b1ac519b296280c0a27f91eab5
https://git.kernel.org/stable/c/6496ce90845df2d22fb8e8ed235cd2936fad41c8
reply other threads:[~2026-09-11 19:46 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=2026091137-CVE-2026-80942-6e4c@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.