CVE-2026-52910PoC(linux / linux_kernel)

HIGHCVSS 7.8 · HIGH

Exploitation observed; activity peaked at 3 mentions and remains active

Immediate actions

Patch linux linux_kernel systems immediately
Assume compromise if assets are exposed
Hunt for exploitation attempts and persistence artifacts
Increase monitoring for publicly documented tradecraft

Recommended action window: Immediate (within 24h)

NVD description

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: <IRQ> 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 </IRQ> <TASK> __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---

linux CVEs Back to dashboard

7.5/ 10 priority

Sources & remediation

Patch / fix

Vendor / third-party advisories

Other references

Weakness type (CWE)

CWE-125CWE-416CWE-364

Priority

HIGH

Exploitation

ACTIVE

PoC

YES

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

linux_kernel

Threat summary

Active exploitation appears in 1 classified signals
Public PoC and exploit tooling are both present
Patch or workaround signal is available
10 mentions across 7 observed days

What's happening

Active exploitation reported across 1 signal
Exploit tool or code specified in 4 signals
PoC mentioned or linked in 5 signals
Patch or workaround mentioned in 2 signals
Technical details provided in 9 signals
Disclosure: 2 classified signals
Peaked 2d ago at 3 mentions (2026-09-23); latest day: 1
10 total mentions across 7 days

Affected systems

Vendors

linux

Products

linux_kernel

1 version affected across 1 product

Deep dive

Activity timeline10 mentions / 7d

Signal classification5 categories

PoC

440.0%

Disclosure

220.0%

Exploit

220.0%

Active Exploitation

110.0%

Patch

110.0%

Referenced assets7 URLs

By indicator

Classification over time

Date	Total	Labels

2026-06-19	2	Active Exploitation1Disclosure1
2026-09-14	1	Exploit1
2026-09-17	1	PoC1
2026-09-18	1	Exploit1
2026-09-23	3	Disclosure1PoC2
2026-09-24	1	PoC1
2026-10-03	1	Patch1

Full discourse10 posts

