Skip to main content

CVE-2025-21914: Vulnerability in Linux Linux

High
VulnerabilityCVE-2025-21914cvecve-2025-21914
Published: Tue Apr 01 2025 (04/01/2025, 15:40:51 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: slimbus: messaging: Free transaction ID in delayed interrupt scenario In case of interrupt delay for any reason, slim_do_transfer() returns timeout error but the transaction ID (TID) is not freed. This results into invalid memory access inside qcom_slim_ngd_rx_msgq_cb() due to invalid TID. Fix the issue by freeing the TID in slim_do_transfer() before returning timeout error to avoid invalid memory access. Call trace: __memcpy_fromio+0x20/0x190 qcom_slim_ngd_rx_msgq_cb+0x130/0x290 [slim_qcom_ngd_ctrl] vchan_complete+0x2a0/0x4a0 tasklet_action_common+0x274/0x700 tasklet_action+0x28/0x3c _stext+0x188/0x620 run_ksoftirqd+0x34/0x74 smpboot_thread_fn+0x1d8/0x464 kthread+0x178/0x238 ret_from_fork+0x10/0x20 Code: aa0003e8 91000429 f100044a 3940002b (3800150b) ---[ end trace 0fe00bec2b975c99 ]--- Kernel panic - not syncing: Oops: Fatal exception in interrupt.

AI-Powered Analysis

AILast updated: 06/30/2025, 10:41:23 UTC

Technical Analysis

CVE-2025-21914 is a vulnerability in the Linux kernel affecting the Qualcomm SLIMbus (Serial Low-power Inter-chip Media Bus) controller driver, specifically within the slim_qcom_ngd_ctrl module. The issue arises in the slim_do_transfer() function, which handles data transfers over the SLIMbus interface. When an interrupt delay occurs, slim_do_transfer() returns a timeout error but fails to free the transaction ID (TID) associated with the transfer. This leads to the reuse of an invalid TID, causing an invalid memory access in the interrupt handler function qcom_slim_ngd_rx_msgq_cb(). The invalid memory access can trigger a kernel panic due to a fatal exception in interrupt context, resulting in a denial of service (DoS) condition. The call trace provided shows the sequence of kernel functions leading to the panic, confirming that the issue occurs during interrupt processing and tasklet execution. The root cause is a missing cleanup step in the error path of slim_do_transfer(), which was fixed by ensuring the TID is freed before returning the timeout error. This vulnerability affects specific Linux kernel versions identified by the commit hash afbdcc7c384b0d446da08b1e0901dc176b41b9e0. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet. The vulnerability requires kernel-level access to trigger and does not involve user-space interaction directly but can be exploited by triggering conditions that cause interrupt delays on affected hardware using the Qualcomm SLIMbus controller.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to systems running Linux kernels with the affected Qualcomm SLIMbus driver, which is commonly found in embedded devices, mobile platforms, and specialized industrial equipment. The impact includes potential denial of service through kernel panics, leading to system crashes and downtime. This can disrupt critical infrastructure, telecommunications equipment, or industrial control systems that rely on stable Linux-based platforms with Qualcomm SLIMbus hardware. Confidentiality and integrity impacts are limited since the vulnerability causes memory corruption leading to crashes rather than arbitrary code execution or data leakage. However, availability impact can be significant in environments where uptime is critical, such as healthcare, manufacturing, or telecommunications sectors prevalent in Europe. The lack of known exploits reduces immediate risk, but the vulnerability could be leveraged in targeted attacks or by malware aiming to cause disruption. Organizations using affected Linux versions in their infrastructure should consider this a medium to high risk for availability depending on their reliance on affected hardware and kernel versions.

Mitigation Recommendations

To mitigate this vulnerability, European organizations should: 1) Identify and inventory Linux systems using Qualcomm SLIMbus controllers, especially those running kernel versions matching the affected commit hash. 2) Apply the official Linux kernel patches that fix the TID freeing issue in slim_do_transfer() as soon as they become available from trusted sources or Linux distribution vendors. 3) If immediate patching is not possible, consider isolating or limiting access to affected systems to reduce the risk of triggering interrupt delays. 4) Monitor system logs for kernel panic events or related error messages indicating slim_qcom_ngd_ctrl issues. 5) Engage with hardware and software vendors to confirm SLIMbus usage and coordinate patch deployment. 6) Implement robust system monitoring and automated recovery mechanisms to minimize downtime in case of crashes. 7) For embedded or industrial devices, coordinate firmware or kernel updates with device manufacturers to ensure timely remediation. These steps go beyond generic advice by focusing on hardware-specific identification, patch prioritization, and operational continuity planning.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2024-12-29T08:45:45.787Z
Cisa Enriched
false
Cvss Version
null
State
PUBLISHED

Threat ID: 682d9833c4522896dcbe8ba2

Added to database: 5/21/2025, 9:09:07 AM

Last enriched: 6/30/2025, 10:41:23 AM

Last updated: 8/15/2025, 6:43:22 PM

Views: 16

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