CVE-2025-40003

UNRATEDCVSS · not yet scored

Also known asEUVD-2025-34986 (ENISA EUVD) · GHSA-29x3-q6jr-jf4j (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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---

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.3%
EPSS %ILE
17th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 18, 2025

Last Modified

October 30, 2026

References (5)

Vendor Advisories for CVE-2025-40003(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-14.14) @ questing2026-10-30ubuntu
ubuntulinux-tools-gcp-64k-6.17 (6.17.0-1007.7) @ questing2026-10-30ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1007.7) @ questing2026-10-30ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1011.11) @ noble2026-10-30ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1008.8) @ questing2026-10-30ubuntu
linuxKernel @ 6.12.54 (fixes >=4.18.0)—osv
linuxKernel @ 6.6.160 (fixes >=4.18.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.57-1~bpo12+1 (6 versions)
  • every version up to 6.12.57-1: fixed in 6.12.57-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.17.5-1~exp1 (75 versions)
  • every version up to 6.17.6-1: fixed in 6.17.6-1
—

Additional Vendor Advisories

(5)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 57× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 239 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 141 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-06 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  2. 2026-11-05 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  3. 2026-11-04 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  4. 2026-11-03 16:44 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  5. 2026-11-02 16:42 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  6. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  7. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  8. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  9. 2026-10-30 13:40 UTCVendor advisory
  10. 2026-10-30 13:40 UTCGHSA enrichmentGHSA-29x3-q6jr-jf4j
  11. 2026-10-30 13:26 UTCNVD update
  12. 2026-10-30 12:34 UTCEG score recompute
  13. 2026-10-30 12:34 UTCVendor advisory
  14. 2026-10-30 12:34 UTCGHSA enrichmentGHSA-29x3-q6jr-jf4j
  15. 2026-10-30 12:30 UTCMITRE cvelistV5
  16. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  17. 2026-10-29 08:25 UTCOSV refresh
  18. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  19. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  20. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  21. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  22. 2026-10-25 16:28 UTCEG score recompute
  23. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  24. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  25. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
Show 73 more
  1. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  2. 2026-10-21 14:02 UTCVendor advisory
  3. 2026-10-21 14:02 UTCGHSA enrichmentGHSA-29x3-q6jr-jf4j
  4. 2026-10-21 13:45 UTCNVD update
  5. 2026-10-21 13:13 UTCVendor advisory
  6. 2026-10-21 13:13 UTCGHSA enrichmentGHSA-29x3-q6jr-jf4j
  7. 2026-10-21 12:36 UTCEG score recompute
  8. 2026-10-21 12:36 UTCVendor advisory
  9. 2026-10-21 12:35 UTCGHSA enrichmentGHSA-29x3-q6jr-jf4j
  10. 2026-10-21 12:26 UTCMITRE cvelistV5
  11. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  12. 2026-10-19 22:36 UTCEG score recompute
  13. 2026-10-19 22:36 UTCVendor advisory
  14. 2026-10-19 22:36 UTCGHSA enrichmentGHSA-29x3-q6jr-jf4j
  15. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  16. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  17. 2026-10-18 05:35 UTCEG score recompute
  18. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  19. 2026-10-16 16:38 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  20. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  21. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  22. 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  23. 2026-10-12 17:06 UTCEG score recompute
  24. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  25. 2026-10-11 20:39 UTCEG score recompute
  26. 2026-10-11 18:50 UTCEG score recompute
  27. 2026-10-11 15:27 UTCEG score recompute
  28. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  29. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  30. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  31. 2026-10-08 17:09 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  32. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  33. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  34. 2026-10-06 07:49 UTCOSV refresh
  35. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  36. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  37. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  38. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  39. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  40. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  41. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  42. 2026-09-26 00:24 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  43. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  44. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  45. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  46. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  47. 2026-09-17 19:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  48. 2026-09-16 15:25 UTCOSV refresh
  49. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  50. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  51. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  52. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  53. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  54. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  55. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  56. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  57. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  58. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  59. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  60. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  61. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  62. 2026-09-01 04:38 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  63. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  64. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  65. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  66. 2026-08-28 15:23 UTCOSV refresh
  67. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  68. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  69. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  70. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  71. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  72. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  73. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.2% · 13th percentile

Related CVEs(same vendor)

Frequently asked(4)

What is CVE-2025-40003?
CVE-2025-40003 is a vulnerability whose severity is not yet rated; its CVE record was published on October 18, 2025. 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…
When was the CVE record for CVE-2025-40003 published?
The CVE record for CVE-2025-40003 was published on October 18, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 30, 2026; the record at its source may have been updated since.
Is CVE-2025-40003 actively exploited?
CVE-2025-40003 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
How do I remediate CVE-2025-40003?
A fix for CVE-2025-40003 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-40003 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-40003

Explore →

Is Your Infrastructure Affected by CVE-2025-40003?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs