From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49105: staging: wfx: fix an error handling in wfx_init_common()
Date: Wed, 26 Feb 2025 02:55:10 +0100 [thread overview]
Message-ID: <2025022601-CVE-2022-49105-b5ae@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
staging: wfx: fix an error handling in wfx_init_common()
One error handler of wfx_init_common() return without calling
ieee80211_free_hw(hw), which may result in memory leak. And I add
one err label to unify the error handler, which is useful for the
subsequent changes.
The Linux kernel CVE team has assigned CVE-2022-49105 to this issue.
Affected and fixed versions
===========================
Fixed in 5.10.111 with commit 93498c6e775ae91732a8109dba1bdcd324908f84
Fixed in 5.15.34 with commit 86efcb524ae1889ae73f2a2f0bb7fff2ec757ab0
Fixed in 5.16.20 with commit ab0fed1fa744173433cfd1dbaf9239f200ded650
Fixed in 5.17.3 with commit 9727912e906762a63c1a667c84731d3427653f88
Fixed in 5.18 with commit 60f1d3c92dc1ef1026e5b917a329a7fa947da036
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-2022-49105
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/staging/wfx/main.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/93498c6e775ae91732a8109dba1bdcd324908f84
https://git.kernel.org/stable/c/86efcb524ae1889ae73f2a2f0bb7fff2ec757ab0
https://git.kernel.org/stable/c/ab0fed1fa744173433cfd1dbaf9239f200ded650
https://git.kernel.org/stable/c/9727912e906762a63c1a667c84731d3427653f88
https://git.kernel.org/stable/c/60f1d3c92dc1ef1026e5b917a329a7fa947da036
reply other threads:[~2025-02-26 1:58 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=2025022601-CVE-2022-49105-b5ae@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@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.