CVE-2026-45859 Details
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.
A vulnerability in the Linux kernel's netfilter component, specifically within the nfnetlink_queue, has been addressed. This issue arose when an application did not activate the 'F_GSO' capability flag. In such cases, if a Generic Segmentation Offload (GSO) packet with an unconfirmed connection tracking entry was received, all packets were dropped instead of being queued. This problem occurred because the verification process was applied after the segmentation of the packet, leading to the loss of exclusive ownership of the socket buffer (skb) and its related connection tracking entry. The vulnerability primarily affected UDP packets, as TCP's unconfirmed packets are not aggregated by the Generic Receive Offload (GRO). The regression was reported by Ulrich Weber.
Users can apply the latest patches available in the Linux kernel stable tree to address this vulnerability.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/207b3ebacb6113acaaec0d171d5307032c690004 | kernel.org | Patch |
| https://git.kernel.org/stable/c/23901aa6b8a2f294c4b774436b4691f3ff863a8f | kernel.org | Patch |
| https://git.kernel.org/stable/c/79b713ef4261a8ead96af4703f89d0b5f25532e2 | kernel.org | Patch |
| https://git.kernel.org/stable/c/b740e7ddd7ca0dbfeafca3f5e52717206cf28524 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.15.166, < 5.16 >= 6.1.107, < 6.2 >= 6.6.48, < 6.7 >= 6.10.7, < 6.11 >= 6.11.1, < 6.12.75 >= 6.13, < 6.18.14 >= 6.19, < 6.19.4 6.11 - 6.11 rc4 6.11 rc5 6.11 rc6 6.11 rc7 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 25, 2026 | Initial Analysis | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| May 30, 2026 | CVE Modified | kernel.org |
| May 27, 2026 | New CVE Received | kernel.org |