Vulnerability · Published Oct 18, 2025 · Assigned by Linux

CVE-2025-40003net: mscc: ocelot: Fix use-after-free caused by cyclic delayed work

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 18% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.3%top 82.3% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: net: mscc: ocelot: Fix use-after-free caused by cyclic delayed work The origin code calls cancel_delayed_work() in ocelot_stats_deinit() to cancel the cyclic delayed work item ocelot->stats_work. However, cancel_delayed_work() may fail to cancel the work item if it is already executing. While destroy_workqueue() does wait for all pending work items in the work queue to complete before destroying the work queue, it cannot prevent the delayed work item from being rescheduled within the ocelot_check_stats_work() function. This limitation exists because the delayed work item is only enqueued into the work queue after its timer expires. Before the timer expiration, destroy_workqueue() has no visibility of this pending work item. Once the work queue appears empty, destroy_workqueue() proceeds with destruction. When the timer eventually expires, the delayed work item gets queued again, leading to the following warning: workqueue: cannot queue ocelot_check_stats_work on wq ocelot-switch-stats WARNING: CPU: 2 PID: 0 at kernel/workqueue.c:2255 __queue_work+0x875/0xaf0 ... RIP: 0010:__queue_work+0x875/0xaf0 ... RSP: 0018:ffff88806d108b10 EFLAGS: 00010086 RAX: 0000000000000000 RBX: 0000000000000101 RCX: 0000000000000027 RDX: 0000000000000027 RSI: 0000000000000004 RDI: ffff88806d123e88 RBP: ffffffff813c3170 R08: 0000000000000000 R09: ffffed100da247d2 R10: ffffed100da247d1 R11: ffff88806d123e8b R12: ffff88800c00f000 R13: ffff88800d7285c0 R14: ffff88806d0a5580 R15: ffff88800d7285a0 FS: 0000000000000000(0000) GS:ffff8880e5725000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fe18e45ea10 CR3: 0000000005e6c000 CR4: 00000000000006f0 Call Trace: <IRQ> ? kasan_report+0xc6/0xf0 ? __pfx_delayed_work_timer_fn+0x10/0x10 ? __pfx_delayed_work_timer_fn+0x10/0x10 call_timer_fn+0x25/0x1c0 __run_timer_base.part.0+0x3be/0x8c0 ? __pfx_delayed_work_timer_fn+0x10/0x10 ? rcu_sched_clock_irq+0xb06/0x27d0 ? __pfx___run_timer_base.part.0+0x10/0x10 ? try_to_wake_up+0xb15/0x1960 ? _raw_spin_lock_irq+0x80/0xe0 ? __pfx__raw_spin_lock_irq+0x10/0x10 tmigr_handle_remote_up+0x603/0x7e0 ? __pfx_tmigr_handle_remote_up+0x10/0x10 ? sched_balance_trigger+0x1c0/0x9f0 ? sched_tick+0x221/0x5a0 ? _raw_spin_lock_irq+0x80/0xe0 ? __pfx__raw_spin_lock_irq+0x10/0x10 ? tick_nohz_handler+0x339/0x440 ? __pfx_tmigr_handle_remote_up+0x10/0x10 __walk_groups.isra.0+0x42/0x150 tmigr_handle_remote+0x1f4/0x2e0 ? __pfx_tmigr_handle_remote+0x10/0x10 ? ktime_get+0x60/0x140 ? lapic_next_event+0x11/0x20 ? clockevents_program_event+0x1d4/0x2a0 ? hrtimer_interrupt+0x322/0x780 handle_softirqs+0x16a/0x550 irq_exit_rcu+0xaf/0xe0 sysvec_apic_timer_interrupt+0x70/0x80 </IRQ> ... The following diagram reveals the cause of the above warning: CPU 0 (remove) | CPU 1 (delayed work callback) mscc_ocelot_remove() | ocelot_deinit() | ocelot_check_stats_work() ocelot_stats_deinit() | cancel_delayed_work()| ... | queue_delayed_work() destroy_workqueue() | (wait a time) | __queue_work() //UAF The above scenario actually constitutes a UAF vulnerability. The ocelot_stats_deinit() is only invoked when initialization failure or resource destruction, so we must ensure that any delayed work items cannot be rescheduled. Replace cancel_delayed_work() with disable_delayed_work_sync() to guarantee proper cancellation of the delayed work item and ensure completion of any currently executing work before the workqueue is deallocated. A deadlock concern was considered: ocelot_stats_deinit() is called in a process context and is not holding any locks that the delayed work item might also need. Therefore, the use of the _sync() variant is safe here. This bug was identified through static analysis. To reproduce the issue and validate the fix, I simulated ocelot-swit ---truncated---

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2025-40003
Debian:13linux6.12.57-1DEBIAN-CVE-2025-40003
Debian:14linux6.17.6-1DEBIAN-CVE-2025-40003
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2025-40003
Ubuntu:25.10linux6.17.0-14.14USN-8029-1
Ubuntu:25.10linux6.17.0-14.14UBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2025-40003
Ubuntu:25.10linux-aws6.17.0-1007.7UBUNTU-CVE-2025-40003
Ubuntu:25.10linux-aws6.17.0-1007.7USN-8029-2
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-aws-6.176.17.0-1007.7~24.04.1UBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2025-40003
Ubuntu:25.10linux-azure6.17.0-1008.8UBUNTU-CVE-2025-40003
Ubuntu:25.10linux-azure6.17.0-1008.8USN-8029-3
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2025-40003
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2025-40003
Ubuntu:25.10linux-gcp6.17.0-1007.7USN-8030-1
Ubuntu:25.10linux-gcp6.17.0-1007.7UBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-gcp-6.176.17.0-1008.8~24.04.1UBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-nvidia-6.176.17.0-1008.8UBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-oem-6.176.17.0-1011.11UBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-oem-6.176.17.0-1011.11USN-8048-1
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2025-40003
Ubuntu:25.10linux-oracle6.17.0-1007.7UBUNTU-CVE-2025-40003
Ubuntu:25.10linux-oracle6.17.0-1007.7USN-8029-2
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-oracle-6.176.17.0-1007.7~24.04.1UBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2025-40003
Ubuntu:25.10linux-raspi6.17.0-1008.8USN-8029-1
Ubuntu:25.10linux-raspi6.17.0-1008.8UBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-40003
Ubuntu:25.10linux-realtime6.17.0-1006.7UBUNTU-CVE-2025-40003
Ubuntu:25.10linux-realtime6.17.0-1006.7USN-8029-1
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-40003
Ubuntu:25.10linux-riscv6.17.0-14.14.1UBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2025-40003
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2025-40003
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2025-40003

Affected products (as reported)

VendorProductVersions
Linux Linux a556c76adc052c979ef9e80f0cd3fa1379ff4943 – before 2dd7540183f7410e0dc85661defcc8035c14ddc9a556c76adc052c979ef9e80f0cd3fa1379ff4943 – before c4672bdc4730d28ee8d9f65386599298047c045ea556c76adc052c979ef9e80f0cd3fa1379ff4943 – before 70acdd1eb35ffb3afdcb59e4c3bbb178da411d0fa556c76adc052c979ef9e80f0cd3fa1379ff4943 – before c3363db5d0685a8d077ade706051bbccc75f7e14a556c76adc052c979ef9e80f0cd3fa1379ff4943 – before bc9ea787079671cb19a8b25ff9f02be5ef6bfcf5
Linux Linux 4.18

References