CVE-2026-68181

mei: bus: access mei_device under device_lock on cleanup

N/A
Published: August 10, 2026 at 11:59 AM UTC
Updated: August 23, 2026 at 01:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 6.15.11v ≥ 6.16.26.1.149 ≤ v < 6.1.1846.12.43 ≤ v < 6.12.1016.15.11 ≤ v < 6.166.16.2 ≤ v < 6.176.17 ≤ v < 6.18.426.17 ≤ v < 7.1.66.17 ≤ v < 7.26.6.103 ≤ v < 6.6.14824f4ceeaeee7983c07590149556a0e33efe2ec9028de6ca5276a94b0589ae1bf026b89fa0eaf14c02f29dce5a5ae06a7db32e4491d72269329a86eeb35e8a426b16adbecae7a4e0e3c00fc8d0273db536.1.1496.12.436.15.116.16.26.176.6.103612c8d21ce6e37b73f3106aec7ffa35959d402616f2a6ef86b23a30b92ad57981de537bce67bfa45
Vendor states this is fixed in 02e3a755086db847d795f2593ebc45e8ee4f1755 (fixed)
Vendor states this is fixed in 441559d4c595f839b39f0ab6a4ae628427c2fd9e (fixed)
Vendor states this is fixed in 59dd34854202d9a3faaa87a85205e553fe7150e1 (fixed)
Vendor states this is fixed in 7cf79e8d682fe93777268f029668ce5e214237fd (fixed)
Vendor states this is fixed in c88c030a324c9018b77894a19b2564eb66862020 (fixed)
Vendor states this is fixed in f112ea910e554d58b4b39a4492b7d302f0f4204f (fixed)
Vendor states this is fixed in 6.1.184 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Affected range stops below 6.16, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.17 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card