Kernel memory corruption via delayed-work rescheduling
Published Oct 18, 2025 · Updated Oct 18, 2025
Use-after-free in Linux before 6.18-rc1 allows local users to corrupt kernel memory during Ocelot switch device teardown. The ocelot_stats_deinit() path uses cancel_delayed_work(), which permits ocelot_check_stats_work() to reschedule after its workqueue is destroyed. Reaching the flaw requires local low-privileged access and a race during initialization failure or resource destruction; successful triggering corrupts kernel memory and interrupts or destabilizes the host.
Summary
What happened
Use-after-free in Linux before 6.18-rc1 allows local users to corrupt kernel memory during Ocelot switch device teardown. The ocelot_stats_deinit() path uses cancel_delayed_work(), which permits ocelot_check_stats_work() to reschedule after its workqueue is destroyed. Reaching the flaw requires local low-privileged access and a race during initialization failure or resource destruction; successful triggering corrupts kernel memory and interrupts or destabilizes the host.
The record
- CVE
- CVE-2025-40003
- Published
- Oct 18, 2025
- Updated
- Oct 18, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 18, 2025CVE publishedPublication date reported by the CVE source.
- Oct 18, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.18
- Affected versionversion=a556c76adc052c979ef9e80f0cd3fa1379ff4943 <bc9ea787079671cb19a8b25ff9f02be5ef6bfcf5
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo