CVE-2025-38180VulnerabilityPublished 8 Apr 2026Updated 5 Nov 2026

Red Hat Security Advisory: kernel security update

Affects Linux kernelSource GCVE Database

Compare

Mentioned vulnerabilities

Not known to be exploited.

Data as of 5 Nov 2026, 16:02 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 5 Nov 2026.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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

Red Hat has released updated kernel packages that fix these vulnerabilities. Users should apply the provided kernel update for Red Hat Enterprise Linux 9.2 and reboot their systems to ensure the fixes take effect. Refer to the Red Hat advisory RHSA-2026:6986 and the linked article https://access.redhat.com/articles/11258 for detailed update instructions.

Description

This Red Hat security advisory addresses multiple vulnerabilities in the Linux kernel packages, including use-after-free and double free flaws in various subsystems. The vulnerabilities affect the ATM subsystem, the exFAT filesystem, and the macvlan network driver. These issues could lead to use-after-free conditions or denial of service. The advisory rates the overall impact as moderate and provides updated kernel packages to remediate these flaws. A system reboot is required to apply the updates.

Impact

Successful exploitation of these vulnerabilities could lead to use-after-free conditions or double free errors in kernel components, potentially causing system instability or denial of service. The advisory classifies the security impact as moderate. There is no indication of active exploitation in the wild.

Summary

The advisory covers three kernel vulnerabilities: CVE-2025-38180 is a use-after-free vulnerability in the ATM subsystem; CVE-2025-38206 is a double free vulnerability in the exFAT filesystem that can cause denial of service; CVE-2026-23001 is a possible use-after-free in the macvlan_forward_source() function. These flaws are addressed in updated kernel packages for Red Hat Enterprise Linux 9.2 and related variants. The advisory recommends applying the update and rebooting the system to activate the fixes.

CWE-911Improper Update of Reference Count (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count.
CWE-763Release of Invalid Pointer or Reference (opens in a new tab)
Base weakness
The product attempts to return a memory resource to the system, but it calls the wrong release function or calls the appropriate release function incorrectly.
Implementation
Only call matching memory management functions. Do not mix and match routines. For example, when you allocate a buffer with malloc(), dispose of the original pointer with free().
Implementation
When programming in C++, consider using smart pointers provided by the boost library to help correctly and consistently manage memory.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-416Use After Free (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #7
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Architecture and Design · Language Selection
Choose a language that provides automatic memory management.
Implementation · Attack Surface Reduction
When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 5 Nov 2026, 16:02 UTC

WeaknessesCWE-911, CWE-763, CWE-416

Technical details

References

Community reviews

Related threats