CVE-2024-36886VulnerabilityPublished 20 Aug 2024Updated 1 Sep 2026

Red Hat Security Advisory: kpatch-patch-4_18_0-553 security update

Affects Red HatSource GCVE Database

Mentioned vulnerabilities

CVE-2024-36971

Not known to be exploited : upgrade to 8.10.0 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: 1.3% chance of exploitation in 30 days – higher than 70% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.10.0

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Aug 2024
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 Red Hat to 8.10.0.

Affected software

Product	Affected	Fixed in
Red Hat Product Security Red Hat	Affected >=8.0.0 <8.10.0	Fixed in 8.10.0

AI-suggested

A security update for the kpatch-patch-4_18_0-553 module is available and should be applied promptly to affected Red Hat Enterprise Linux 8 systems. The update addresses both CVE-2024-36886 and CVE-2024-36971 vulnerabilities. Users should follow Red Hat's official guidance for applying the patch as detailed in https://access.redhat.com/articles/11258. No additional mitigations are specified or required beyond applying the official patch.

Description

Red Hat has released a security update for the kpatch-patch-4_18_0-553 kernel live patch module targeting Red Hat Enterprise Linux 8. This update addresses two use-after-free vulnerabilities in the kernel: CVE-2024-36886 affecting TIPC message reassembly and CVE-2024-36971 affecting network route management. These vulnerabilities could potentially allow remote code execution or other impacts related to memory corruption. The update is rated as Important by Red Hat and is available for multiple architectures including x86_64 and ppc64le. Users of affected Red Hat Enterprise Linux 8 versions should apply the update to mitigate these issues.

Impact

The vulnerabilities involve use-after-free conditions in kernel components that could be exploited to execute arbitrary code remotely or cause other memory corruption impacts. Successful exploitation could compromise system integrity or availability. The advisory does not report known exploits in the wild. The impact is rated Important by Red Hat, indicating a high risk to affected systems if unpatched.

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

Affected software

Description

AI analysisMachine-generated, updated 12 Sep 2026, 21:32 UTC

WeaknessesCWE-416

Technical details

References

Community reviews

Related threats