From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-44985: ipv6: prevent possible UAF in ip6_xmit()
Date: Wed, 4 Sep 2024 21:56:50 +0200 [thread overview]
Message-ID: <2024090445-CVE-2024-44985-2dde@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ipv6: prevent possible UAF in ip6_xmit()
If skb_expand_head() returns NULL, skb has been freed
and the associated dst/idev could also have been freed.
We must use rcu_read_lock() to prevent a possible UAF.
The Linux kernel CVE team has assigned CVE-2024-44985 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.15 with commit 0c9f227bee11 and fixed in 5.15.166 with commit 975f764e96f7
Issue introduced in 5.15 with commit 0c9f227bee11 and fixed in 6.1.107 with commit 38a21c026ed2
Issue introduced in 5.15 with commit 0c9f227bee11 and fixed in 6.6.48 with commit 124b428fe280
Issue introduced in 5.15 with commit 0c9f227bee11 and fixed in 6.10.7 with commit fc88d6c1f289
Issue introduced in 5.15 with commit 0c9f227bee11 and fixed in 6.11-rc5 with commit 2d5ff7e339d0
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-2024-44985
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:
net/ipv6/ip6_output.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/975f764e96f71616b530e300c1bb2ac0ce0c2596
https://git.kernel.org/stable/c/38a21c026ed2cc7232414cb166efc1923f34af17
https://git.kernel.org/stable/c/124b428fe28064c809e4237b0b38e97200a8a4a8
https://git.kernel.org/stable/c/fc88d6c1f2895a5775795d82ec581afdff7661d1
https://git.kernel.org/stable/c/2d5ff7e339d04622d8282661df36151906d0e1c7
reply other threads:[~2024-09-04 19:57 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=2024090445-CVE-2024-44985-2dde@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.