From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2022-49867: net: wwan: iosm: fix memory leak in ipc_wwan_dellink
Date: Thu, 1 May 2025 16:10:57 +0200 [thread overview]
Message-ID: <2025050149-CVE-2022-49867-e420@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net: wwan: iosm: fix memory leak in ipc_wwan_dellink
IOSM driver registers network device without setting the
needs_free_netdev flag, and does NOT call free_netdev() when
unregisters network device, which causes a memory leak.
This patch sets needs_free_netdev to true when registers
network device, which makes netdev subsystem call free_netdev()
automatically after unregister_netdevice().
The Linux kernel CVE team has assigned CVE-2022-49867 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.14 with commit 2a54f2c7793409736f2e5ea101e050b3f1997088 and fixed in 5.15.79 with commit 2ce2348c2858d723f7fe389dead9b43b08e0944e
Issue introduced in 5.14 with commit 2a54f2c7793409736f2e5ea101e050b3f1997088 and fixed in 6.0.9 with commit 128514b51a5ba2c82f9e4a106f1c10423907618a
Issue introduced in 5.14 with commit 2a54f2c7793409736f2e5ea101e050b3f1997088 and fixed in 6.1 with commit f25caaca424703d5a0607310f0452f978f1f78d9
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-49867
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/wwan/iosm/iosm_ipc_wwan.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/2ce2348c2858d723f7fe389dead9b43b08e0944e
https://git.kernel.org/stable/c/128514b51a5ba2c82f9e4a106f1c10423907618a
https://git.kernel.org/stable/c/f25caaca424703d5a0607310f0452f978f1f78d9
reply other threads:[~2025-05-01 14:16 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=2025050149-CVE-2022-49867-e420@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.