Skip to main content

CVE-2025-37915: Vulnerability in Linux Linux

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

Description

In the Linux kernel, the following vulnerability has been resolved: net_sched: drr: 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 drr, 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 adding to the list to cover for the reentrant case. [1] https://lore.kernel.org/netdev/CAHcdcOm+03OD2j6R0=YHKqmy=VgJ8xEOKuP6c7mSgnp-TEJJbw@mail.gmail.com/

AI-Powered Analysis

AILast updated: 07/04/2025, 01:27:32 UTC

Technical Analysis

CVE-2025-37915 is a vulnerability identified in the Linux kernel's network scheduling subsystem, specifically within the Deficit Round Robin (drr) queuing discipline (qdisc) when used in conjunction with a netem child qdisc. The issue arises due to a reentrancy problem in the enqueue callback of the parent qdisc caused by certain use cases involving netem as a child. While this does not lead to a use-after-free (UAF) condition, the vulnerability causes the same classifier to be added twice to the active_list, resulting in memory corruption. This memory corruption can lead to unpredictable kernel behavior, including potential crashes or data integrity issues. The patch addressing this vulnerability adds a check to ensure that a class is not added twice to the active_list by verifying if it is already active (cl_is_active) before insertion, in addition to the existing check for queue length being zero. The vulnerability was reported by Gerrard and publicly disclosed on May 20, 2025. It affects Linux kernel versions identified by the commit hash 37d9cf1a3ce35de3df6f7d209bfb1f50cf188cea and potentially other versions sharing the same code base. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to systems running vulnerable Linux kernel versions with network scheduling configurations that use the drr qdisc with netem as a child. The impact includes potential kernel memory corruption leading to system instability or crashes, which could disrupt critical network services or infrastructure. In environments where Linux servers handle network traffic shaping or emulation—such as ISPs, telecom providers, cloud service providers, and enterprises with complex network setups—this could degrade service availability. Although no direct remote code execution or privilege escalation is indicated, memory corruption vulnerabilities in the kernel can sometimes be leveraged for more severe attacks if combined with other vulnerabilities. Therefore, the vulnerability could be a stepping stone for attackers aiming to disrupt operations or cause denial of service. Given the widespread use of Linux in European data centers, cloud environments, and embedded systems, the potential impact is significant, especially for organizations relying on precise network traffic control and quality of service.

Mitigation Recommendations

European organizations should prioritize updating their Linux kernels to versions that include the patch for CVE-2025-37915 as soon as it becomes available. Since the vulnerability is related to specific network scheduling configurations, administrators should audit their systems to identify usage of the drr qdisc with netem as a child. Where feasible, temporarily disabling or reconfiguring these qdiscs to avoid the vulnerable code path can reduce risk until patches are applied. Network administrators should also monitor kernel logs and system stability for signs of memory corruption or crashes that could indicate exploitation attempts. Implementing strict access controls and limiting administrative privileges can reduce the risk of exploitation. Additionally, organizations should maintain robust backup and recovery procedures to mitigate the impact of potential system crashes. For environments where patching is delayed, deploying network segmentation and isolating critical systems can limit exposure. Finally, staying informed through Linux kernel mailing lists and security advisories will help organizations respond promptly to any emerging exploit reports.

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: 682cd0f71484d88663aeaf75

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

Last enriched: 7/4/2025, 1:27:32 AM

Last updated: 8/11/2025, 9:12:37 PM

Views: 18

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