Skip to main content

CVE-2025-23151: Vulnerability in Linux Linux

High
VulnerabilityCVE-2025-23151cvecve-2025-23151
Published: Thu May 01 2025 (05/01/2025, 12:55:38 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: bus: mhi: host: Fix race between unprepare and queue_buf A client driver may use mhi_unprepare_from_transfer() to quiesce incoming data during the client driver's tear down. The client driver might also be processing data at the same time, resulting in a call to mhi_queue_buf() which will invoke mhi_gen_tre(). If mhi_gen_tre() runs after mhi_unprepare_from_transfer() has torn down the channel, a panic will occur due to an invalid dereference leading to a page fault. This occurs because mhi_gen_tre() does not verify the channel state after locking it. Fix this by having mhi_gen_tre() confirm the channel state is valid, or return error to avoid accessing deinitialized data. [mani: added stable tag]

AI-Powered Analysis

AILast updated: 07/03/2025, 22:11:34 UTC

Technical Analysis

CVE-2025-23151 is a vulnerability identified in the Linux kernel specifically within the MHI (Modem Host Interface) bus host driver. The issue arises from a race condition between the functions mhi_unprepare_from_transfer() and mhi_queue_buf(). The mhi_unprepare_from_transfer() function is used by client drivers to quiesce or pause incoming data during the teardown process of the client driver. However, if the client driver is simultaneously processing data, it may call mhi_queue_buf(), which in turn invokes mhi_gen_tre(). The vulnerability occurs because mhi_gen_tre() does not verify the channel state after acquiring a lock. If mhi_gen_tre() executes after the channel has been torn down by mhi_unprepare_from_transfer(), it attempts to access deinitialized data, leading to an invalid dereference and a kernel panic due to a page fault. This can cause the affected system to crash unexpectedly. The fix involves modifying mhi_gen_tre() to confirm the channel state is valid before proceeding or returning an error to avoid accessing invalid memory. This vulnerability affects multiple versions of the Linux kernel as indicated by the affected commit hashes. There are no known exploits in the wild at the time of publication, and no CVSS score has been assigned yet. The vulnerability is categorized as a race condition leading to a denial of service (system crash) due to improper synchronization and state validation in the MHI host driver code.

Potential Impact

For European organizations relying on Linux-based systems, especially those using hardware or embedded devices that utilize the MHI bus interface (commonly found in modem and communication subsystems), this vulnerability could lead to unexpected system crashes or denial of service conditions. This can disrupt critical services, particularly in telecommunications, industrial control systems, and embedded environments where Linux is prevalent. The kernel panic caused by this race condition could result in downtime, loss of availability, and potential cascading failures in dependent systems. While this vulnerability does not appear to allow privilege escalation or remote code execution, the availability impact alone can be significant for infrastructure providers, cloud services, and enterprises with Linux-based servers or network equipment. The lack of known exploits reduces immediate risk, but the vulnerability’s presence in the kernel means that any device running affected Linux versions is susceptible if the vulnerable MHI driver is in use. European organizations with embedded Linux devices in telecommunications or IoT sectors should be particularly vigilant.

Mitigation Recommendations

1. Apply the official Linux kernel patches that address CVE-2025-23151 as soon as they become available from trusted sources or Linux distribution vendors. 2. Identify and inventory all systems running affected Linux kernel versions, focusing on those using MHI bus interfaces, such as modems or embedded communication devices. 3. For embedded or specialized devices, coordinate with hardware vendors to obtain updated firmware or kernel versions that include the fix. 4. Implement monitoring to detect kernel panics or unexpected reboots that may indicate exploitation or triggering of this race condition. 5. Where possible, isolate critical systems using MHI interfaces from untrusted networks to reduce the risk of accidental triggering. 6. Conduct thorough testing of updated kernels in staging environments to ensure stability and compatibility before deployment. 7. Educate system administrators and security teams about the nature of this vulnerability to ensure rapid response if symptoms appear. 8. Consider implementing kernel lockdown or integrity monitoring features to detect anomalous kernel behavior related to this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2025-01-11T14:28:41.513Z
Cisa Enriched
false
Cvss Version
null
State
PUBLISHED

Threat ID: 682d9820c4522896dcbdd470

Added to database: 5/21/2025, 9:08:48 AM

Last enriched: 7/3/2025, 10:11:34 PM

Last updated: 7/30/2025, 8:52:29 PM

Views: 8

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats