CVE-2026-52910

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-38034 (ENISA EUVD) · GHSA-gj4p-2qjv-wchv (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.8Exploit: Public PoCExposed services: Not assessed

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.8HIGHmedium confidence
EG Risk
51
EG Risk 51/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-09). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 19, 2026

Last Modified

November 10, 2026

Advisory Details (8)

Auto-updated Jun 28, 2026
Patch available.
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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(27)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-ibm-lts-20.04 (5.4.0.1111.140) @ focal2026-11-03ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-11-03ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-11-03ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-11-03ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18~24.04.1) @ noble2026-11-03ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-11-03ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2018.18) @ resolute2026-11-03ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1019.19) @ resolute2026-11-03ubuntu
ubuntulinux-tools-ibm-7.0 (7.0.0-1013.13) @ resolute2026-11-03ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18) @ resolute2026-11-03ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1011.11) @ resolute2026-11-03ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1122.131) @ jammy2026-11-03ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-11-03ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-11-03ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1118.128~20.04.1) @ focal2026-11-03ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1114.120~20.04.1) @ focal2026-11-03ubuntu
ubuntulinux-tools-gcp-lts-22.04 (5.15.0.1118.115) @ jammy2026-11-03ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1080 (5.15.0-1080.84) @ jammy2026-11-03ubuntu
ubuntulinux-tools-ibm-edge (6.8.0-1066.67~22.04.1) @ jammy2026-11-03ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1070.78+fips1) @ noble2026-11-03ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1070.78) @ noble2026-11-03ubuntu
ubuntulinux-virtual-6.8 (6.8.0-146.146) @ noble2026-11-03ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1063.66) @ noble2026-11-03ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1112.112) @ jammy2026-11-03ubuntu
ubuntulinux-tools-gcp-lts-24.04 (6.8.0-1070.78) @ noble2026-11-03ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1083 (5.4.0-1083.87) @ focal2026-11-03ubuntu
linuxKernel @ 5.10.259 (fixes >=4.5.0)—osv

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 rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)
  • every version up to 5.10.259-1: fixed in 5.10.259-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)
  • every version up to 6.1.176-1~deb11u1: fixed in 6.1.176-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)
  • every version up to 6.1.176-1: fixed in 6.1.176-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)
  • every version up to 6.12.94-1: fixed in 6.12.94-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)
  • every version up to 7.0.12-2: fixed in 7.0.12-2
—

Weakness Classification(3)

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

Additional Vendor Advisories

