From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99072: ipv4: stop route notification sizing when nexthop group shrinks
Date: Fri, 23 Oct 2026 14:21:14 +0200 [thread overview]
Message-ID: <2026102334-CVE-2026-99072-ef2f@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ipv4: stop route notification sizing when nexthop group shrinks
Commit 680aea08e78c ("net: ipv4: Emit notification when fib
hardware flags are changed") added an RCU-only fib_nlmsg_size() call
for asynchronous hardware flag notifications.
fib_nlmsg_size() checks fib_info_num_path() before each iteration,
then fib_info_nhc() independently reloads nh->nh_grp. If
RTM_NEWNEXTHOP replaces a group with fewer paths between those loads,
fib_info_nhc() returns NULL and fib_nexthop_nlmsg_size() dereferences
it.
Stop sizing when the indexed path is absent. Nexthop groups are
dense, so the current snapshot has no later path.
The Linux kernel CVE team has assigned CVE-2026-99072 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.12 with commit 680aea08e78c003292415518ad270bc20f9c80b1 and fixed in 6.6.160 with commit 72d9d17092bb37b0717f12042a0817d01a1f9e78
Issue introduced in 5.12 with commit 680aea08e78c003292415518ad270bc20f9c80b1 and fixed in 6.12.113 with commit ad1c9f1b98c92609e9bb2ae8f05916defc3b0a54
Issue introduced in 5.12 with commit 680aea08e78c003292415518ad270bc20f9c80b1 and fixed in 6.18.57 with commit c1f48d1c2d5e9efd904dbbc2f2b3d41543e55c49
Issue introduced in 5.12 with commit 680aea08e78c003292415518ad270bc20f9c80b1 and fixed in 7.2.11 with commit ad2b3a68b8a7d5d27de88e05674e4adb1ce46d88
Issue introduced in 5.12 with commit 680aea08e78c003292415518ad270bc20f9c80b1 and fixed in 7.3 with commit d3daa33c7af92e38f2274bbd2576f58bfbaf89e6
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-2026-99072
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/ipv4/fib_semantics.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/72d9d17092bb37b0717f12042a0817d01a1f9e78
https://git.kernel.org/stable/c/ad1c9f1b98c92609e9bb2ae8f05916defc3b0a54
https://git.kernel.org/stable/c/c1f48d1c2d5e9efd904dbbc2f2b3d41543e55c49
https://git.kernel.org/stable/c/ad2b3a68b8a7d5d27de88e05674e4adb1ce46d88
https://git.kernel.org/stable/c/d3daa33c7af92e38f2274bbd2576f58bfbaf89e6
reply other threads:[~2026-10-23 12:43 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=2026102334-CVE-2026-99072-ef2f@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.