Brad Spengler@spendergrsec137d
Active Exploitation
A CVE so nice they announced it twice: https://lore.kernel.org/linux-cve-announce/2026061935-CVE-2026-52908-ecea@gregkh/T/#u https://lore.kernel.org/linux-cve-announce/2026061932-CVE-2026-52908-fb97@gregkh/T/#u and the cBPF CVE delayed for over a month past when people were able to exploit it with public info: https://lore.kernel.org/linux-cve-announce/2026061934-CVE-2026-52910-aef2@gregkh/T/#u https://t.co/5lUdtsjxJx
Post summary
The text notes duplicate announcements of CVE‑2026‑52908 and points out that CVE‑2026‑52910 was publicly exploitable after a month, suggesting active exploitation.
2102273.3K
7.1K followersView on X
Ryx@PadhiyarRushi46d
Exploit
Working PoC for CVE-2026-52910 is public!! Linux kernel BPF reuseport race: replace a cBPF filter while packets are still flowing → use-after-free → reliable kernel panic. Exploit code reproduces the crash cleanly. https://cybrmonk.com/blog/cve-2026-52910-exploit-code-now-public-linux-kernel-bpf-reuseport-crash-can-be-triggered-now #Cybersecurity #AI #AISecurity #MCP #Claude #GPT #Infosec #Trending #KernelSecurity
Post summary
The text announces public availability of working exploit code for CVE-2026-52910, a Linux kernel BPF reuseport race condition causing kernel panic, without mentioning active exploitation or patches.
1001871.2K
954 followersView on X
pwnmachine 👾@princechaddha31d
Patch
Codex (gpt-5.6-sol) came closest to escaping as it found and cloned CVE-2026-52910 a public container escape targeting the reuseport cBPF race on Ubuntu 24.04 6.8.0-139 and retargeted it to the host's exact kernel (6.8.0-142) by extracting symbols from the actual kernel package but the exploit failed to land because the newer kernel changed JIT memory accounting though the BPF manipulation likely corrupted kernel state and crashed the entire host not just the container 🫠 Crashing containers is easy for these agents but this was a host kernel crash from inside a container which is a different class of problem entirely because resource limits (CPU, memory, pids) can't prevent it since it targets kernel internals not resource consumption. Only seccomp filtering of the bpf syscall would have stopped it but it was disabled intentionally for this level. None cleanly escaped the sandbox
Post summary
The text describes an AI agent's attempt to exploit CVE-2026-52910, which caused a host kernel crash, and notes that seccomp filtering of the bpf syscall could have prevented the escape.
0101261.5K
8.2K followersView on X
Rıdvan Yağlı@ridvanyagli41d
PoC
🔴 CVE-2026-80521 ve CVE-2026-52910 için Linux container escape PoC'leri yayınlandı. PoC'ler, kernel açıklarını kullanarak container izolasyonunun aşılmasını hedefliyor ve sırasıyla Ubuntu 26.04 ile Ubuntu 24.04 üzerinde test edilmiş. https://github.com/Markakd/Container_escape
Post summary
The tweet announces PoC releases for CVE‑2026‑80521 and CVE‑2026‑52910 Linux container escape vulnerabilities, cites a GitHub repository, and notes testing on Ubuntu 26.04 and 24.04.
0201161.5K
2.5K followersView on X
Ryx@PadhiyarRushi47d
PoC
Public PoC for CVE-2026-52910 is out!! Linux kernel BPF reuseport race: replace a cBPF filter on a UDP reuseport socket while another thread is still sending packets → use-after-free → reliable kernel panic. Working exploit code is on GitHub. Unpatched hosts can be crashed on demand. https://cybrmonk.com/blog/cve-2026-52910-exploit-code-now-public-linux-kernel-bpf-reuseport-crash-can-be-triggered-now #Cybersecurity #AI #AISecurity #MCP #Claude #GPT #Infosec #Trending #KernelSecurity
Post summary
The tweet announces a public proof‑of‑concept for CVE-2026-52910, provides technical details of the BPF reuseport race leading to a use‑after‑free kernel panic, and notes that exploit code is available on GitHub, with no patch or active exploitation claim.
00098844
954 followersView on X
dbugs@ptdbugs40d
PoC
A PoC/exploit has been discovered for vulnerabilities CVE-2026-52910 and CVE-2026-80521 PT ID: PT-2026-50928 Vendor: Linux Product: Linux Kernel Description: CVE-2026-52910 is a use-after-free vulnerability in the Linux kernel's reuseport classic BPF handling, while CVE-2026-80521 is a race condition in AF_UNIX garbage collection that can result in access to partially freed kernel objects. Exploitation of these vulnerabilities can allow an attacker with code execution inside a container to corrupt kernel memory and escape container isolation. References: • https://dbu.gs/vulnerability/PT-2026-50928 • https://github.com/Markakd/Container_escape
Post summary
A proof-of-concept (PoC) exploit has been discovered for CVE-2026-52910 and CVE-2026-80521 in the Linux Kernel, enabling potential container escape. Technical details are provided, but no patches or active exploitation reports are mentioned.
030111698
3.7K followersView on X
OS開発者@hacker_infra41d
Disclosure
9/18以降に追っているのは正確にはLPE 8件です。 CVE-2026-80844 CVE-2026-81000 CVE-2026-68121 CVE-2026-74469 CVE-2026-74753 CVE-2026-52910 CVE-2026-80521 CVE未採番：RustyTux / strparser・ESP-in-TCP race LPE 9/23まで、これ全部緩和策がわかるものとRed hatに報告した。異常すぎる密度だよ。
Post summary
The text tracks multiple CVEs related to Local Privilege Escalation, mentions known mitigations reported to Red Hat, and highlights the high density of vulnerabilities. The focus is on tracking and reporting vulnerabilities with technical details.
00071562
2.9K followersView on X
anya@anya_tokugawa41d
PoC
CVE-2026-52910: reuseport classic BPF - Tested Ubuntu 24.04, 6.8.0-139-generic CVE-2026-80521: AF_UNIX garbage collection - Ubuntu 26.04, 7.0.0-31-generic https://github.com/Markakd/Container_escape
Post summary
The post mentions two CVEs with short technical descriptions and shares a link to a GitHub repository that likely contains a proof of concept for container escape.
0000084
1.0K followersView on X
cybrmonk@cybr_monk50d
Exploit
CVE-2026-52910 Exploit Code Now Public: Linux Kernel BPF Reuseport Crash Can Be Triggered Now https://cybrmonk.com/blog/cve-2026-52910-exploit-code-now-public-linux-kernel-bpf-reuseport-crash-can-be-triggered-now #cybersecurity #threatintelligence https://t.co/q5WjdjQZaE
Post summary
The tweet announces that exploit code for CVE-2026-52910, a Linux kernel BPF reuseport crash vulnerability, is now publicly available. No patch, workaround, or active exploitation is mentioned.
0000050
47 followersView on X
Vulmon Vulnerability Feed@VulmonFeeds137d
Disclosure
CVE-2026-52910 Use-After-Free Vulnerability in Linux Kernel BPF Reuseport Program Handling https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-52910
Post summary
The notice details a use‑after‑free flaw in Linux Kernel BPF reuseport handling, providing a technical description but no PoC, exploit code, active exploitation evidence, or patch information.
0000047
4.1K followersView on X

