CVE-2026-53184: udp: clear skb->dev before running a sockmap verdict
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.49% (FIRST EPSS).
- 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 1b585673a2249f13678e7ac443ac683ba767e0b6, 263779a6beff03b8b06f6d25566cb0f45af361f2, 3c94f241f776562c489876ff506f366224565c21; azl3 kernel 6.6.141.1-1 on Azure Linux 3.0 6.6.143.1-1.
Low priority for now. Upgrade to Linux Linux 1b585673a2249f13678e7ac443ac683ba767e0b6, 263779a6beff03b8b06f6d25566cb0f45af361f2, 3c94f241f776562c489876ff506f366224565c21; azl3 kernel 6.6.141.1-1 on Azure Linux 3.0 6.6.143.1-1 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: udp: clear skb->dev before running a sockmap verdict On the UDP receive path skb->dev is repurposed as dev_scratch (the truesize/state cache set by udp_set_dev_scratch()), through the union { struct net_device *dev; unsigned long dev_scratch; } in sk_buff. When a UDP socket is in a sockmap, sk_data_ready is sk_psock_verdict_data_ready(), which calls udp_read_skb() -> recv_actor() (sk_psock_verdict_recv) to run the attached SK_SKB verdict program in softirq. If that program calls a socket-lookup helper (bpf_sk_lookup_tcp/udp, bpf_skc_lookup_tcp), bpf_skc_lookup() does: if (skb->dev) caller_net = dev_net(skb->dev); skb->dev still holds the dev_scratch value (a non-NULL integer), so dev_net() dereferences it as a struct net_device * and the kernel takes a general protection fault on a non-canonical address in softirq: Oops: general protection fault, probably for non-canonical address 0x1010000800004a0 CPU: 1 UID: 0 PID: 1406 Comm: syz.2.19 Not tainted 7.1.0-rc6 #1 PREEMPT(full) RIP: 0010:bpf_skc_lookup net/core/filter.c:7033 [inline] RIP: 0010:bpf_sk_lookup+0x45/0x160 net/core/filter.c:7047 Call Trace: <IRQ> bpf_prog_4675cb904b7071f8+0x12e/0x14e bpf_prog_run_pin_on_cpu+0xc6/0x1f0 sk_psock_verdict_recv+0x1ba/0x350 udp_read_skb+0x31a/0x370 sk_psock_verdict_data_ready+0x2e3/0x600 __udp_enqueue_schedule_skb+0x4c8/0x650 udpv6_queue_rcv_one_skb+0x3ec/0x740 udp6_unicast_rcv_skb+0x11d/0x140 ip6_protocol_deliver_rcu+0x61e/0x950 ip6_input_finish+0xa9/0x150 NF_HOOK+0x286/0x2f0 ip6_input+0x117/0x220 NF_HOOK+0x286/0x2f0 __netif_receive_skb+0x85/0x200 process_backlog+0x374/0x9a0 __napi_poll+0x4f/0x1c0 net_rx_action+0x3b0/0x770 handle_softirqs+0x15a/0x460 do_softirq+0x57/0x80 </IRQ> The rmem charge that dev_scratch accounted for is released by skb_recv_udp() on dequeue, just above, so the scratch is dead by the time recv_actor() runs. Clear skb->dev so bpf_skc_lookup() falls back to sock_net(skb->sk), which skb_set_owner_sk_safe() set just above.
- Published
- Jun 25, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.4% · 42th percentile
- CWE
- CWE-476
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.4%
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.
Is your version affected? Check itNoroxi 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 kernel6.0 and later · before 6.1.176
- linux linux kernel6.2 and later · before 6.6.143
- linux linux kernel6.7 and later · before 6.12.94
- linux linux kernel6.13 and later · before 6.18.36
- linux linux kernel6.19 and later · before 7.0.13
- linux linux kernel7.1
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
- 6.0affected
- 965b57b469a589d64d81b1688b38dcb537011bb0 and later · before 263779a6beff03b8b06f6d25566cb0f45af361f2affected · git
- 965b57b469a589d64d81b1688b38dcb537011bb0 and later · before 1b585673a2249f13678e7ac443ac683ba767e0b6affected · git
- 965b57b469a589d64d81b1688b38dcb537011bb0 and later · before 90d35188aaa92b8f8b23f66335e0e91bf60103a3affected · git
- 965b57b469a589d64d81b1688b38dcb537011bb0 and later · before 6822eed69572000a181fa4e31fceacc60918c471affected · git
- 965b57b469a589d64d81b1688b38dcb537011bb0 and later · before 7d6d92d000ebe3a845a17c165c1d3a70c5d84fe1affected · git
- 965b57b469a589d64d81b1688b38dcb537011bb0 and later · before 3c94f241f776562c489876ff506f366224565c21affected · git
- before 6.0not affected · semver
- 6.1.176 and later · up to and including 6.1.*not affected · semver
- 6.6.143 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.176-1 | 6.1.176-1 |
| Debian:13 | linux | before 6.12.94-1 | 6.12.94-1 |
| Debian:14 | linux | before 7.0.13-1 | 7.0.13-1 |
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-53182Jun 25, 2026 · wifi: nl80211: reject oversized EMA RNR lists31Monitor
- ← EarlierCVE-2026-53183Jun 25, 2026 · mptcp: allow subflow rcv wnd to shrink30Monitor
- Later →CVE-2026-53185Jun 25, 2026 · zram: fix use-after-free in zram_bvec_write_partial()31Monitor
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 | 1b585673a2249f13678e7ac443ac683ba767e0b6 | Vendor (CNA) |
| Linux Linux | 263779a6beff03b8b06f6d25566cb0f45af361f2 | Vendor (CNA) |
| Linux Linux | 3c94f241f776562c489876ff506f366224565c21 | Vendor (CNA) |
| Linux Linux | 6822eed69572000a181fa4e31fceacc60918c471 | Vendor (CNA) |
| Linux Linux | 7d6d92d000ebe3a845a17c165c1d3a70c5d84fe1 | Vendor (CNA) |
| Linux Linux | 90d35188aaa92b8f8b23f66335e0e91bf60103a3 | Vendor (CNA) |
| azl3 kernel 6.6.141.1-1 on Azure Linux 3.0 | 6.6.143.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.176-1 · Debian:12 | Package registry (OSV) |
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.
No nightly-computed relations.
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).
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-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/263779a6beff03b8b06f6d25566cb0f45af361f2
- git.kernel.org/stable/c/3c94f241f776562c489876ff506f366224565c21
- git.kernel.org/stable/c/6822eed69572000a181fa4e31fceacc60918c471
- git.kernel.org/stable/c/7d6d92d000ebe3a845a17c165c1d3a70c5d84fe1
- git.kernel.org/stable/c/90d35188aaa92b8f8b23f66335e0e91bf60103a3
- cert-portal.siemens.com/productcert/html/ssa-784472.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.