mei: bus: access mei_device under device_lock on cleanup
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 35e8a426b16adbecae7a4e0e3c00fc8d0273db53 · < f112ea910e554d58b4b39a4492b7d302f0f4204f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mei: bus: access mei_device under device_lock on cleanup
Fix couple of problems in mei_cl_bus_dev_release():
mei_cl_flush_queues() is running without lock. bus->file_list access after mei_dev_bus_put(bus) can become a use-after-free if this was the last reference to bus.
Protect queues cleanup and WARN traversal by device lock there to avoid the concurrent access problems. Move WARN traversal before mei_dev_bus_put(bus).
This file uses bus variable name for mei_device, adjust code of mei_cl_bus_dev_release() to use bus variable too.
From the CVE record · Linux
The Linux kernel’s MEI bus device cleanup can access queues without a lock and can access a device after its last reference is released. This can cause concurrent-access problems, including a use-after-free; the input does not specify an attacker path, authentication requirements, or user interaction.
Engineers running the Linux kernel should check whether their kernel includes the MEI bus cleanup fix; affected versions are not specified.