Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-68181mei: bus: access mei_device under device_lock on cleanup

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.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 13 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 6f2a6ef86b23a30b92ad57981de537bce67bfa45 – < 02e3a755086db847d795f2593ebc45e8ee4f1755
    • affected 24f4ceeaeee7983c07590149556a0e33efe2ec90 – < 441559d4c595f839b39f0ab6a4ae628427c2fd9e
    • affected 612c8d21ce6e37b73f3106aec7ffa35959d40261 – < c88c030a324c9018b77894a19b2564eb66862020
    • affected 35e8a426b16adbecae7a4e0e3c00fc8d0273db53 – < 59dd34854202d9a3faaa87a85205e553fe7150e1
    • affected 35e8a426b16adbecae7a4e0e3c00fc8d0273db53 – < 7cf79e8d682fe93777268f029668ce5e214237fd
    • affected 35e8a426b16adbecae7a4e0e3c00fc8d0273db53 – < f112ea910e554d58b4b39a4492b7d302f0f4204f
    • affected 2f29dce5a5ae06a7db32e4491d72269329a86eeb
    • affected 28de6ca5276a94b0589ae1bf026b89fa0eaf14c0
    • affected 6.1.149 – < 6.1.184
    • affected 6.6.103 – < 6.6.148
    • affected 6.12.43 – < 6.12.101
    • affected 6.15.11 – < 6.16
    • affected 6.16.2 – < 6.17
  • Linux · Linux

    • affected 6.17
    • unaffected < 6.17
    • unaffected 6.1.184 – ≤ 6.1.*
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-68181 badge
[![CVE-2026-68181](https://cveledger.app/badge/CVE-2026-68181.svg)](https://cveledger.app/cve/CVE-2026-68181)

Record last updated .