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

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

Affects Red HatSource GCVE Database

Mentioned vulnerabilities

CVE-2024-36971

Not known to be exploited.

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.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 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

Affected software

Product	Affected	Fixed in
Red Hatredhat/kpatch-patch-4_18_0-477_43_1`pkg:rpm/redhat/kpatch-patch-4_18_0-477_43_1`Other threats	Affected =4.18.0-477.43.1.el8_8	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released an official security update in the form of a kpatch live patch module for kernel-4.18.0-477.43.1.el8_8. Applying this update will remediate the vulnerabilities. Users should follow Red Hat's official guidance at https://access.redhat.com/articles/11258 to apply the patch. Since this is a live patch, it can be applied without rebooting the system. No additional mitigation steps are indicated by the vendor.

Description

This advisory addresses two use-after-free vulnerabilities in the Linux kernel targeted by the kpatch live patch module for Red Hat Enterprise Linux 8.8. The vulnerabilities include CVE-2024-36886, affecting TIPC message reassembly, and CVE-2024-36971, affecting network route management. These flaws could potentially allow remote code execution or other impacts related to memory corruption. Red Hat has released an important security update patching these issues for kernel version 4.18.0-477.43.1.el8_8. The update is available as a kpatch live patch module, enabling modification of running kernel code without reboot. No known exploits are reported in the wild at this time.

Impact

The vulnerabilities are use-after-free bugs in kernel components that could allow an attacker to execute arbitrary code remotely or cause other memory corruption impacts. This could compromise system integrity or availability. The issues affect the kernel's TIPC message reassembly and network route management subsystems. Red Hat rates the security impact as important, indicating a high severity but not critical. There are no known exploits in the wild currently.

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:31 UTC

WeaknessesCWE-416

Technical details

References

Community reviews

Related threats