CVE-2026-45859: netfilter: nfnetlink_queue: do shared-unconfirmed check before segmentation
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.65% (FIRST EPSS); higher than 51.3% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 207b3ebacb6113acaaec0d171d5307032c690004, 23901aa6b8a2f294c4b774436b4691f3ff863a8f, 4666688657e1054278b836b825fb88b2907e2da2; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 207b3ebacb6113acaaec0d171d5307032c690004, 23901aa6b8a2f294c4b774436b4691f3ff863a8f, 4666688657e1054278b836b825fb88b2907e2da2; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- May 27, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.6% · 51th percentile
- CWE
- CWE-400
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.15.166 and later · before 5.16
- linux linux kernel6.1.107 and later · before 6.2
- linux linux kernel6.6.48 and later · before 6.7
- linux linux kernel6.10.7 and later · before 6.11
- linux linux kernel6.11.1 and later · before 6.12.75
- linux linux kernel6.13 and later · before 6.18.14
- linux linux kernel6.19 and later · before 6.19.4
- linux linux kernel6.11
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6c4a0ba674f410ab99a30a16f32dac0ebfed5cd3, 025b3326c5c409b372d0103ad30f174e55adbd1b, 6.11affected
- 6dcc8ba8a6074bb79040f502dc66ad23a58a1c86 and later · before 4666688657e1054278b836b825fb88b2907e2da2affected · git
- 74e6eb7fd27ef1ccc68041dbc66e6d80d2e4a1a0 and later · before aead84bdacd77e08357fd718e5dcaffaf387f3c3affected · git
- 7d8dc1c7be8d3509e8f5164dd5df64c8e34d7eeb and later · before 79b713ef4261a8ead96af4703f89d0b5f25532e2affected · git
- 7d8dc1c7be8d3509e8f5164dd5df64c8e34d7eeb and later · before 23901aa6b8a2f294c4b774436b4691f3ff863a8faffected · git
- 7d8dc1c7be8d3509e8f5164dd5df64c8e34d7eeb and later · before b740e7ddd7ca0dbfeafca3f5e52717206cf28524affected · git
- 7d8dc1c7be8d3509e8f5164dd5df64c8e34d7eeb and later · before 207b3ebacb6113acaaec0d171d5307032c690004affected · git
- 6.1.107 and later · before 6.1.191affected · semver
- 6.6.48 and later · before 6.6.160affected · semver
- 5.15.166 and later · before 5.16affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.66.1.el10_2 | 6.12.0-211.66.1.el10_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-45855May 27, 2026 · ata: libata-scsi: avoid Non-NCQ command starvation22Monitor
- ← EarlierCVE-2026-45856May 27, 2026 · RDMA/uverbs: Validate wqe_size before using it in ib_uverbs_post_send28Monitor
- Later →CVE-2026-45860May 27, 2026 · netfilter: nf_conncount: increase the connection clean up limit to 6430Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 207b3ebacb6113acaaec0d171d5307032c690004 | Vendor (CNA) |
| Linux Linux | 23901aa6b8a2f294c4b774436b4691f3ff863a8f | Vendor (CNA) |
| Linux Linux | 4666688657e1054278b836b825fb88b2907e2da2 | Vendor (CNA) |
| Linux Linux | 5.16 | Vendor (CNA) |
| Linux Linux | 6.1.191 | Vendor (CNA) |
| Linux Linux | 6.11 | Vendor (CNA) |
| Linux Linux | 6.6.160 | Vendor (CNA) |
| Linux Linux | 79b713ef4261a8ead96af4703f89d0b5f25532e2 | Vendor (CNA) |
| Linux Linux | aead84bdacd77e08357fd718e5dcaffaf387f3c3 | Vendor (CNA) |
| Linux Linux | b740e7ddd7ca0dbfeafca3f5e52717206cf28524 | Vendor (CNA) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| almalinux:kernel | 6.12.0-211.66.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-211.66.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-211.66.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-211.66.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-211.66.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-211.66.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-211.66.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-211.66.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-211.66.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-211.66.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-211.66.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-211.66.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.12.85-1 · Debian:13 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:6.12.0-211.66.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:6.12.0-211.66.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:6.12.0-211.66.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:6.12.0-211.66.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:6.12.0-211.66.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
+8
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-462737 days apartibmveth: Disable GSO for packets with small MSS34Monitor
- CVE-2025-38501284 days apartksmbd: limit repeated connections from clients with the same IP31Monitor
- CVE-2026-458600 days apartnetfilter: nf_conncount: increase the connection clean up limit to 6430Monitor
- CVE-2026-5318329 days apartmptcp: allow subflow rcv wnd to shrink30Monitor
- CVE-2026-6417553 days apartwifi: iwlwifi: mld: stop TX during firmware restart30Monitor
- CVE-2026-23086112 days apartvsock/virtio: cap TX credit to local buffer size22Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0290 · Jun 2, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) {
return node.children.map(expand);
}Fixed
const MAX_DEPTH = 32;
function expand(node, depth = 0) {
if (depth > MAX_DEPTH) throw new Error("too deep");
return node.children.map((c) => expand(c, depth + 1));
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/23901aa6b8a2f294c4b774436b4691f3ff863a8f
- git.kernel.org/stable/c/4666688657e1054278b836b825fb88b2907e2da2
- git.kernel.org/stable/c/79b713ef4261a8ead96af4703f89d0b5f25532e2
- git.kernel.org/stable/c/aead84bdacd77e08357fd718e5dcaffaf387f3c3
- git.kernel.org/stable/c/b740e7ddd7ca0dbfeafca3f5e52717206cf28524
Vendor advisories and official records. Exploit/PoC links are deliberately left out.