From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-45873: netfilter: nft_set_rbtree: check for partial overlaps in anonymous sets
Date: Wed, 27 May 2026 14:18:35 +0200 [thread overview]
Message-ID: <2026052713-CVE-2026-45873-40e6@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nft_set_rbtree: check for partial overlaps in anonymous sets
Userspace provides an optimized representation in case intervals are
adjacent, where the end element is omitted.
The existing partial overlap detection logic skips anonymous set checks
on start elements for this reason.
However, it is possible to add intervals that overlap to this anonymous
where two start elements with the same, eg. A-B, A-C where C < B.
start end
A B
start end
A C
Restore the check on overlapping start elements to report an overlap.
The Linux kernel CVE team has assigned CVE-2026-45873 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.10.166 with commit 4aacf3d78424293e318c616016865380b37b9cc5 and fixed in 5.10.252 with commit 7ca5813e1b21ef300e04593f47b073ef3217aac6
Issue introduced in 5.15.91 with commit 2bf1435fa19d2c58054391b3bba40d5510a5758c and fixed in 5.15.202 with commit 029e5f6a95e905b12d6bc20421be32a01e0eb311
Issue introduced in 6.1.9 with commit 318cb24a4c3fce8140afaf84e4d45fcb76fb280b and fixed in 6.1.165 with commit f1381ce0a1dd013610985e1c4260908163a427df
Issue introduced in 6.2 with commit c9e6978e2725a7d4b6cd23b2facd3f11422c0643 and fixed in 6.6.128 with commit f1535d56fc3f6c625b7e0559c006bd0318791bb1
Issue introduced in 6.2 with commit c9e6978e2725a7d4b6cd23b2facd3f11422c0643 and fixed in 6.12.75 with commit 05feaf826390fd16f1deb89dd9412def3b2a280f
Issue introduced in 6.2 with commit c9e6978e2725a7d4b6cd23b2facd3f11422c0643 and fixed in 6.18.14 with commit dad14d22dff1a191612acb98facceb303d0524a2
Issue introduced in 6.2 with commit c9e6978e2725a7d4b6cd23b2facd3f11422c0643 and fixed in 6.19.4 with commit e6497e06a102870803a59570d75ed2c36d7e11b3
Issue introduced in 6.2 with commit c9e6978e2725a7d4b6cd23b2facd3f11422c0643 and fixed in 7.0 with commit 4780ec142cbb24b794129d3080eee5cac2943ffc
Issue introduced in 4.19.316 with commit 7ab87a326f20c52ff4d9972052d085be951c704b
Issue introduced in 5.4.262 with commit 181859bdfb9734aca449512fccaee4cacce64aed
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-45873
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/netfilter/nft_set_rbtree.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/7ca5813e1b21ef300e04593f47b073ef3217aac6
https://git.kernel.org/stable/c/029e5f6a95e905b12d6bc20421be32a01e0eb311
https://git.kernel.org/stable/c/f1381ce0a1dd013610985e1c4260908163a427df
https://git.kernel.org/stable/c/f1535d56fc3f6c625b7e0559c006bd0318791bb1
https://git.kernel.org/stable/c/05feaf826390fd16f1deb89dd9412def3b2a280f
https://git.kernel.org/stable/c/dad14d22dff1a191612acb98facceb303d0524a2
https://git.kernel.org/stable/c/e6497e06a102870803a59570d75ed2c36d7e11b3
https://git.kernel.org/stable/c/4780ec142cbb24b794129d3080eee5cac2943ffc
reply other threads:[~2026-05-27 12:21 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=2026052713-CVE-2026-45873-40e6@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.