CVE-2025-39995

UNRATEDCVSS · not yet scored

Also known asEUVD-2025-34578 (ENISA EUVD) · GHSA-fxhq-536w-f9c9 (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.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

media: i2c: tc358743: Fix use-after-free bugs caused by orphan timer in probe

The state->timer is a cyclic timer that schedules work_i2c_poll and delayed_work_enable_hotplug, while rearming itself. Using timer_delete() fails to guarantee the timer isn't still running when destroyed, similarly cancel_delayed_work() cannot ensure delayed_work_enable_hotplug has terminated if already executing. During probe failure after timer initialization, these may continue running as orphans and reference the already-freed tc358743_state object through tc358743_irq_poll_timer.

The following is the trace captured by KASAN.

BUG: KASAN: slab-use-after-free in __run_timer_base.part.0+0x7d7/0x8c0 Write of size 8 at addr ffff88800ded83c8 by task swapper/1/0 ... Call Trace: dump_stack_lvl+0x55/0x70 print_report+0xcf/0x610 ? __pfx_sched_balance_find_src_group+0x10/0x10 ? __run_timer_base.part.0+0x7d7/0x8c0 kasan_report+0xb8/0xf0 ? __run_timer_base.part.0+0x7d7/0x8c0 __run_timer_base.part.0+0x7d7/0x8c0 ? rcu_sched_clock_irq+0xb06/0x27d0 ? __pfx___run_timer_base.part.0+0x10/0x10 ? try_to_wake_up+0xb15/0x1960 ? tmigr_update_events+0x280/0x740 ? _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+0x98/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 ...

Allocated by task 141: kasan_save_stack+0x24/0x50 kasan_save_track+0x14/0x30 __kasan_kmalloc+0x7f/0x90 __kmalloc_node_track_caller_noprof+0x198/0x430 devm_kmalloc+0x7b/0x1e0 tc358743_probe+0xb7/0x610 i2c_device_probe+0x51d/0x880 really_probe+0x1ca/0x5c0 __driver_probe_device+0x248/0x310 driver_probe_device+0x44/0x120 __device_attach_driver+0x174/0x220 bus_for_each_drv+0x100/0x190 __device_attach+0x206/0x370 bus_probe_device+0x123/0x170 device_add+0xd25/0x1470 i2c_new_client_device+0x7a0/0xcd0 do_one_initcall+0x89/0x300 do_init_module+0x29d/0x7f0 load_module+0x4f48/0x69e0 init_module_from_file+0xe4/0x150 idempotent_init_module+0x320/0x670 __x64_sys_finit_module+0xbd/0x120 do_syscall_64+0xac/0x280 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Freed by task 141: kasan_save_stack+0x24/0x50 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3a/0x60 __kasan_slab_free+0x3f/0x50 kfree+0x137/0x370 release_nodes+0xa4/0x100 devres_release_group+0x1b2/0x380 i2c_device_probe+0x694/0x880 really_probe+0x1ca/0x5c0 __driver_probe_device+0x248/0x310 driver_probe_device+0x44/0x120 __device_attach_driver+0x174/0x220 bus_for_each_drv+0x100/0x190 __device_attach+0x206/0x370 bus_probe_device+0x123/0x170 device_add+0xd25/0x1470 i2c_new_client_device+0x7a0/0xcd0 do_one_initcall+0x89/0x300 do_init_module+0x29d/0x7f0 load_module+0x4f48/0x69e0 init_module_from_file+0xe4/0x150 idempotent_init_module+0x320/0x670 __x64_sys_finit_module+0xbd/0x120 do_syscall_64+0xac/0x280 entry_SYSCALL_64_after_hwframe+0x77/0x7f ...

Replace timer_delete() with timer_delete_sync() and cancel_delayed_work() with cancel_delayed_work_sync() to ensure proper termination of timer and work items before resource cleanup.

This bug was initially identified through static analysis. For reproduction and testing, I created a functional emulation of the tc358743 device via a kernel module and introduced faults through the debugfs interface.

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.2%
EPSS %ILE
14th
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.2% within 30 daysSource: FIRST EPSS. 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 15, 2025

Last Modified

October 19, 2026

Vendor Advisories for CVE-2025-39995(1)

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

Patch Availability(25)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1109.107) @ jammy2026-10-19ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-10-19ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1050.53~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1052.55+fips1) @ noble2026-10-19ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2040.41) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1051.57) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1052.58+fips1) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1109.94) @ jammy2026-10-19ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1097.95) @ jammy2026-10-19ubuntu
ubuntulinux-tools-aws-edge (5.15.0.1100.107~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1041.43) @ jammy2026-10-19ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1064 (5.15.0-1064.68) @ jammy2026-10-19ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.170.159) @ jammy2026-10-19ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1099.103) @ jammy2026-10-19ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1100.90) @ jammy2026-10-19ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1097.93) @ jammy2026-10-19ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1095.95) @ jammy2026-10-19ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1095.95) @ jammy2026-10-19ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1052.52) @ jammy2026-10-19ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1049.52~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-virtual-6.8 (6.8.0-106.106) @ noble2026-10-19ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1045.46~22.04.1) @ jammy2026-10-19ubuntu
linuxKernel @ 5.4.301 (fixes >=4.3.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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (47 versions)
  • every version up to 5.10.247-1: fixed in 5.10.247-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.153-1~deb11u1 (12 versions)
  • every version up to 6.1.158-1~deb11u1: fixed in 6.1.158-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (44 versions)
  • every version up to 6.1.158-1: fixed in 6.1.158-1
—
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.16~rc7-1~exp1 (69 versions)
  • every version up to 6.16.11-1: fixed in 6.16.11-1
—

Additional Vendor Advisories

(24)

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

Frequently asked(4)

What is CVE-2025-39995?
CVE-2025-39995 is a vulnerability whose severity is not yet rated; its CVE record was published on October 15, 2025. In the Linux kernel, the following vulnerability has been resolved: media: i2c: tc358743: Fix use-after-free bugs caused by orphan timer in probe The state->timer is a cyclic timer that schedules work_i2c_poll and delayed_work_enable_hotplug, while rearming itself. Using timer_delete() fails to…
When was the CVE record for CVE-2025-39995 published?
The CVE record for CVE-2025-39995 was published on October 15, 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 19, 2026; the record at its source may have been updated since.
Is CVE-2025-39995 actively exploited?
CVE-2025-39995 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
How do I remediate CVE-2025-39995?
A fix for CVE-2025-39995 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-39995 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-39995

Explore →

Is Your Infrastructure Affected by CVE-2025-39995?

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