Live › vulnerability › CVE-2026-98772
Go to dashboardIn the Linux kernel USB serial core, port driver data could be freed while shared URB completion handlers still accessed it during disconnect or last close. A local or device-triggered race can cause a use-after-free, which may crash the kernel or be leveraged further.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with USB serial drivers for multiport devices are the ones in scope, since the flaw is in the shared URB teardown path of those drivers. Machines without USB serial hardware or drivers loaded are unlikely to be exposed. The sources do not state the trigger conditions or who can reach it.
No product ranges from the sources yet.
uname -r and compare against the fixed kernel builds in the upstream stable tree (unknown from the sources)lsmod | grep -i usbserial to see whether the USB serial driver is loadedEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
USB: serial: fix port tear down use-after-free
Some drivers for multiport devices access port driver data from completion handlers of shared URBs submitted at attach() or first open() and stopped at disconnect() or last close(), respectively.
A simple NULL check before accessing the driver data makes sure that a port state container has at least been allocated, but a completion handler can still race with port tear down.
Reorder the disconnect handling so that ports are not deregistered (and their driver data freed) until after all ports have been hung up and the driver disconnect() callback has run so that all I/O has been stopped.
This page as .md · .json · in your agent: get_signal("CVE-2026-98772")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.