USB: serial: fix driver deregistration order
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 765e0ba62613fb90f09c1b5926750df0aa56f349 · < a1aa474768f69ea3a70da523f00f74c264cfa10e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
USB: serial: fix driver deregistration order
USB serial driver modules register one driver for the USB bus and one or more drivers for the ports on the USB serial bus.
When unloading a driver module, the USB driver must be deregistered before the USB serial bus drivers so that I/O is stopped before unbinding the ports to avoid use-after-free in completion handlers accessing port data.
Note that the "new_id" attributes must first be removed to prevent new ids from being added and triggering a probe of the USB driver after it has been deregistered.
From the CVE record · Linux
The Linux kernel's USB serial driver modules can deregister drivers in an order that allows I/O completion handlers to access freed port data during module unloading. The input does not specify whether an attacker can trigger this, or any authentication, network, or user-interaction requirements.
Engineers running the Linux kernel with USB serial driver modules should check their systems; affected versions are not specified.