# CVE-2025-40003: net: mscc: ocelot: Fix use-after-free caused by cyclic delayed work CVE-2025-40003 is fixed in 13 products on 1 platform, first by DEBIAN-CVE-2025-40003, released October 18, 2025. It is not reported as exploited. Patch Radar priority: High. - Web page: https://patchblox.com/security/cve/CVE-2025-40003 - Priority: High - CVSS: 7.8 (Important) - EPSS: 0.0026 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: Oct 18, 2025 - Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-40003 ## 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: ? 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 ... 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--- ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | dtb-aarch64 opensuse-leap 16.0 | 6.12.0-160000.8.1 | [OPENSUSE-SU-2025:20172-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2025-20172-1.md) | Dec 19, 2025 | | Linux | kernel-64kb opensuse-leap 16.0 | 6.12.0-160000.8.1 | [OPENSUSE-SU-2025:20172-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2025-20172-1.md) | Dec 19, 2025 | | Linux | kernel-64kb sles 16.0 | 6.12.0-160000.8.1 | [SUSE-SU-2026:20015-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20015-1.md) | Dec 19, 2025 | | Linux | kernel-default opensuse-leap 16.0 | 6.12.0-160000.8.1 | [OPENSUSE-SU-2025:20172-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2025-20172-1.md) | Dec 19, 2025 | | Linux | kernel-default sles 16.0 | 6.12.0-160000.8.1 | [SUSE-SU-2026:20015-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20015-1.md) | Dec 19, 2025 | | Linux | kernel-default-base opensuse-leap 16.0 | 6.12.0-160000.8.1.160000.2.5 | [OPENSUSE-SU-2025:20172-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2025-20172-1.md) | Dec 19, 2025 | | Linux | kernel-default-base sles 16.0 | 6.12.0-160000.8.1.160000.2.5 | [SUSE-SU-2026:20015-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20015-1.md) | Dec 19, 2025 | | Linux | kernel-docs opensuse-leap 16.0 | 6.12.0-160000.8.1 | [OPENSUSE-SU-2025:20172-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2025-20172-1.md) | Dec 19, 2025 | | Linux | kernel-docs sles 16.0 | 6.12.0-160000.8.1 | [SUSE-SU-2026:20015-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20015-1.md) | Dec 19, 2025 | | Linux | kernel-kvmsmall opensuse-leap 16.0 | 6.12.0-160000.8.1 | [OPENSUSE-SU-2025:20172-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2025-20172-1.md) | Dec 19, 2025 | | Linux | kernel-kvmsmall sles 16.0 | 6.12.0-160000.8.1 | [SUSE-SU-2026:20015-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20015-1.md) | Dec 19, 2025 | | Linux | kernel-obs-build opensuse-leap 16.0 | 6.12.0-160000.8.1 | [OPENSUSE-SU-2025:20172-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2025-20172-1.md) | Dec 19, 2025 | | Linux | kernel-obs-qa opensuse-leap 16.0 | 6.12.0-160000.8.1 | [OPENSUSE-SU-2025:20172-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2025-20172-1.md) | Dec 19, 2025 | | Linux | kernel-obs-qa sles 16.0 | 6.12.0-160000.8.1 | [SUSE-SU-2026:20015-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20015-1.md) | Dec 19, 2025 | | Linux | kernel-rt opensuse-leap 16.0 | 6.12.0-160000.8.1 | [OPENSUSE-SU-2025:20172-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2025-20172-1.md) | Dec 19, 2025 | | Linux | kernel-source opensuse-leap 16.0 | 6.12.0-160000.8.1 | [OPENSUSE-SU-2025:20172-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2025-20172-1.md) | Dec 19, 2025 | | Linux | kernel-source sles 16.0 | 6.12.0-160000.8.1 | [SUSE-SU-2026:20015-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20015-1.md) | Dec 19, 2025 | | Linux | kernel-syms opensuse-leap 16.0 | 6.12.0-160000.8.1 | [OPENSUSE-SU-2025:20172-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2025-20172-1.md) | Dec 19, 2025 | | Linux | kernel-syms sles 16.0 | 6.12.0-160000.8.1 | [SUSE-SU-2026:20015-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20015-1.md) | Dec 19, 2025 | | Linux | kernel-zfcpdump opensuse-leap 16.0 | 6.12.0-160000.8.1 | [OPENSUSE-SU-2025:20172-1](https://patchblox.com/security/data/fix/linux/opensuse-su-2025-20172-1.md) | Dec 19, 2025 | | Linux | kernel-zfcpdump sles 16.0 | 6.12.0-160000.8.1 | [SUSE-SU-2026:20015-1](https://patchblox.com/security/data/fix/linux/suse-su-2026-20015-1.md) | Dec 19, 2025 | | Linux | linux Debian 13.5 (trixie) | 6.12.57-1 | [DEBIAN-CVE-2025-40003](https://patchblox.com/security/data/fix/linux/debian-cve-2025-40003.md) | Oct 18, 2025 | | Linux | linux Debian 14 | 6.17.6-1 | [DEBIAN-CVE-2025-40003](https://patchblox.com/security/data/fix/linux/debian-cve-2025-40003.md) | Oct 18, 2025 | --- Data as of 2026-11-09T07:25:28Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.