Kernel memory corruption via unlocked MEI cleanup
Published Aug 10, 2026 · Updated Aug 10, 2026
Use-after-free in Linux kernel MEI bus cleanup allows local users to corrupt memory or crash the system during device release. The mei_cl_bus_dev_release() function flushes queues without device_lock and traverses bus->file_list after mei_dev_bus_put() can free the final bus reference. Low-privileged local access and a concurrent cleanup race are required; the resulting kernel memory corruption can destabilize the host.
Summary
What happened
Use-after-free in Linux kernel MEI bus cleanup allows local users to corrupt memory or crash the system during device release. The mei_cl_bus_dev_release() function flushes queues without device_lock and traverses bus->file_list after mei_dev_bus_put() can free the final bus reference. Low-privileged local access and a concurrent cleanup race are required; the resulting kernel memory corruption can destabilize the host.
The record
- CVE
- CVE-2026-68181
- Published
- Aug 10, 2026
- Updated
- Aug 10, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-364, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 10, 2026CVE publishedPublication date reported by the CVE source.
- Aug 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=24f4ceeaeee7983c07590149556a0e33efe2ec90 <441559d4c595f839b39f0ab6a4ae628427c2fd9e
- Affected versionversion=28de6ca5276a94b0589ae1bf026b89fa0eaf14c0
- Affected versionversion=2f29dce5a5ae06a7db32e4491d72269329a86eeb
- Affected versionversion=35e8a426b16adbecae7a4e0e3c00fc8d0273db53 <59dd34854202d9a3faaa87a85205e553fe7150e1
- Affected versionversion=35e8a426b16adbecae7a4e0e3c00fc8d0273db53 <7cf79e8d682fe93777268f029668ce5e214237fd
- Affected versionversion=35e8a426b16adbecae7a4e0e3c00fc8d0273db53 <f112ea910e554d58b4b39a4492b7d302f0f4204f
- Affected versionversion=6.1.149 <6.2
- Affected versionversion=6.12.43 <6.12.101
- Affected versionversion=612c8d21ce6e37b73f3106aec7ffa35959d40261 <c88c030a324c9018b77894a19b2564eb66862020
- Affected versionversion=6.15.11 <6.16
- Affected versionversion=6.16.2 <6.17
- Affected versionversion=6.17
- Affected versionversion=6.6.103 <6.6.148
- Affected versionversion=6f2a6ef86b23a30b92ad57981de537bce67bfa45
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo