CVE-2025-38448
What it is
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: u_serial: Fix race condition in TTY wakeup A race condition occurs when gs_start_io() calls either gs_start_rx() or gs_start_tx(), as those functions briefly drop the port_lock for usb_ep_queue(). This allows gs_close() and gserial_disconnect() to clear port.tty and port_usb, respectively. Use the null-safe TTY Port helper function to wake up TTY. Example CPU1: CPU2: gserial_connect() // lock gs_close() // await lock gs_start_rx() // unlock usb_ep_queue() gs_close() // lock, reset port.tty and unlock gs_start_rx() // lock tty_wakeup() // NPE
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 4.7 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-362 · Race condition
- Record status
- Analyzed
Affected
- Linux Kernel < 5.4.296
- Linux Kernel < 5.10.240
- Linux Kernel < 5.15.189
- Linux Kernel < 6.1.146
- Linux Kernel < 6.6.99
- Linux Kernel < 6.12.39
- Linux Kernel < 6.15.7
- Linux Kernel 6.16
Attack profile CVSS 3.1 · 4.7
- Attack vector
- Local
- Complexity
- High
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-38448.md and follow it. Check whether this project is affected by CVE-2025-38448. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/18d58a467ccf011078352d91b4d6a0108c7318e8
- https://git.kernel.org/stable/c/a5012673d49788f16bb4e375b002d7743eb642d9
- https://git.kernel.org/stable/c/abf3620cba68e0e51e5c21054ce4f925f75b3661
- https://git.kernel.org/stable/c/c529c3730bd09115684644e26bf01ecbd7e2c2c9
- https://git.kernel.org/stable/c/c6eb4a05af3d0ba3bc4e8159287722fb9abc6359
- https://git.kernel.org/stable/c/c8c80a3a35c2e3488409de2d5376ef7e662a2bf5
- https://git.kernel.org/stable/c/d43657b59f36e88289a6066f15bc9a80df5014eb
- https://git.kernel.org/stable/c/ee8d688e2ba558f3bb8ac225113740be5f335417
References
- https://git.kernel.org/stable/c/18d58a467ccf011078352d91b4d6a0108c7318e8
- https://git.kernel.org/stable/c/a5012673d49788f16bb4e375b002d7743eb642d9
- https://git.kernel.org/stable/c/abf3620cba68e0e51e5c21054ce4f925f75b3661
- https://git.kernel.org/stable/c/c529c3730bd09115684644e26bf01ecbd7e2c2c9
- https://git.kernel.org/stable/c/c6eb4a05af3d0ba3bc4e8159287722fb9abc6359
- https://git.kernel.org/stable/c/c8c80a3a35c2e3488409de2d5376ef7e662a2bf5
- https://git.kernel.org/stable/c/d43657b59f36e88289a6066f15bc9a80df5014eb
- https://git.kernel.org/stable/c/ee8d688e2ba558f3bb8ac225113740be5f335417
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html