CVE-2026-53184

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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: 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

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.

CVSS v3
7.5
EG Score
7.5(high)
EPSS
39.6%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 6, 2026

Advisory Details (6)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

udp: clear skb->dev before running a sockmap verdict - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/90d35188aaa92b8f8b23f66335e0e91bf60103a3
generic

udp: clear skb->dev before running a sockmap verdict - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7d6d92d000ebe3a845a17c165c1d3a70c5d84fe1
generic

udp: clear skb->dev before running a sockmap verdict - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6822eed69572000a181fa4e31fceacc60918c471
generic

udp: clear skb->dev before running a sockmap verdict - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3c94f241f776562c489876ff506f366224565c21
generic

udp: clear skb->dev before running a sockmap verdict - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/263779a6beff03b8b06f6d25566cb0f45af361f2
generic

udp: clear skb->dev before running a sockmap verdict - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1b585673a2249f13678e7ac443ac683ba767e0b6

Vendor Advisories for CVE-2026-53184(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 52× in last 7d / 74× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 01:22 UTCEG score recompute
  2. 2026-07-07 01:22 UTCVendor advisory
  3. 2026-07-07 01:22 UTCGHSA enrichment
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 13:19 UTCEG score recompute
  7. 2026-07-06 13:19 UTCVendor advisory
  8. 2026-07-06 13:19 UTCGHSA enrichment
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-06 01:06 UTCEG score recompute
  12. 2026-07-06 01:06 UTCVendor advisory
  13. 2026-07-06 01:06 UTCGHSA enrichment
  14. 2026-07-05 12:58 UTCEG score recompute
  15. 2026-07-05 12:58 UTCVendor advisory
  16. 2026-07-05 12:58 UTCGHSA enrichment
  17. 2026-07-05 02:31 UTCEPSS rescore
  18. 2026-07-05 02:30 UTCEPSS rescore
  19. 2026-07-05 00:55 UTCEG score recompute
  20. 2026-07-05 00:55 UTCVendor advisory
  21. 2026-07-05 00:55 UTCGHSA enrichment
  22. 2026-07-04 12:52 UTCEG score recompute
  23. 2026-07-04 12:52 UTCVendor advisory
  24. 2026-07-04 12:52 UTCGHSA enrichment
  25. 2026-07-04 06:31 UTCEPSS rescore
Show 49 more
  1. 2026-07-04 06:31 UTCEPSS rescore
  2. 2026-07-04 00:50 UTCEG score recompute
  3. 2026-07-04 00:50 UTCVendor advisory
  4. 2026-07-04 00:50 UTCGHSA enrichment
  5. 2026-07-03 12:47 UTCEG score recompute
  6. 2026-07-03 12:47 UTCVendor advisory
  7. 2026-07-03 12:47 UTCGHSA enrichment
  8. 2026-07-03 00:43 UTCEG score recompute
  9. 2026-07-03 00:43 UTCVendor advisory
  10. 2026-07-03 00:43 UTCGHSA enrichment
  11. 2026-07-02 12:40 UTCEG score recompute
  12. 2026-07-02 12:40 UTCVendor advisory
  13. 2026-07-02 12:40 UTCGHSA enrichment
  14. 2026-07-02 00:37 UTCEG score recompute
  15. 2026-07-02 00:37 UTCVendor advisory
  16. 2026-07-02 00:37 UTCGHSA enrichment
  17. 2026-07-01 15:07 UTCEPSS rescore
  18. 2026-07-01 12:34 UTCEG score recompute
  19. 2026-07-01 12:34 UTCVendor advisory
  20. 2026-07-01 12:34 UTCGHSA enrichment
  21. 2026-07-01 00:31 UTCEG score recompute
  22. 2026-07-01 00:31 UTCVendor advisory
  23. 2026-07-01 00:31 UTCGHSA enrichment
  24. 2026-06-30 23:22 UTCEPSS rescore
  25. 2026-06-30 12:27 UTCEG score recompute
  26. 2026-06-30 12:27 UTCVendor advisory
  27. 2026-06-30 12:27 UTCGHSA enrichment
  28. 2026-06-30 00:21 UTCEG score recompute
  29. 2026-06-30 00:21 UTCVendor advisory
  30. 2026-06-30 00:21 UTCGHSA enrichment
  31. 2026-06-29 14:06 UTCEPSS rescore
  32. 2026-06-29 14:06 UTCEPSS rescore
  33. 2026-06-29 12:18 UTCEG score recompute
  34. 2026-06-29 12:18 UTCVendor advisory
  35. 2026-06-29 12:18 UTCGHSA enrichment
  36. 2026-06-29 00:15 UTCEG score recompute
  37. 2026-06-29 00:15 UTCVendor advisory
  38. 2026-06-29 00:15 UTCGHSA enrichment
  39. 2026-06-28 14:07 UTCEPSS rescore
  40. 2026-06-28 12:12 UTCEG score recompute▲ 7.50
  41. 2026-06-28 12:12 UTCVendor advisory
  42. 2026-06-28 12:12 UTCGHSA enrichment
  43. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  44. 2026-06-28 04:56 UTCEPSS rescore
  45. 2026-06-28 04:56 UTCEPSS rescore
  46. 2026-06-27 03:08 UTCEPSS rescore
  47. 2026-06-25 13:49 UTCEPSS rescore
  48. 2026-06-25 10:07 UTCEG score recompute
  49. 2026-06-25 10:07 UTCGHSA enrichment

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-53184?
CVE-2026-53184 is a high vulnerability published on June 25, 2026. 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 udpsetdev_scratch()), through the union { struct netdevice *dev; unsigned long…
When was CVE-2026-53184 disclosed?
CVE-2026-53184 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53184 actively exploited?
CVE-2026-53184 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 39.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53184?
CVE-2026-53184 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-53184?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53184, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53184

Explore →

Is Your Infrastructure Affected by CVE-2026-53184?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs