CVE-2025-7370VulnerabilityPublished 10 Jul 2025Updated 15 Jul 2025

CVE-2025-7370: Red Hat Enterprise Linux 10

Affects Red Hat Enterprise Linux 10Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 3 Aug 2025, 00:37 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Given the lack of patches or detailed technical guidance, European organizations should adopt proactive and specific mitigation strategies beyond generic advice: 1) Network Segmentation: Isolate critical RHEL 10 servers from untrusted networks and restrict inbound traffic to essential services only, using firewalls and access control lists to minimize exposure. 2) Intrusion Detection and Prevention: Deploy network-based and host-based intrusion detection systems (IDS/IPS) configured to detect anomalous traffic patterns or known attack signatures targeting RHEL 10 services. 3) Resource Limits and Monitoring: Implement resource usage limits and monitor system health metrics closely to detect early signs of DoS attempts or system instability. 4) Incident Response Preparedness: Develop and test incident response plans specifically for DoS scenarios affecting RHEL 10 systems, including rapid failover and service restoration procedures. 5) Vendor Engagement: Maintain close communication with Red Hat for timely updates, patches, and advisories related to CVE-2025-7370, and prioritize patch deployment once available. 6) Application Layer Hardening: Where possible, configure application-level timeouts and rate limiting to reduce the impact of potential DoS triggers. 7) Logging and Forensics: Enable detailed logging to facilitate post-incident analysis and attribution if exploitation occurs.

Impact

For European organizations, the impact of CVE-2025-7370 could be significant, especially for those relying on Red Hat Enterprise Linux 10 in production environments such as financial institutions, government agencies, telecommunications, and critical infrastructure providers. A successful exploitation leading to denial of service could result in downtime of essential services, loss of productivity, and potential cascading effects on dependent systems and services. Since the vulnerability does not affect confidentiality or integrity, data breaches or unauthorized data modifications are unlikely; however, service unavailability can have severe operational and reputational consequences. Organizations with high availability requirements or those subject to regulatory mandates for uptime and service continuity (e.g., GDPR mandates on data availability and integrity) may face compliance risks. Additionally, the ease of exploitation (no privileges or user interaction required) increases the threat level, as attackers can remotely trigger the DoS condition without complex prerequisites.

Summary

CVE-2025-7370 is a vulnerability identified in Red Hat Enterprise Linux (RHEL) 10, a widely used enterprise-grade Linux distribution. Although the description lacks specific technical details, the CVSS vector string provides critical insight into the nature and impact of the vulnerability. The vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H indicates a network attack vector (AV:N) with low attack complexity (AC:L), no privileges required (PR:N), and no user interaction needed (UI:N). The scope is unchanged (S:U), meaning the vulnerability affects the same security scope, and the impact is solely on availability (A:H), with no confidentiality (C:N) or integrity (I:N) impact. This suggests the vulnerability allows an unauthenticated attacker to remotely cause a denial of service (DoS) condition on affected RHEL 10 systems, potentially by crashing a critical service or the kernel itself, leading to system unavailability. The absence of known exploits in the wild and lack of detailed technical information or patches at the time of publication (July 10, 2025) implies this is a newly disclosed vulnerability, possibly under active investigation or pending remediation. Given RHEL 10's role in enterprise environments, such a DoS vulnerability could disrupt critical services and operations if exploited.

Community reviews

Loading reviews…

Exploitation evidence

What to do

AI analysisMachine-generated, updated 17 Jul 2025, 20:47 UTC

Impact

Summary

Technical details

Community reviews

Related threats