CVE-2026-45859: Linux kernel · netfilter: nfnetlink_queue: do shared-unconfirmed check before segmentation
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 7.5 High · fixed in 6.8.0-1060.63~22.04.1 : patch Linux kernel soon.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.8.0-1060.63~22.04.1, 6.8.0-1063.71~22.04.1, 6.8.0-1062.69~22.04.1 +30
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 27 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-8492-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8492-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8497-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8498-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8499-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8492-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8492-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-8492-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-8606-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8607-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8609-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8619-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 25.10linuxpkg:deb/ubuntu/linux?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10linux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10linux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10linux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10linux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10linux-oraclepkg:deb/ubuntu/linux-oracle?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2026-45859 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-45859 (opens in a new tab)
- git.kernel.org/linus/207b3ebacb6113acaaec0d171d5307032c690004 (opens in a new tab)
- ubuntu.com/security/notices/USN-8492-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8492-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8497-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8498-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8499-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8492-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8492-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-8492-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-8606-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8607-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8609-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8619-1 (opens in a new tab)