CVE-2026-46189VulnerabilityPublished 28 Sep 2026Updated 31 Oct 2026

Red Hat Security Advisory: kpatch-patch-5_14_0-284_134_1, kpatch-patch-5_14_0-284_148_1

Affects Red HatSource GCVE Database

Compare

Mentioned vulnerabilities

CVE-2026-74581

Not known to be exploited.

Data as of 31 Oct 2026, 11:05 UTC

Severity

High

Rated by Threat Radar · CVSS not yet scored by NVD

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Sep 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 30 Oct 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 official live patch updates (kpatch-patch packages) for affected kernel versions in Red Hat Enterprise Linux 9.2. Users should apply these updates promptly following Red Hat's documented procedures to remediate the vulnerabilities. Since this is a live patch module, it can be applied without rebooting the system. No additional mitigation steps are indicated by the vendor advisory.

Description

This advisory addresses two security vulnerabilities in the Red Hat Enterprise Linux 9.2 kernel live patch module for kernel-5.14.0-284.134.1.el9_2. The first vulnerability (CVE-2026-46189) is a double free error in the RDMA/vmw_pvrdma component during the pvrdma_alloc_ucontext() error path. The second vulnerability (CVE-2026-74581) is a use-after-free in the IPv6 networking code due to a stale pointer in fib6_rule_suppress. Both issues could lead to kernel memory corruption. Red Hat has released live patch updates to address these vulnerabilities.

Impact

The vulnerabilities involve kernel memory management errors: a double free and a use-after-free. Such flaws can lead to memory corruption in the kernel, which may cause system crashes or potentially allow an attacker to execute arbitrary code with kernel privileges. The advisory rates the security impact as Important (high severity). No known exploits in the wild have been reported at this time.

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 31 Oct 2026, 11:05 UTC

WeaknessesCWE-763, CWE-416

Technical details

References

Community reviews

Related threats