CVE-2026-90402

Stale MHI controller registration after sysfs failure

Published Sep 17, 2026 · Updated Sep 18, 2026

Improper cleanup in Linux kernels starting with 6.10 allows local users to leave an MHI controller registered after sysfs setup fails. In drivers/bus/mhi/host/init.c, mhi_register_controller() adds the device before creating trigger_edl, but the failure path calls put_device() without first calling device_del(). The condition requires trigger_edl creation to fail during controller registration; the upstream notice does not state the resulting security consequence.

CVSS severity7.0
High
EPSS probability0.12%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Improper cleanup in Linux kernels starting with 6.10 allows local users to leave an MHI controller registered after sysfs setup fails. In drivers/bus/mhi/host/init.c, mhi_register_controller() adds the device before creating trigger_edl, but the failure path calls put_device() without first calling device_del(). The condition requires trigger_edl creation to fail during controller registration; the upstream notice does not state the resulting security consequence.

The record

CVE
CVE-2026-90402
Published
Sep 17, 2026
Updated
Sep 18, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Sep 17, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 18, 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.

  1. Affected versionversion=17553ba8e19dee8770b3dcc597d49dcc3418f3b0 <0d5b9e66591d4e2a4376ac82c8cda889a29ba3ee
  2. Affected versionversion=17553ba8e19dee8770b3dcc597d49dcc3418f3b0 <4743959aa8d876b5b456a62e8a62eb770db7afe9
  3. Affected versionversion=17553ba8e19dee8770b3dcc597d49dcc3418f3b0 <4fb17a7c437f145353e93e6a9791f6db70e1cc63
  4. Affected versionversion=17553ba8e19dee8770b3dcc597d49dcc3418f3b0 <7943dc67250fad6ceac0dd089c6ad5776e4be71d
  5. Affected versionversion=6.10

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=17553ba8e19dee8770b3dcc597d49dcc3418f3b0 <0d5b9e66591d4e2a4376ac82c8cda889a29ba3ee; version=17553ba8e19dee8770b3dcc597d49dcc3418f3b0 <4743959aa8d876b5b456a62e8a62eb770db7afe9; version=17553ba8e19dee8770b3dcc597d49dcc3418f3b0 <4fb17a7c437f145353e93e6a9791f6db70e1cc63; version=17553ba8e19dee8770b3dcc597d49dcc3418f3b0 <7943dc67250fad6ceac0dd089c6ad5776e4be71d; version=6.10

Published CVSS scores

7.0NVDCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

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

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started