[CVE-2026-68181][MODERATE 7.0] mei: bus: access mei_device under device_lock on cleanup

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-68181
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: mei: bus: access mei_device under device_lock on cleanup
Commit: 441559d4c595f839b39f0ab6a4ae628427c2fd9e
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=441559d4c595f839b39f0ab6a4ae628427c2fd9e
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68181
Analysis date: Mon, 10 Aug 2026 15:13:11 -0400
ActionableScore: 5
ActionableScore lower bound: 4
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
A local MEI bus cleanup race can drop the last `mei_device` reference before `file_list` traversal, creating a use-after-free that is most likely a kernel crash DoS but should be manually reviewed for local privilege escalation feasibility.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-68181 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68181

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: MODERATE 7.0
Manual review required: YES

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-68181	MODERATE	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H';*CWE-416;CWE-362;CWE-667;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H';BEST CVSS score: '7';DESCR 'A use-after-free can occur in the MEI bus cleanup path because mei_cl_bus_dev_release could drop the last reference to the mei_device with mei_dev_bus_put and then still traverse bus file_list. Queue cleanup was also performed without holding device_lock, which creates a race window against concurrent MEI device or client state changes. For the CVSS the PR:L is used because reliable triggering is expected to require local code or access to MEI client device lifetime operations, but not necessarily full administrator privileges in all deployments. The issue is not network reachable and is triggered through local device cleanup behavior. Impact is at least local denial of service via kernel crash. In the paranoid interpretation, the explicit UAF class can justify C:H/I:H/A:H because stale kernel object access may become memory corruption depending on allocator reuse and timing.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 5)  SKIP CVE-2026-68181 UNKNOWN SKIP The Fixes patch not applied yet, so unlikely that actual: 35e8a426b16adbecae7a4e0e3c00fc8d0273db53 YES  NO NO unknown 	MAYBE	INIT UAF HARDWARE KPANIC 	-	-	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=5
ActionableScoreLower=4

## 1. ActionableScore

* Conservative score: 4
* Paranoid score: 5
* Final recommended bucket: **Actionable Moderate at minimum**::

## 2. Signal breakdown

Conservative signals:

* Local unprivileged or low-privileged trigger: +1. Triggering is local through MEI client device lifetime or cleanup behavior, not network traffic.
* Memory corruption, weak primitive: +1. The commit explicitly describes a possible use-after-free after `mei_dev_bus_put(bus)`, but the patch does not show attacker-controlled reclaim, write-after-free, callback control, or type confusion.
* Real lifetime corruption: +1. This is a reference/lifetime ordering bug where the last `mei_device` reference may be dropped before `bus->file_list` traversal.
* Reliable kernel crash / strong DoS: +1. Traversing a list through a freed `mei_device` can plausibly cause an Oops or panic.
* Hard race or special timing required: -1. The issue depends on cleanup ordering and concurrent access, so reliable triggering likely needs a narrow lifetime window.
* Privileged kernel/device-management lifetime path: +1. The corruption is in a trusted device-management cleanup path involving MEI bus/client state.

Conservative total: 4

Paranoid additional signal:

* Broad/default/common platform exposure: +1. MEI is commonly present and enabled on many Intel client and enterprise systems, even though it is hardware-dependent and not universally exposed.

Paranoid total: 5

## 3. Reachability analysis

This is not remotely reachable. The affected path is local MEI bus/client cleanup in `mei_cl_bus_dev_release()`.

A local process that can cause MEI client device teardown or influence MEI client lifetime may be able to reach the vulnerable cleanup path. Exact practical privileges depend on device-node permissions, loaded MEI client drivers, udev policy, and whether a container or service account has access to the relevant MEI device. In many deployments this is not a fully unprivileged interface, but it also should not automatically be treated as full host-root only.

Namespaces and containers may matter if MEI device nodes are passed through or if a reduced-privilege service account can interact with MEI client devices. The path is hardware-dependent but common on Intel systems.

Call-site confidence: high for the immediate bug mechanics because the release function and the problematic ordering are visible in the patch. Confidence is medium for practical attacker reachability because the provided patch does not include all userspace-facing MEI access paths.

## 4. Severity interpretation

This behaves more like an actionable Moderate issue than an ordinary Moderate cleanup bug.

Realistically, the most evidenced impact is local denial of service through kernel crash during MEI device cleanup. The use-after-free is explicit, but the patch does not demonstrate a strong privilege-escalation primitive such as controlled reclaim, stale callback dispatch, write-after-free, type confusion, or refcount takeover.

The paranoid score is still raised to 5 because kernel lifetime UAF bugs in device cleanup paths are historically worth manual review, especially when the affected subsystem can be reached by non-root or reduced-privilege local actors in some deployments. It is not a strong Important candidate based only on this patch, but it should not be auto-closed.

## 5. One-sentence report phrase

A local MEI bus cleanup race can drop the last `mei_device` reference before `file_list` traversal, creating a use-after-free that is most likely a kernel crash DoS but should be manually reviewed for local privilege escalation feasibility.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: the patch explicitly fixes a use-after-free and missing locking in a kernel device cleanup path. No strong LPE primitive is demonstrated, but the lifetime bug is concrete enough that automatic closure would be risky.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: mei: bus: access mei_device under device_lock on cleanup
Commit: 441559d4c595f839b39f0ab6a4ae628427c2fd9e
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=441559d4c595f839b39f0ab6a4ae628427c2fd9e

Commit description:

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.

Cc: stable <stable@kernel.org>
Fixes: 35e8a42 ("mei: bus: Check for still connected devices in mei_cl_bus_dev_release()")
Reviewed-by: Menachem Adin <menachem.adin@intel.com>
Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>
Link: https://patch.msgid.link/20260705151259.3054795-1-alexander.usyskin@intel.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/misc/mei/bus.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=441559d4c595f839b39f0ab6a4ae628427c2fd9e

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-68181 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-68181

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
  The Best / paranoid CVSS score: 7

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 4
  Paranoid ActionableScore: 5

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: MODERATE
KPANIC detected for this report: YES
Published priority for this report (same as in Subject): MODERATE 7.0

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).