CVE-2026-43499VulnerabilityPublished 24 Aug 2026Updated 5 Nov 2026

Red Hat Security Advisory: kpatch-patch-5_14_0-570_116_1, kpatch-patch-5_14_0-570_17_1, kpatch-patch-5_14_0-570_39_1

Affects Red HatSource GCVE Database

Compare

Mentioned vulnerabilities

Not known to be exploited.

Data as of 5 Nov 2026, 21:18 UTC

Severity

High

Rated by Threat Radar · CVSS not yet scored by NVD

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Aug 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 kpatch live patch modules for kernel-5.14.0-570.17.1.el9_6 that address these vulnerabilities. Users should apply these official patches as per Red Hat's update instructions to remediate the issues. Details on applying the update are available at https://access.redhat.com/articles/11258. Since these are live patches, they can be applied without rebooting the system.

Description

This advisory addresses multiple security vulnerabilities in the Red Hat Enterprise Linux 9.6 kernel live patch module for kernel version 5.14.0-570.17.1.el9_6. The vulnerabilities include issues in the real-time mutex handling, GFS2 filesystem, XFRM state management, and SCTP protocol implementation. These flaws could potentially lead to use-after-free conditions and improper list handling within the kernel. Red Hat has released updated kpatch modules to fix these issues.

Impact

The vulnerabilities affect kernel components responsible for synchronization (rtmutex), filesystem operations (GFS2), IPsec state management (XFRM), and SCTP networking. Exploitation could lead to kernel memory corruption such as use-after-free, potentially causing system instability or privilege escalation. The advisory rates the security impact as Important (high severity). No known exploits in the wild have been reported.

Summary

The Red Hat security advisory covers a kernel live patch module for Red Hat Enterprise Linux 9.6 targeting kernel version 5.14.0-570.17.1.el9_6. It fixes four vulnerabilities: CVE-2026-43499 addresses an issue in the rtmutex subsystem where remove_waiter() used the current task instead of waiter::task; CVE-2026-45984 fixes a use-after-free in the GFS2 iomap inline data write path; CVE-2026-46116 mitigates improper unhashing of xfrm_state lists in __xfrm_state_delete; and CVE-2026-46227 corrects SCTP list cursor revalidation after sctp_sendmsg_to_asoc() in SCTP_SENDALL. These vulnerabilities are addressed by updated kpatch-patch modules that can be loaded to modify the running kernel without rebooting.

CWE-825Expired Pointer Dereference (opens in a new tab)
Base weakness
The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.
Architecture and Design
Choose a language that provides automatic memory management.
Implementation
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-826Premature Release of Resource During Expected Lifetime (opens in a new tab)
Base weakness
The product releases a resource that is still intended to be used by itself or another actor.
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-367Time-of-check Time-of-use (TOCTOU) Race Condition (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.
Implementation
The most basic advice for TOCTOU vulnerabilities is to not perform a check before the use. This does not resolve the underlying issue of the execution of a function on a resource whose state and identity cannot be assured, but it does help to limit the false sense of security given by the check.
Implementation
When the file being altered is owned by the current user and group, set the effective gid and uid to that of the current user and group when executing this statement.
Architecture and Design
Limit the interleaving of operations on files from multiple processes.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V1.11.3 (opens in a new tab)
V11.1.6 (opens in a new tab)
V1.11.2 (opens in a new tab)
Attack patterns
Leveraging Race Conditions via Symbolic Links (opens in a new tab)
Leveraging Time-of-Check and Time-of-Use (TOCTOU) 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

Description

AI analysisMachine-generated, updated 5 Nov 2026, 21:18 UTC

Public exploits and detectionGitHub proofs of concept

WeaknessesCWE-825, CWE-826, CWE-763 +1

Technical details

References

Community reviews

Related threats