CVE-2023-53577

published 4 Oct 2025 · updated 5 Aug 2026

bpf, cpumap: Make sure kthread is running before map update returns

7.8HighCVSS 7.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 640a604585aa30f93e39b17d4d6ba69fcb1e66c9, Kernel 7a1178a3671b40746830d355836b72e47ceb2490, Kernel b44d28b98f185d2f2348aa3c3636838c316f889e and 1 more.

In the Linux kernel, the following vulnerability has been resolved: bpf, cpumap: Make sure kthread is running before map update returns The following warning was reported when running stress-mode enabled xdp_redirect_cpu with some RT threads: ------------[ cut here ]------------ WARNING: CPU: 4 PID: 65 at kernel/bpf/cpumap.c:135 CPU: 4 PID: 65 Comm: kworker/4:1 Not tainted 6.5.0-rc2+ #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) Workqueue: events cpu_map_kthread_stop RIP: 0010:put_cpu_map_entry+0xda/0x220 ...... Call Trace: <TASK> ? show_regs+0x65/0x70 ? __warn+0xa5/0x240 ...... ? put_cpu_map_entry+0xda/0x220 cpu_map_kthread_stop+0x41/0x60 process_one_work+0x6b0/0xb80 worker_thread+0x96/0x720 kthread+0x1a5/0x1f0 ret_from_fork+0x3a/0x70 ret_from_fork_asm+0x1b/0x30 </TASK> The root cause is the same as commit 436901649731 ("bpf: cpumap: Fix memory leak in cpu_map_update_elem"). The kthread is stopped prematurely by kthread_stop() in cpu_map_kthread_stop(), and kthread() doesn't call cpu_map_kthread_run() at all but XDP program has already queued some frames or skbs into ptr_ring. So when __cpu_map_ring_cleanup() checks the ptr_ring, it will find it was not emptied and report a warning. An alternative fix is to use __cpu_map_ring_cleanup() to drop these pending frames or skbs when kthread_stop() returns -EINTR, but it may confuse the user, because these frames or skbs have been handled correctly by XDP program. So instead of dropping these frames or skbs, just make sure the per-cpu kthread is running before __cpu_map_entry_alloc() returns. After apply the fix, the error handle for kthread_stop() will be unnecessary because it will always return 0, so just remove it.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=4.15, >=6710e1126934d8b4372b4d2f9ae1646cd3f151bf <640a604585aa30f93e39b17d4d6ba69fcb1e66c9, >=6710e1126934d8b4372b4d2f9ae1646cd3f151bf <7a1178a3671b40746830d355836b72e47ceb2490, >=6710e1126934d8b4372b4d2f9ae1646cd3f151bf <b44d28b98f185d2f2348aa3c3636838c316f889e, >=6710e1126934d8b4372b4d2f9ae1646cd3f151bf <ecb45b852af5e88257020b88bea5ff0798d72aca640a604585aa30f93e39b17d4d6ba69fcb1e66c9, 7a1178a3671b40746830d355836b72e47ceb2490, b44d28b98f185d2f2348aa3c3636838c316f889e, ecb45b852af5e88257020b88bea5ff0798d72aca

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2023-53577 severity on Zeptric[![CVE-2023-53577](https://zeptric.io/badge/cve/CVE-2023-53577.svg)](https://zeptric.io/cve/CVE-2023-53577)