(24)

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 / 47× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 347 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 247 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-11-10 13:28 UTCEchelonGraph re-scored
  4. 2026-11-10 13:28 UTCGHSA enrichmentGHSA-gj4p-2qjv-wchv · GitHub severity HIGH · GitHub CVSS 7.8
  5. 2026-11-10 12:50 UTCEchelonGraph re-scored
  6. 2026-11-10 12:50 UTCGHSA enrichmentGHSA-gj4p-2qjv-wchv · GitHub severity HIGH · GitHub CVSS 7.8
  7. 2026-11-10 00:45 UTCEchelonGraph re-scored
  8. 2026-11-10 00:45 UTCGHSA enrichmentGHSA-gj4p-2qjv-wchv · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-11-08 16:39 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-11-03 09:27 UTCEchelonGraph re-scored
  17. 2026-11-03 09:27 UTCVendor advisory
  18. 2026-11-03 09:27 UTCGHSA enrichmentGHSA-gj4p-2qjv-wchv · GitHub severity HIGH · GitHub CVSS 7.8
  19. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  20. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  21. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  22. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  23. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  24. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  25. 2026-10-27 18:10 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-10-27 18:10 UTCVendor advisory
  2. 2026-10-27 18:09 UTCGHSA enrichmentGHSA-gj4p-2qjv-wchv · GitHub severity HIGH · GitHub CVSS 7.8
  3. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  4. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  5. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-10-25 14:21 UTCEchelonGraph re-scored
  7. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  9. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  10. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  12. 2026-10-19 20:42 UTCEchelonGraph re-scored
  13. 2026-10-19 20:42 UTCVendor advisory
  14. 2026-10-19 20:41 UTCGHSA enrichmentGHSA-gj4p-2qjv-wchv · GitHub severity HIGH · GitHub CVSS 7.8
  15. 2026-10-19 20:09 UTCEchelonGraph re-scored
  16. 2026-10-19 20:09 UTCVendor advisory
  17. 2026-10-19 20:09 UTCGHSA enrichmentGHSA-gj4p-2qjv-wchv · GitHub severity HIGH · GitHub CVSS 7.8
  18. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  20. 2026-10-18 03:32 UTCEchelonGraph re-scored
  21. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  22. 2026-10-16 17:27 UTCEchelonGraph re-scored
  23. 2026-10-16 17:27 UTCVendor advisory
  24. 2026-10-16 17:26 UTCGHSA enrichmentGHSA-gj4p-2qjv-wchv · GitHub severity HIGH · GitHub CVSS 7.8
  25. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  26. 2026-10-16 15:58 UTCEchelonGraph re-scored
  27. 2026-10-16 15:58 UTCVendor advisory
  28. 2026-10-16 15:57 UTCGHSA enrichmentGHSA-gj4p-2qjv-wchv · GitHub severity HIGH · GitHub CVSS 7.8
  29. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  30. 2026-10-15 02:31 UTCEchelonGraph re-scored
  31. 2026-10-15 02:31 UTCVendor advisory
  32. 2026-10-15 02:31 UTCGHSA enrichmentGHSA-gj4p-2qjv-wchv · GitHub severity HIGH · GitHub CVSS 7.8
  33. 2026-10-15 01:34 UTCEchelonGraph re-scored
  34. 2026-10-15 01:33 UTCGHSA enrichmentGHSA-gj4p-2qjv-wchv · GitHub severity HIGH · GitHub CVSS 7.8
  35. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  36. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  37. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  38. 2026-10-12 15:58 UTCEchelonGraph re-scored
  39. 2026-10-11 19:41 UTCEchelonGraph re-scored
  40. 2026-10-11 16:56 UTCEchelonGraph re-scored
  41. 2026-10-11 14:19 UTCEchelonGraph re-scored
  42. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  43. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  44. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  45. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  46. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  47. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  48. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  49. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  50. 2026-10-03 04:39 UTCOSV refresh
  51. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  52. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  53. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  54. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  55. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  56. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  57. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  58. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  59. 2026-09-14 02:15 UTCEchelonGraph re-scored
  60. 2026-09-14 02:15 UTCVendor advisory
  61. 2026-09-14 02:15 UTCGHSA enrichmentGHSA-gj4p-2qjv-wchv · GitHub severity HIGH · GitHub CVSS 7.8
  62. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  63. 2026-09-13 13:15 UTCEchelonGraph re-scored
  64. 2026-09-13 13:15 UTCVendor advisory
  65. 2026-09-13 13:15 UTCGHSA enrichmentGHSA-gj4p-2qjv-wchv · GitHub severity HIGH · GitHub CVSS 7.8
  66. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  67. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  68. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  69. 2026-09-08 09:44 UTCEchelonGraph re-scored
  70. 2026-09-08 09:44 UTCVendor advisory
  71. 2026-09-08 09:44 UTCGHSA enrichmentGHSA-gj4p-2qjv-wchv · GitHub severity HIGH · GitHub CVSS 7.8
  72. 2026-09-08 08:59 UTCEchelonGraph re-scored
  73. 2026-09-08 08:59 UTCVendor advisory
  74. 2026-09-08 08:59 UTCGHSA enrichmentGHSA-gj4p-2qjv-wchv · GitHub severity HIGH · GitHub CVSS 7.8
  75. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 1st percentile

Publicly available exploits

(2 references)

Public exploit code is referenced for this CVE (2 GitHub PoCs). Defenders should treat patch urgency accordingly.

  • GitHub PoCDere3046/ScreenOff
    Published Jul 21, 2026

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

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

    noLKM,5.10 use CVE-2026-52910.

    Open source ↗

Related CVEs(same vendor + same CWE)· as of November 11, 2026

Frequently asked(5)

What is CVE-2026-52910?
CVE-2026-52910 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-52910 published?
The CVE record for CVE-2026-52910 was published on June 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 10, 2026; the record at its source may have been updated since.
Is CVE-2026-52910 actively exploited?
CVE-2026-52910 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-52910?
CVE-2026-52910 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-52910?
A fix for CVE-2026-52910 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-52910 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs