In the Linux kernel, the following vulnerability has been resolved: bus: mhi: host: Fix controller cleanup on EDL sysfs failure… (CVE-2026-90402)
A high-severity vulnerability in the Linux kernel's MHI bus host controller was fixed. The issue involved improper cleanup of the controller device when sysfs file creation failed during initialization, potentially leaving the device registered incorrectly. This could lead to system instability or resource mismanagement. The vulnerability has been resolved by ensuring proper device removal on error paths.
AI Analysis
Technical Summary
The Linux kernel's mhi_register_controller() function adds a controller device before creating an optional trigger_edl sysfs file. If sysfs_create_file() fails, the error handling path previously only dropped the device reference without unregistering the device, leaving it registered improperly. The fix involves calling device_del() in the error path before put_device() to ensure proper cleanup of the controller device on failure.
Potential Impact
Improper cleanup of the controller device on sysfs creation failure could lead to resource leaks or inconsistent device state, potentially causing system instability or denial of service. The CVSS score of 7.0 indicates high severity with high impact on confidentiality, integrity, and availability, but exploitation requires local access with high attack complexity and low privileges.
Mitigation Recommendations
A fix is available and has been applied to the Linux kernel to properly clean up the controller device on sysfs creation failure. Users and administrators should update to the fixed kernel version once released. No additional mitigation is required beyond applying the official patch.
In the Linux kernel, the following vulnerability has been resolved: bus: mhi: host: Fix controller cleanup on EDL sysfs failure… (CVE-2026-90402)
Description
A high-severity vulnerability in the Linux kernel's MHI bus host controller was fixed. The issue involved improper cleanup of the controller device when sysfs file creation failed during initialization, potentially leaving the device registered incorrectly. This could lead to system instability or resource mismanagement. The vulnerability has been resolved by ensuring proper device removal on error paths.
CVSS v3.1
Score 7.0high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's mhi_register_controller() function adds a controller device before creating an optional trigger_edl sysfs file. If sysfs_create_file() fails, the error handling path previously only dropped the device reference without unregistering the device, leaving it registered improperly. The fix involves calling device_del() in the error path before put_device() to ensure proper cleanup of the controller device on failure.
Potential Impact
Improper cleanup of the controller device on sysfs creation failure could lead to resource leaks or inconsistent device state, potentially causing system instability or denial of service. The CVSS score of 7.0 indicates high severity with high impact on confidentiality, integrity, and availability, but exploitation requires local access with high attack complexity and low privileges.
Mitigation Recommendations
A fix is available and has been applied to the Linux kernel to properly clean up the controller device on sysfs creation failure. Users and administrators should update to the fixed kernel version once released. No additional mitigation is required beyond applying the official patch.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-fqr5-r6rr-x7fx
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-90402"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6aade51c55bf5e2cf5edc0a6
Added to database: 09/19/2026, 01:27:56 UTC
Last enriched: 09/19/2026, 01:46:28 UTC
Last updated: 09/19/2026, 01:46:28 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.