CVE-2026-53184

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. the CNA's CVSS baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 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(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

June 25, 2026

Last Modified

August 5, 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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1—

Data Freshness Timeline

(refreshed 5× in last 7d / 85× 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.

Showing the most recent 100 of 305 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-30 19:41 UTCEG score recompute
  11. 2026-08-30 19:41 UTCVendor advisory
  12. 2026-08-30 19:41 UTCGHSA enrichment
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 01:22 UTCEPSS rescore
  15. 2026-08-28 21:41 UTCEPSS rescore
  16. 2026-08-28 02:54 UTCEG score recompute
  17. 2026-08-28 02:54 UTCVendor advisory
  18. 2026-08-28 02:54 UTCGHSA enrichment
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 01:21 UTCEG score recompute
  23. 2026-08-25 01:21 UTCVendor advisory
  24. 2026-08-25 01:21 UTCGHSA enrichment
  25. 2026-08-24 13:15 UTCEG score recompute
Show 75 more
  1. 2026-08-24 13:15 UTCVendor advisory
  2. 2026-08-24 13:15 UTCGHSA enrichment
  3. 2026-08-23 23:11 UTCVendor advisory
  4. 2026-08-23 23:11 UTCGHSA enrichment
  5. 2026-08-23 10:53 UTCEG score recompute
  6. 2026-08-23 10:53 UTCVendor advisory
  7. 2026-08-23 10:53 UTCGHSA enrichment
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-22 22:50 UTCVendor advisory
  10. 2026-08-22 22:50 UTCGHSA enrichment
  11. 2026-08-22 10:47 UTCEG score recompute
  12. 2026-08-22 10:47 UTCVendor advisory
  13. 2026-08-22 10:47 UTCGHSA enrichment
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 19:19 UTCGHSA enrichment
  16. 2026-08-21 07:16 UTCEG score recompute
  17. 2026-08-21 07:16 UTCVendor advisory
  18. 2026-08-21 07:16 UTCGHSA enrichment
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-20 19:13 UTCVendor advisory
  21. 2026-08-20 19:13 UTCGHSA enrichment
  22. 2026-08-20 07:10 UTCEG score recompute
  23. 2026-08-20 07:10 UTCVendor advisory
  24. 2026-08-20 07:10 UTCGHSA enrichment
  25. 2026-08-19 17:04 UTCEPSS rescore
  26. 2026-08-19 13:43 UTCVendor advisory
  27. 2026-08-19 13:43 UTCGHSA enrichment
  28. 2026-08-19 01:33 UTCEG score recompute
  29. 2026-08-19 01:33 UTCVendor advisory
  30. 2026-08-19 01:33 UTCGHSA enrichment
  31. 2026-08-18 13:48 UTCEPSS rescore
  32. 2026-08-17 15:06 UTCEG score recompute
  33. 2026-08-17 15:06 UTCVendor advisory
  34. 2026-08-17 15:06 UTCGHSA enrichment
  35. 2026-08-17 13:47 UTCEPSS rescore
  36. 2026-08-17 03:02 UTCVendor advisory
  37. 2026-08-17 03:02 UTCGHSA enrichment
  38. 2026-08-16 14:59 UTCEG score recompute
  39. 2026-08-16 14:59 UTCVendor advisory
  40. 2026-08-16 14:59 UTCGHSA enrichment
  41. 2026-08-16 14:56 UTCEPSS rescore
  42. 2026-08-16 02:56 UTCEG score recompute
  43. 2026-08-16 02:56 UTCVendor advisory
  44. 2026-08-16 02:56 UTCGHSA enrichment
  45. 2026-08-16 02:14 UTCEPSS rescore
  46. 2026-08-15 14:53 UTCVendor advisory
  47. 2026-08-15 14:53 UTCGHSA enrichment
  48. 2026-08-15 02:50 UTCEG score recompute
  49. 2026-08-15 02:50 UTCVendor advisory
  50. 2026-08-15 02:50 UTCGHSA enrichment
  51. 2026-08-15 01:30 UTCEPSS rescore
  52. 2026-08-14 14:46 UTCVendor advisory
  53. 2026-08-14 14:46 UTCGHSA enrichment
  54. 2026-08-14 02:43 UTCEG score recompute
  55. 2026-08-14 02:43 UTCVendor advisory
  56. 2026-08-14 02:43 UTCGHSA enrichment
  57. 2026-08-13 22:00 UTCEPSS rescore
  58. 2026-08-13 14:40 UTCVendor advisory
  59. 2026-08-13 14:40 UTCGHSA enrichment
  60. 2026-08-13 02:38 UTCGHSA enrichment
  61. 2026-08-12 14:35 UTCEG score recompute
  62. 2026-08-12 14:35 UTCVendor advisory
  63. 2026-08-12 14:35 UTCGHSA enrichment
  64. 2026-08-12 13:51 UTCEPSS rescore
  65. 2026-08-12 02:30 UTCVendor advisory
  66. 2026-08-12 02:30 UTCGHSA enrichment
  67. 2026-08-11 14:27 UTCEG score recompute
  68. 2026-08-11 14:27 UTCVendor advisory
  69. 2026-08-11 14:27 UTCGHSA enrichment
  70. 2026-08-11 02:23 UTCEG score recompute
  71. 2026-08-11 02:23 UTCVendor advisory
  72. 2026-08-11 02:22 UTCGHSA enrichment
  73. 2026-08-11 00:00 UTCEPSS rescore
  74. 2026-08-10 14:20 UTCGHSA enrichment
  75. 2026-08-10 02:17 UTCGHSA enrichment

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 August 5, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 60.1% of all scored CVEs.
What is the CVSS score of CVE-2026-53184?
CVE-2026-53184 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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