From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2023-53808: wifi: mwifiex: fix memory leak in mwifiex_histogram_read()
Date: Tue, 9 Dec 2025 09:02:29 +0900 [thread overview]
Message-ID: <2025120944-CVE-2023-53808-e169@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
wifi: mwifiex: fix memory leak in mwifiex_histogram_read()
Always free the zeroed page on return from 'mwifiex_histogram_read()'.
The Linux kernel CVE team has assigned CVE-2023-53808 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.0 with commit cbf6e05527a7654ac1c4f4787dfd7a182fcc0c73 and fixed in 4.14.326 with commit d3b53ac2b60283f84bcc650aaa8af98500f37b56
Issue introduced in 4.0 with commit cbf6e05527a7654ac1c4f4787dfd7a182fcc0c73 and fixed in 4.19.295 with commit 7be90670b967d11f53a9d45bc88fa8ac9daf9709
Issue introduced in 4.0 with commit cbf6e05527a7654ac1c4f4787dfd7a182fcc0c73 and fixed in 5.4.257 with commit 8f717752f94efae84853e17f2589665c330a0cf5
Issue introduced in 4.0 with commit cbf6e05527a7654ac1c4f4787dfd7a182fcc0c73 and fixed in 5.10.195 with commit 0c4240d23db525208fd40dd6371ca3254fa1b93d
Issue introduced in 4.0 with commit cbf6e05527a7654ac1c4f4787dfd7a182fcc0c73 and fixed in 5.15.132 with commit 308eb3a609ac39ca9c3e466b35e8825007c8d826
Issue introduced in 4.0 with commit cbf6e05527a7654ac1c4f4787dfd7a182fcc0c73 and fixed in 6.1.53 with commit 84081b4baafb49211193c6a056d5aee9c0e6ab8e
Issue introduced in 4.0 with commit cbf6e05527a7654ac1c4f4787dfd7a182fcc0c73 and fixed in 6.4.16 with commit 5d66b32a6ecf2e2e1a9523eaa4f8b314832fe06c
Issue introduced in 4.0 with commit cbf6e05527a7654ac1c4f4787dfd7a182fcc0c73 and fixed in 6.5.3 with commit f76e1da838377777557d78dfeb6d8c532f7118be
Issue introduced in 4.0 with commit cbf6e05527a7654ac1c4f4787dfd7a182fcc0c73 and fixed in 6.6 with commit 9c8fd72a5c2a031cbc680a2990107ecd958ffcdb
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-53808
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/marvell/mwifiex/debugfs.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/d3b53ac2b60283f84bcc650aaa8af98500f37b56
https://git.kernel.org/stable/c/7be90670b967d11f53a9d45bc88fa8ac9daf9709
https://git.kernel.org/stable/c/8f717752f94efae84853e17f2589665c330a0cf5
https://git.kernel.org/stable/c/0c4240d23db525208fd40dd6371ca3254fa1b93d
https://git.kernel.org/stable/c/308eb3a609ac39ca9c3e466b35e8825007c8d826
https://git.kernel.org/stable/c/84081b4baafb49211193c6a056d5aee9c0e6ab8e
https://git.kernel.org/stable/c/5d66b32a6ecf2e2e1a9523eaa4f8b314832fe06c
https://git.kernel.org/stable/c/f76e1da838377777557d78dfeb6d8c532f7118be
https://git.kernel.org/stable/c/9c8fd72a5c2a031cbc680a2990107ecd958ffcdb
reply other threads:[~2025-12-09 0:04 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=2025120944-CVE-2023-53808-e169@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.