From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2025-21760: ndisc: extend RCU protection in ndisc_send_skb()
Date: Wed, 26 Feb 2025 18:17:16 -0800 [thread overview]
Message-ID: <2025022604-CVE-2025-21760-fb9d@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ndisc: extend RCU protection in ndisc_send_skb()
ndisc_send_skb() can be called without RTNL or RCU held.
Acquire rcu_read_lock() earlier, so that we can use dev_net_rcu()
and avoid a potential UAF.
The Linux kernel CVE team has assigned CVE-2025-21760 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.26 with commit 1762f7e88eb34f653b4a915be99a102e347dd45e and fixed in 6.1.129 with commit a9319d800b5701e7f5e3fa71a5b7c4831fc20d6d
Issue introduced in 2.6.26 with commit 1762f7e88eb34f653b4a915be99a102e347dd45e and fixed in 6.6.79 with commit ae38982f521621c216fc2f5182cd091f4734641d
Issue introduced in 2.6.26 with commit 1762f7e88eb34f653b4a915be99a102e347dd45e and fixed in 6.12.16 with commit 789230e5a8c1097301afc802e242c79bc8835c67
Issue introduced in 2.6.26 with commit 1762f7e88eb34f653b4a915be99a102e347dd45e and fixed in 6.13.4 with commit 04e05112f10354ffc3bb6cc796d553bab161594c
Issue introduced in 2.6.26 with commit 1762f7e88eb34f653b4a915be99a102e347dd45e and fixed in 6.14-rc3 with commit ed6ae1f325d3c43966ec1b62ac1459e2b8e45640
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-2025-21760
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/ndisc.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/a9319d800b5701e7f5e3fa71a5b7c4831fc20d6d
https://git.kernel.org/stable/c/ae38982f521621c216fc2f5182cd091f4734641d
https://git.kernel.org/stable/c/789230e5a8c1097301afc802e242c79bc8835c67
https://git.kernel.org/stable/c/04e05112f10354ffc3bb6cc796d553bab161594c
https://git.kernel.org/stable/c/ed6ae1f325d3c43966ec1b62ac1459e2b8e45640
reply other threads:[~2025-02-27 2:18 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=2025022604-CVE-2025-21760-fb9d@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.