Skip to main content

CVE-2025-37914: Vulnerability in Linux Linux

High
VulnerabilityCVE-2025-37914cvecve-2025-37914
Published: Tue May 20 2025 (05/20/2025, 15:21:45 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: net_sched: ets: Fix double list add in class with netem as child qdisc As described in Gerrard's report [1], there are use cases where a netem child qdisc will make the parent qdisc's enqueue callback reentrant. In the case of ets, there won't be a UAF, but the code will add the same classifier to the list twice, which will cause memory corruption. In addition to checking for qlen being zero, this patch checks whether the class was already added to the active_list (cl_is_active) before doing the addition to cater for the reentrant case. [1] https://lore.kernel.org/netdev/CAHcdcOm+03OD2j6R0=YHKqmy=VgJ8xEOKuP6c7mSgnp-TEJJbw@mail.gmail.com/

AI-Powered Analysis

AILast updated: 07/03/2025, 18:39:56 UTC

Technical Analysis

CVE-2025-37914 is a vulnerability identified in the Linux kernel's network scheduling subsystem, specifically involving the 'ets' (Enhanced Transmission Selection) queuing discipline (qdisc) when used with a 'netem' (Network Emulator) child qdisc. The issue arises due to a logic flaw where the parent qdisc's enqueue callback can become reentrant in certain use cases involving netem as a child. This reentrancy leads to the same classifier being added twice to the active_list within the ets qdisc. While this does not result in a use-after-free (UAF) condition, the double addition causes memory corruption. The vulnerability stems from insufficient checks before adding a class to the active_list; the patch fixes this by verifying if the class is already active (cl_is_active) before adding it again, in addition to checking if the queue length (qlen) is zero. This flaw could lead to unpredictable kernel behavior, including potential crashes or memory corruption, which might be exploitable to cause denial of service or potentially escalate privileges if combined with other vulnerabilities. The vulnerability affects specific Linux kernel versions identified by commit hashes, indicating it is present in certain development or stable branches prior to the patch. No known exploits are currently reported in the wild, and the vulnerability was publicly disclosed on May 20, 2025. The technical details do not include a CVSS score, and the vulnerability does not require user interaction but involves kernel-level networking components, which are critical for system stability and security.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to systems running affected Linux kernel versions, especially those utilizing advanced network traffic control features such as ETS and netem. These features are commonly used in data centers, telecom infrastructure, cloud environments, and enterprise networks to manage bandwidth and simulate network conditions. Memory corruption in the kernel can lead to system instability, crashes, or denial of service, potentially disrupting critical services. In worst-case scenarios, attackers with local access or the ability to send crafted network traffic might exploit this flaw to escalate privileges or compromise system integrity. Given the widespread use of Linux in European government agencies, financial institutions, telecommunications providers, and cloud service providers, the impact could be significant if exploited. Additionally, the vulnerability could affect embedded Linux devices used in industrial control systems and IoT deployments prevalent in Europe, potentially impacting critical infrastructure. The absence of known exploits reduces immediate risk, but the vulnerability's presence in core kernel networking code warrants prompt attention to avoid future exploitation.

Mitigation Recommendations

European organizations should prioritize patching affected Linux kernel versions as soon as vendor updates become available. Since the vulnerability involves kernel-level network scheduling components, updating to the latest stable kernel releases that include the fix is essential. Organizations should audit their systems to identify those running vulnerable kernel versions, especially servers and network devices employing ETS and netem qdiscs. In environments where immediate patching is not feasible, mitigating risk can include limiting untrusted user access to systems, restricting the ability to configure or manipulate network qdiscs, and monitoring for unusual kernel crashes or memory corruption symptoms. Network segmentation and strict firewall rules can reduce exposure by limiting the ability of attackers to send malicious traffic that triggers the vulnerability. Additionally, organizations should implement robust kernel integrity monitoring and logging to detect anomalous behavior. For embedded and IoT devices, coordination with vendors to obtain patched firmware is critical. Finally, maintaining up-to-date incident response plans and threat intelligence feeds will help detect and respond to any emerging exploits targeting this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2025-04-16T04:51:23.967Z
Cisa Enriched
false
Cvss Version
null
State
PUBLISHED

Threat ID: 682cd0f71484d88663aeaf73

Added to database: 5/20/2025, 6:59:03 PM

Last enriched: 7/3/2025, 6:39:56 PM

Last updated: 8/21/2025, 7:03:08 AM

Views: 30

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