CVE-2025-38052VulnerabilityPublished 15 Sep 2025Updated 18 Sep 2026

Red Hat Security Advisory: kpatch-patch-5_14_0-570_17_1 and kpatch-patch-5_14_0-570_39_1 security update

Affects Red HatSource GCVE Database

Mentioned vulnerabilities

CVE-2025-38352

Not known to be exploited · fixed in 5.15.0-1094.103~20.04.1 : patch Red Hat soon.

Data as of 25 Oct 2026, 19:02 UTC

Severity

High

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 5.15.0-1094.103~20.04.1, 5.15.0-1090.99~20.04.1, 5.15.0-1090.97~20.04.1 +2

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Sep 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-25.

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

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
Red Hat Product Security Red Hat	Affected <5.15.0-1090.97~20.04.1 <5.15.0-1094.103~20.04.1 <5.15.0-1090.99~20.04.1 <5.15.0-152.162~20.04.1 <5.15.0-1083.86~20.04.1	Fixed in 5.15.0-1090.97~20.04.1 5.15.0-1094.103~20.04.1 5.15.0-1090.99~20.04.1 5.15.0-152.162~20.04.1 5.15.0-1083.86~20.04.1

AI-suggested

A patch is available via the kpatch-patch-5_14_0-570_17_1 and kpatch-patch-5_14_0-570_39_1 live kernel patch modules. Users should apply the update as provided by Red Hat and reboot the system for the patch to take effect. Refer to the official Red Hat advisory and article https://access.redhat.com/articles/11258 for detailed update instructions.

Description

This advisory addresses two security vulnerabilities in the Red Hat Enterprise Linux 9 kernel live patch module for kernel-5.14.0-570.17.1.el9_6. The first vulnerability (CVE-2025-38052) is a slab-use-after-free read issue in the net/tipc component. The second (CVE-2025-38352) is a race condition between handle_posix_cpu_timers() and posix_cpu_timer_del() in the posix-cpu-timers component. These issues are fixed by the kpatch-patch-5_14_0-570_17_1 and kpatch-patch-5_14_0-570_39_1 updates. Systems must be rebooted after applying the update for the fixes to take effect.

Impact

The vulnerabilities involve a use-after-free memory read and a race condition in kernel components, which could potentially lead to system instability or security issues related to kernel memory handling. The advisory rates the impact as Important (high severity). No known exploits in the wild have been reported. The issues affect Red Hat Enterprise Linux 9 kernel version 5.14.0-570.17.1.el9_6 and related builds.

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).
CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
Architecture and Design
In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.
Architecture and Design
Use thread-safe capabilities such as the data access abstraction in Spring.
Architecture and Design
Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V1.11.2 (opens in a new tab)
Attack patterns
Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions (opens in a new tab)
Leveraging Race Conditions (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

Affected software

Description

AI analysisMachine-generated, updated 19 Sep 2026, 02:14 UTC

WeaknessesCWE-416, CWE-362

Technical details

References

Community reviews

Related threats