CVE-2026-45859

netfilter: nfnetlink_queue: do shared-unconfirmed check before segmentation

HIGH
7.5
CVSS Score
Published: May 27, 2026 at 12:15 PM UTC
Updated: October 21, 2026 at 01:18 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.7%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: netfilter: nfnetlink_queue: do shared-unconfirmed check before segmentation Ulrich reports a regression with nfqueue: If an application did not set the 'F_GSO' capability flag and a gso packet with an unconfirmed nf_conn entry is received all packets are now dropped instead of queued, because the check happens after skb_gso_segment(). In that case, we did have exclusive ownership of the skb and its associated conntrack entry. The elevated use count is due to skb_clone happening via skb_gso_segment(). Move the check so that its peformed vs. the aggregated packet. Then, annotate the individual segments except the first one so we can do a 2nd check at reinject time. For the normal case, where userspace does in-order reinjects, this avoids packet drops: first reinjected segment continues traversal and confirms entry, remaining segments observe the confirmed entry. While at it, simplify nf_ct_drop_unconfirmed(): We only care about unconfirmed entries with a refcnt > 1, there is no need to special-case dying entries. This only happens with UDP. With TCP, the only unconfirmed packet will be the TCP SYN, those aren't aggregated by GRO. Next patch adds a udpgro test case to cover this scenario.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.15.166 ≤ v < 5.166.1.107 ≤ v < 6.26.10.7 ≤ v < 6.116.11.1 ≤ v < 6.12.756.13 ≤ v < 6.18.146.19 ≤ v < 6.19.46.6.48 ≤ v < 6.725b3326c5c409b372d103ad30f174e55adbd1b5.15.1666.1.1076.10.76.116.11 rc46.11 rc56.11 rc66.11 rc76.6.486c4a0ba674f410ab99a30a16f32dac0ebfed5cd36dcc8ba8a6074bb79040f502dc66ad23a58a1c8674e6eb7fd27ef1ccc68041dbc66e6d80d2e4a1a07d8dc1c7be8d3509e8f5164dd5df64c8e34d7eeb
Vendor states this is fixed in 207b3ebacb6113acaaec0d171d5307032c690004 (fixed)
Vendor states this is fixed in 23901aa6b8a2f294c4b774436b4691f3ff863a8f (fixed)
Vendor states this is fixed in 79b713ef4261a8ead96af4703f89d0b5f25532e2 (fixed)
Vendor states this is fixed in b740e7ddd7ca0dbfeafca3f5e52717206cf28524 (fixed)
Affected range stops below 5.16, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.11 (unaffected)
Vendor states this is fixed in 6.12.75 (unaffected)
Vendor states this is fixed in 6.18.14 (unaffected)
Vendor states this is fixed in 6.19.4 (unaffected)
Affected range stops below 6.2, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.6.160 (unaffected)
Affected range stops below 6.7, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 7.0 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfoCWE-400

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card