From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49417: iwlwifi: mei: fix potential NULL-ptr deref
Date: Wed, 26 Feb 2025 03:11:31 +0100 [thread overview]
Message-ID: <2025022653-CVE-2022-49417-2a5f@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
iwlwifi: mei: fix potential NULL-ptr deref
If SKB allocation fails, continue rather than using the NULL
pointer.
Coverity CID: 1497650
The Linux kernel CVE team has assigned CVE-2022-49417 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.17 with commit 2da4366f9e2c44afedec4acad65a99a3c7da1a35 and fixed in 5.17.14 with commit 29b81de94d62b5e2704bb5106b3e701ca8d7c7a4
Issue introduced in 5.17 with commit 2da4366f9e2c44afedec4acad65a99a3c7da1a35 and fixed in 5.18.3 with commit 5d8d06fd3a02919100b28f927bcb76481ec0a0e3
Issue introduced in 5.17 with commit 2da4366f9e2c44afedec4acad65a99a3c7da1a35 and fixed in 5.19 with commit 78488a64aea94a3336ee97f345c1496e9bc5ebdf
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-49417
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/intel/iwlwifi/mei/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/29b81de94d62b5e2704bb5106b3e701ca8d7c7a4
https://git.kernel.org/stable/c/5d8d06fd3a02919100b28f927bcb76481ec0a0e3
https://git.kernel.org/stable/c/78488a64aea94a3336ee97f345c1496e9bc5ebdf
reply other threads:[~2025-02-26 2:14 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=2025022653-CVE-2022-49417-2a5f@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.