CPE platform detail3 entries

Part:

Vendor:

Product:

Version:

Target SW:

Target HW:

3 of 3 entries

Part	Vendor	Product	Version	Target SW	Target HW
OS	linux	linux_kernel	-	-	-
OS	linux	linux_kernel	7.1	-	-
OS	linux	linux_kernel	7.1	-	-

Explore more

Back to dashboard linux CVEs linux_kernel vulnerabilities

What researchers are saying

CVE-2026-52910

Ryx[verified]@PadhiyarRushiExploit

The text announces public availability of working exploit code for CVE-2026-52910, a Linux kernel BPF reuseport race condition causing kernel panic, without mentioning active exploitation or patches.

pwnmachine 👾[verified]@princechaddhaPatch

The text describes an AI agent's attempt to exploit CVE-2026-52910, which caused a host kernel crash, and notes that seccomp filtering of the bpf syscall could have prevented the escape.

Rıdvan Yağlı[verified]@ridvanyagliPoC

The tweet announces PoC releases for CVE‑2026‑80521 and CVE‑2026‑52910 Linux container escape vulnerabilities, cites a GitHub repository, and notes testing on Ubuntu 26.04 and 24.04.

Ryx[verified]@PadhiyarRushiPoC

The tweet announces a public proof‑of‑concept for CVE-2026-52910, provides technical details of the BPF reuseport race leading to a use‑after‑free kernel panic, and notes that exploit code is available on GitHub, with no patch or active exploitation claim.

dbugs[verified]@ptdbugsPoC

A proof-of-concept (PoC) exploit has been discovered for CVE-2026-52910 and CVE-2026-80521 in the Linux Kernel, enabling potential container escape. Technical details are provided, but no patches or active exploitation reports are mentioned.

OS開発者[verified]@hacker_infraDisclosure

The text tracks multiple CVEs related to Local Privilege Escalation, mentions known mitigations reported to Red Hat, and highlights the high density of vulnerabilities. The focus is on tracking and reporting vulnerabilities with technical details.

anya[verified]@anya_tokugawaPoC

The post mentions two CVEs with short technical descriptions and shares a link to a GitHub repository that likely contains a proof of concept for container escape.

Brad Spengler@spendergrsecActive Exploitation

The text notes duplicate announcements of CVE‑2026‑52908 and points out that CVE‑2026‑52910 was publicly exploitable after a month, suggesting active exploitation.