CVE-2026-68181 — mei: bus: access mei_device under device_lock on cleanup
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 6f2a6ef86b23a30b92ad57981de537bce67bfa45 and < 02e3a755086db847d795f2593ebc45e8ee4f1755≥ 24f4ceeaeee7983c07590149556a0e33efe2ec90 and < 441559d4c595f839b39f0ab6a4ae628427c2fd9e≥ 612c8d21ce6e37b73f3106aec7ffa35959d40261 and < c88c030a324c9018b77894a19b2564eb66862020≥ 35e8a426b16adbecae7a4e0e3c00fc8d0273db53 and < 59dd34854202d9a3faaa87a85205e553fe7150e1≥ 35e8a426b16adbecae7a4e0e3c00fc8d0273db53 and < 7cf79e8d682fe93777268f029668ce5e214237fd≥ 35e8a426b16adbecae7a4e0e3c00fc8d0273db53 and < f112ea910e554d58b4b39a4492b7d302f0f4204fversion 2f29dce5a5ae06a7db32e4491d72269329a86eebversion 28de6ca5276a94b0589ae1bf026b89fa0eaf14c0 and 6 more≥ 6.1.149 and < 6.1.184≥ 6.6.103 and < 6.6.148≥ 6.12.43 and < 6.12.101≥ 6.15.11 and < 6.16≥ 6.16.2 and < 6.17version 6.17 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 30, 2026 · 15 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
6 on the record
- git.kernel.org/stable/c/c88c030a324c9018b77894a19b2564eb66862020
- git.kernel.org/stable/c/02e3a755086db847d795f2593ebc45e8ee4f1755
- git.kernel.org/stable/c/f112ea910e554d58b4b39a4492b7d302f0f4204f
- git.kernel.org/stable/c/441559d4c595f839b39f0ab6a4ae628427c2fd9e
- git.kernel.org/stable/c/7cf79e8d682fe93777268f029668ce5e214237fd
- git.kernel.org/stable/c/59dd34854202d9a3faaa87a85205e553fe7150e1
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 3d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 3d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 3d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 3d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 3d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 3d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-68181 is "mei: bus: access mei_device under device_lock on cleanup", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.