From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2025-21763: neighbour: use RCU protection in __neigh_notify()
Date: Wed, 26 Feb 2025 18:17:19 -0800 [thread overview]
Message-ID: <2025022604-CVE-2025-21763-dcff@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
neighbour: use RCU protection in __neigh_notify()
__neigh_notify() can be called without RTNL or RCU protection.
Use RCU protection to avoid potential UAF.
The Linux kernel CVE team has assigned CVE-2025-21763 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.25 with commit 426b5303eb435d98b9bee37a807be386bc2b3320 and fixed in 6.1.129 with commit 784eb2376270e086f7db136d154b8404edacf97b
Issue introduced in 2.6.25 with commit 426b5303eb435d98b9bee37a807be386bc2b3320 and fixed in 6.6.79 with commit 1cbb2aa90cd3fba15ad7efb5cdda28f3d1082379
Issue introduced in 2.6.25 with commit 426b5303eb435d98b9bee37a807be386bc2b3320 and fixed in 6.12.16 with commit cdd5c2a12ddad8a77ce1838ff9f29aa587de82df
Issue introduced in 2.6.25 with commit 426b5303eb435d98b9bee37a807be386bc2b3320 and fixed in 6.13.4 with commit 559307d25235e24b5424778c7332451b6c741159
Issue introduced in 2.6.25 with commit 426b5303eb435d98b9bee37a807be386bc2b3320 and fixed in 6.14-rc3 with commit becbd5850c03ed33b232083dd66c6e38c0c0e569
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-21763
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/core/neighbour.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/784eb2376270e086f7db136d154b8404edacf97b
https://git.kernel.org/stable/c/1cbb2aa90cd3fba15ad7efb5cdda28f3d1082379
https://git.kernel.org/stable/c/cdd5c2a12ddad8a77ce1838ff9f29aa587de82df
https://git.kernel.org/stable/c/559307d25235e24b5424778c7332451b6c741159
https://git.kernel.org/stable/c/becbd5850c03ed33b232083dd66c6e38c0c0e569
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-21763-dcff@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.