Vulnerability · Published Dec 18, 2025 · Assigned by Linux

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

Unrated

In plain English

A security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 10% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS )–Not rated
Exploit odds (30 days)0.2%top 90.2% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official description

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

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:14linux6.17.13-1DEBIAN-CVE-2025-68323
Ubuntu:25.10linux6.17.0-19.19UBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2025-68323
Ubuntu:25.10linux-aws6.17.0-1009.9UBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2025-68323
Ubuntu:24.04:LTSlinux-aws-6.176.17.0-1009.9~24.04.2UBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2025-68323
Ubuntu:25.10linux-azure6.17.0-1010.10UBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2025-68323
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2025-68323
Ubuntu:24.04:LTSlinux-azure-6.176.17.0-1010.10~24.04.1UBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2025-68323
Ubuntu:25.10linux-azure-fdeno fix listedUBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2025-68323
Ubuntu:25.10linux-gcp6.17.0-1009.9UBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2025-68323
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2025-68323
Ubuntu:24.04:LTSlinux-gcp-6.176.17.0-1009.9~24.04.3UBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2025-68323
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2025-68323
Ubuntu:24.04:LTSlinux-hwe-6.176.17.0-19.19~24.04.2UBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2025-68323
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2025-68323
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2025-68323
Ubuntu:24.04:LTSlinux-nvidia-6.176.17.0-1018.18UBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2025-68323
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2025-68323
Ubuntu:24.04:LTSlinux-oem-6.176.17.0-1017.17UBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2025-68323
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2025-68323
Ubuntu:25.10linux-oracle6.17.0-1009.9UBUNTU-CVE-2025-68323
Ubuntu:24.04:LTSlinux-oracle-6.176.17.0-1009.9~24.04.1UBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2025-68323
Ubuntu:25.10linux-raspi6.17.0-1010.10UBUNTU-CVE-2025-68323
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-68323
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2025-68323
Ubuntu:25.10linux-realtime6.17.0-1008.9UBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-68323
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2025-68323
Ubuntu:25.10linux-riscv6.17.0-19.19.1UBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2025-68323
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2025-68323
Ubuntu:24.04:LTSlinux-riscv-6.176.17.0-19.19.1~24.04.1UBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2025-68323
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2025-68323

Affected products (as reported)

VendorProductVersions
Linux Linux 00327d7f2c8c512c9b168daae02c8b989f79ec71 – before d8ac85c76a4279979b917d4b2f9c6b07d978300300327d7f2c8c512c9b168daae02c8b989f79ec71 – before a880ef71a1c8da266b88491213c37893e212648900327d7f2c8c512c9b168daae02c8b989f79ec71 – before 2b7a0f47aaf2439d517ba0a6b29c66a535302154
Linux Linux 6.16

References