CVE-2025-68323

UNRATEDCVSS · not yet scored

Also known asEUVD-2025-204280 (ENISA EUVD) · GHSA-4725-8h49-mqjj (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:

usb: typec: ucsi: fix use-after-free caused by uec->work

The delayed work uec->work is scheduled in gaokun_ucsi_probe() but never properly canceled in gaokun_ucsi_remove(). This creates use-after-free scenarios where the ucsi and gaokun_ucsi structure are freed after ucsi_destroy() completes execution, while the gaokun_ucsi_register_worker() might be either currently executing or still pending in the work queue. The already-freed gaokun_ucsi or ucsi structure may then be accessed.

Furthermore, the race window is 3 seconds, which is sufficiently long to make this bug easily reproducible. The following is the trace captured by KASAN:

================================================================== BUG: KASAN: slab-use-after-free in __run_timers+0x5ec/0x630 Write of size 8 at addr ffff00000ec28cc8 by task swapper/0/0 ... Call trace: show_stack+0x18/0x24 (C) dump_stack_lvl+0x78/0x90 print_report+0x114/0x580 kasan_report+0xa4/0xf0 __asan_report_store8_noabort+0x20/0x2c __run_timers+0x5ec/0x630 run_timer_softirq+0xe8/0x1cc handle_softirqs+0x294/0x720 __do_softirq+0x14/0x20 ____do_softirq+0x10/0x1c call_on_irq_stack+0x30/0x48 do_softirq_own_stack+0x1c/0x28 __irq_exit_rcu+0x27c/0x364 irq_exit_rcu+0x10/0x1c el1_interrupt+0x40/0x60 el1h_64_irq_handler+0x18/0x24 el1h_64_irq+0x6c/0x70 arch_local_irq_enable+0x4/0x8 (P) do_idle+0x334/0x458 cpu_startup_entry+0x60/0x70 rest_init+0x158/0x174 start_kernel+0x2f8/0x394 __primary_switched+0x8c/0x94

Allocated by task 72 on cpu 0 at 27.510341s: kasan_save_stack+0x2c/0x54 kasan_save_track+0x24/0x5c kasan_save_alloc_info+0x40/0x54 __kasan_kmalloc+0xa0/0xb8 __kmalloc_node_track_caller_noprof+0x1c0/0x588 devm_kmalloc+0x7c/0x1c8 gaokun_ucsi_probe+0xa0/0x840 auxiliary_bus_probe+0x94/0xf8 really_probe+0x17c/0x5b8 __driver_probe_device+0x158/0x2c4 driver_probe_device+0x10c/0x264 __device_attach_driver+0x168/0x2d0 bus_for_each_drv+0x100/0x188 __device_attach+0x174/0x368 device_initial_probe+0x14/0x20 bus_probe_device+0x120/0x150 device_add+0xb3c/0x10fc __auxiliary_device_add+0x88/0x130 ...

Freed by task 73 on cpu 1 at 28.910627s: kasan_save_stack+0x2c/0x54 kasan_save_track+0x24/0x5c __kasan_save_free_info+0x4c/0x74 __kasan_slab_free+0x60/0x8c kfree+0xd4/0x410 devres_release_all+0x140/0x1f0 device_unbind_cleanup+0x20/0x190 device_release_driver_internal+0x344/0x460 device_release_driver+0x18/0x24 bus_remove_device+0x198/0x274 device_del+0x310/0xa84 ...

The buggy address belongs to the object at ffff00000ec28c00 which belongs to the cache kmalloc-512 of size 512 The buggy address is located 200 bytes inside of freed 512-byte region The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x4ec28 head: order:2 mapcount:0 entire_mapcount:0 nr_pages_mapped:0 pincount:0 flags: 0x3fffe0000000040(head|node=0|zone=0|lastcpupid=0x1ffff) page_type: f5(slab) raw: 03fffe0000000040 ffff000008801c80 dead000000000122 0000000000000000 raw: 0000000000000000 0000000080100010 00000000f5000000 0000000000000000 head: 03fffe0000000040 ffff000008801c80 dead000000000122 0000000000000000 head: 0000000000000000 0000000080100010 00000000f5000000 0000000000000000 head: 03fffe0000000002 fffffdffc03b0a01 00000000ffffffff 00000000ffffffff head: ffffffffffffffff 0000000000000000 00000000ffffffff 0000000000000004 page dumped because: kasan: bad access detected

Memory state around the buggy address: ffff00000ec28b80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ffff00000ec28c00: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb >ffff00000ec28c80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff00000ec28d00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff00000ec28d80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ================================================================ ---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.2%
EPSS %ILE
9th
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 (model v2026.06.15, score date 2026-10-26). 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

December 18, 2025

Last Modified

April 15, 2026

References (3)

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-raspi-6.17 (6.17.0-1010.10) @ questing2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-19.19) @ questing2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1008.9) @ questing2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.17.0-1008.9~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1010.10) @ questing2026-10-27ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1017.17) @ noble2026-10-27ubuntu
linuxKernel @ 6.17.13 (fixes >=6.16.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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.17.9-1 (85 versions)
  • every version up to 6.17.13-1: fixed in 6.17.13-1
—

All Vendor Advisories

(6)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 40× 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 99 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 130 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(4)

What is CVE-2025-68323?
CVE-2025-68323 is a vulnerability whose severity is not yet rated; its CVE record was published on December 18, 2025. In the Linux kernel, the following vulnerability has been resolved: usb: typec: ucsi: fix use-after-free caused by uec->work The delayed work uec->work is scheduled in gaokun_ucsi_probe() but never properly canceled in gaokun_ucsi_remove(). This creates use-after-free scenarios where the ucsi and…
When was the CVE record for CVE-2025-68323 published?
The CVE record for CVE-2025-68323 was published on December 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 April 15, 2026; the record at its source may have been updated since.
Is CVE-2025-68323 actively exploited?
CVE-2025-68323 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
How do I remediate CVE-2025-68323?
A fix for CVE-2025-68323 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-68323?

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

Book a Demo →Browse All CVEs