CVE-2026-52910

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
7.8EG
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.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

bpf: Free reuseport cBPF prog after RCU grace period.

Eulgyu Kim reported the splat below with a repro. [0]

The repro sets up a UDP reuseport group with a cBPF prog and replaces it with a new one while another thread is sending a UDP packet to the group.

The reuseport prog is freed by sk_reuseport_prog_free(). bpf_prog_put() is called for "e"BPF prog to destruct through multiple stages while cBPF prog is freed immediately by bpf_release_orig_filter() and bpf_prog_free().

If a reuseport prog is detached from the setsockopt() path (reuseport_attach_prog() or reuseport_detach_prog()), sk_reuseport_prog_free() is called without waiting for RCU readers to complete, resulting in various bugs.

Let's defer freeing the reuseport cBPF prog after one RCU grace period.

Note "e"BPF prog is safe as is unless the fast path starts to touch fields destroyed in bpf_prog_put_deferred() and __bpf_prog_put_noref().

[0]: BUG: KASAN: vmalloc-out-of-bounds in reuseport_select_sock+0xedc/0x1220 net/core/sock_reuseport.c:596 Read of size 4 at addr ffffc9000051e004 by task slowme/10208 CPU: 6 UID: 1000 PID: 10208 Comm: slowme Not tainted 7.0.0-geb7ac95ff75e #32 PREEMPT(full) Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Call Trace: dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xca/0x240 mm/kasan/report.c:482 kasan_report+0x118/0x150 mm/kasan/report.c:595 reuseport_select_sock+0xedc/0x1220 net/core/sock_reuseport.c:596 udp4_lib_lookup2+0x3bc/0x950 net/ipv4/udp.c:495 __udp4_lib_lookup+0x768/0xe20 net/ipv4/udp.c:723 __udp4_lib_lookup_skb+0x297/0x390 net/ipv4/udp.c:752 __udp4_lib_rcv+0x1312/0x2620 net/ipv4/udp.c:2752 ip_protocol_deliver_rcu+0x282/0x440 net/ipv4/ip_input.c:207 ip_local_deliver_finish+0x3bb/0x6f0 net/ipv4/ip_input.c:241 NF_HOOK+0x30c/0x3a0 include/linux/netfilter.h:318 NF_HOOK+0x30c/0x3a0 include/linux/netfilter.h:318 __netif_receive_skb_one_core net/core/dev.c:6181 [inline] __netif_receive_skb net/core/dev.c:6294 [inline] process_backlog+0xaa4/0x1960 net/core/dev.c:6645 __napi_poll+0xae/0x340 net/core/dev.c:7709 napi_poll net/core/dev.c:7772 [inline] net_rx_action+0x5d7/0xf50 net/core/dev.c:7929 handle_softirqs+0x22b/0x870 kernel/softirq.c:622 do_softirq+0x76/0xd0 kernel/softirq.c:523 __local_bh_enable_ip+0xf8/0x130 kernel/softirq.c:450 local_bh_enable include/linux/bottom_half.h:33 [inline] rcu_read_unlock_bh include/linux/rcupdate.h:924 [inline] __dev_queue_xmit+0x1dd7/0x3710 net/core/dev.c:4890 neigh_output include/net/neighbour.h:556 [inline] ip_finish_output2+0xca9/0x1070 net/ipv4/ip_output.c:237 NF_HOOK_COND include/linux/netfilter.h:307 [inline] ip_output+0x29f/0x450 net/ipv4/ip_output.c:438 ip_send_skb+0x45/0xc0 net/ipv4/ip_output.c:1508 udp_send_skb+0xb04/0x1510 net/ipv4/udp.c:1195 udp_sendmsg+0x1a71/0x2350 net/ipv4/udp.c:1485 sock_sendmsg_nosec net/socket.c:727 [inline] __sock_sendmsg net/socket.c:742 [inline] __sys_sendto+0x554/0x680 net/socket.c:2206 __do_sys_sendto net/socket.c:2213 [inline] __se_sys_sendto net/socket.c:2209 [inline] __x64_sys_sendto+0xde/0x100 net/socket.c:2209 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x160/0xf80 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x415a2d Code: b3 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f6bc31e41e8 EFLAGS: 00000212 ORIG_RAX: 000000000000002c RAX: ffffffffffffffda RBX: 00007f6bc31e4cdc RCX: 0000000000415a2d RDX: 0000000000000001 RSI: 00007f6bc31e421f RDI: 0000000000000003 RBP: 00007f6bc31e4240 R08: 00007f6bc31e4220 R09: 0000000000000010 R10: 0000000000000000 R11: ---truncated---

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
56(Track)
EG Risk 56/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
Severity78% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

June 19, 2026

Last Modified

September 8, 2026

Advisory Details (8)

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

bpf: Free reuseport cBPF prog after RCU grace period. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fec41484e7c2aa7ded44c541bba98872be937754
generic

bpf: Free reuseport cBPF prog after RCU grace period. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f8b8f1d4bb76098e87b8269a0631019648330e6d
generic

bpf: Free reuseport cBPF prog after RCU grace period. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c3e3fddda6b5d9ba505d218b4055e7d8a282ac57
generic

bpf: Free reuseport cBPF prog after RCU grace period. - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: Free reuseport cBPF prog after RCU grace period. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/87dfb977bdb6eaa47e9993a34e18f44970f88b1f
generic

bpf: Free reuseport cBPF prog after RCU grace period. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/298db6167f81e9c470a57cf652e4e47757b4293e
generic

bpf: Free reuseport cBPF prog after RCU grace period. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/18fc650ccd7fe3376eca89203668cfb8268f60df
generic

bpf: Free reuseport cBPF prog after RCU grace period. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/08264d5bba0bdd3a79bc2984fee09286aba0c4eb

Vendor Advisories for CVE-2026-52910(2)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-14ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-14ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-14ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1
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 (143 versions)7.0.12-2

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 54× 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 266 total refreshes for this CVE.

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

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCDere3046/ScreenOff
    First seen Jul 21, 2026

    CVE-2026-52910 kernel crash PoC. screen goes off.

    Open source ↗
  • GitHub PoCDere3046/ElevateMe_noLKM
    First seen Jul 20, 2026

    noLKM,5.10 use CVE-2026-52910.

    Open source ↗

Frequently asked(5)

What is CVE-2026-52910?
CVE-2026-52910 is a high vulnerability published on June 19, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf: Free reuseport cBPF prog after RCU grace period. Eulgyu Kim reported the splat below with a repro. [0] The repro sets up a UDP reuseport group with a cBPF prog and replaces it with a new one while another thread is sending a…
When was CVE-2026-52910 disclosed?
CVE-2026-52910 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52910 actively exploited?
CVE-2026-52910 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 98.9% of all scored CVEs.
What is the CVSS score of CVE-2026-52910?
CVE-2026-52910 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-52910?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52910, 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-52910

Explore →

Is Your Infrastructure Affected by CVE-2026-52910?

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