CVE-2026-31474VulnerabilityPublished 22 Jun 2026Updated 29 Oct 2026

Red Hat Security Advisory: kernel security, bug fix, and enhancement update

Affects Red Hat kernel security,Source GCVE Database

Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-31474· High 7.8

Not known to be exploited · CVSS 7.8 High · fixed in Red Hat package updates : patch Red Hat kernel security, soon.

Data as of 29 Oct 2026, 10:37 UTC

CVSS 3.1 base score

7.8High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in eec8a1b18a79600bd4419079dc0026c1db72a830, cb3d6efa78460e6d50bf68806d0db66265709f64, 9649d051e54413049c009638ec1dc23962c884a4 +2

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Apr 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 29 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

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 96d1c81e6a0478535342dff6c730adb076cd84e8, < eec8a1b18a79600bd4419079dc0026c1db72a830	Fixed in eec8a1b18a79600bd4419079dc0026c1db72a830
LinuxLinux	Affected ≥ 96d1c81e6a0478535342dff6c730adb076cd84e8, < cb3d6efa78460e6d50bf68806d0db66265709f64	Fixed in cb3d6efa78460e6d50bf68806d0db66265709f64
LinuxLinux	Affected ≥ 96d1c81e6a0478535342dff6c730adb076cd84e8, < 9649d051e54413049c009638ec1dc23962c884a4	Fixed in 9649d051e54413049c009638ec1dc23962c884a4
LinuxLinux	Affected ≥ 96d1c81e6a0478535342dff6c730adb076cd84e8, < 424e95d62110cdbc8fd12b40918f37e408e35a92	Fixed in 424e95d62110cdbc8fd12b40918f37e408e35a92
LinuxLinux	Affected ≥ 96d1c81e6a0478535342dff6c730adb076cd84e8, < 2e62e7051eca75a7f2e3d52d62ec10d7d7aa358c	Fixed in 2e62e7051eca75a7f2e3d52d62ec10d7d7aa358c
LinuxLinux	Affected =6.4	Fixed in–

AI-suggested

A security update for the Red Hat Enterprise Linux 9 kernel packages is available that addresses these vulnerabilities. Users should apply the update promptly and reboot their systems to ensure the fixes take effect. For detailed update instructions, refer to the Red Hat advisory at https://access.redhat.com/articles/11258. No additional mitigations are specified beyond applying the official update.

Description

This Red Hat security advisory addresses multiple vulnerabilities in the Linux kernel packages for Red Hat Enterprise Linux 9. The update fixes several use-after-free, double free, stack buffer overflow, and race condition issues across various kernel subsystems including CAN, MPTCP, Xen, Bluetooth, network scheduling, RDMA, WiFi, and storage. These vulnerabilities could potentially lead to system instability or privilege escalation if exploited. The advisory also includes bug fixes and enhancements unrelated to security. The update requires a system reboot to take effect.

Impact

The vulnerabilities fixed in this advisory include use-after-free, double free, stack buffer overflow, and race conditions in critical kernel components. Exploitation could lead to system crashes, denial of service, or potentially privilege escalation. The advisory rates the security impact as important, indicating a high severity level. No known exploits in the wild have been reported at this time.

Summary

Red Hat issued a security advisory for Red Hat Enterprise Linux 9 kernel packages that fixes multiple security vulnerabilities. These include a use-after-free in isotp_sendmsg() (CVE-2026-31474), slab-use-after-free in __inet_lookup_established (CVE-2026-31669), double free via VMA splitting in Xen privcmd (CVE-2026-31787), stack buffer overflow in Bluetooth hci_le_big_create_sync (CVE-2026-31772), and other issues affecting Bluetooth, network, storage, and RDMA subsystems. The advisory provides fixes for these vulnerabilities and additional bug fixes and enhancements. The update is rated as important by Red Hat Product Security and requires a reboot to apply.

CWE-364Signal Handler Race Condition (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product uses a signal handler that introduces a race condition.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design
Design signal handlers to only set flags, rather than perform complex functionality. These flags can then be checked and acted upon within the main program loop.
Implementation
Only use reentrant functions within signal handlers. Also, use validation to ensure that state is consistent while performing asynchronous actions that affect the state of execution.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V1.11.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
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-787Out-of-bounds Write (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #5
The product writes data past the end, or before the beginning, of the intended buffer.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
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.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
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-772Missing Release of Resource after Effective Lifetime (opens in a new tab)
Base weaknessLikelihood of exploit: High
The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
It is good practice to be responsible for freeing all resources you allocate and to be consistent with how and where you free resources in a function. If you allocate resources that you intend to free upon completion of the function, you must be sure to free the resources at all exit points for that function including…
Operation · Architecture and Design · Resource Limitation
Use resource-limiting settings provided by the operating system or environment. For example, when managing system resources in POSIX, setrlimit() can be used to set limits for certain types of resources, and getrlimit() can determine how many resources are available.
Attack patterns
HTTP DoS (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-1341Multiple Releases of Same Resource or Handle (opens in a new tab)
Base weakness
The product attempts to close or release a resource or handle more than once, without any successful open between the close operations.
Implementation
Change the code's logic so that the resource is only closed once. This might require simplifying or refactoring. This fix can be simple to do in small code blocks, but more difficult when multiple closes are buried within complex conditionals.
Implementation · Refactoring
It can be effective to implement a flag that is (1) set when the resource is opened, (2) cleared when it is closed, and (3) checked before closing. This approach can be useful when there are disparate cases in which closes must be performed.
Implementation · Refactoring
When closing a resource, set the resource's associated variable to NULL or equivalent value for the given language. Some APIs will ignore this null value without causing errors.
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-413Improper Resource Locking (opens in a new tab)
Base weakness
The product must have exclusive access to a resource, but it does not lock or does not correctly lock that resource.
Architecture and Design
Use a non-conflicting privilege scheme.
Architecture and Design · Implementation
Use synchronization when locking a resource.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-1288Improper Validation of Consistency within Input (opens in a new tab)
Base weakness
The product receives a complex input with multiple elements or fields that must be consistent with each other, but it does not validate or incorrectly validates that the input is actually consistent.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
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-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-1058Invokable Control Element in Multi-Thread Context with non-Final Static Storable or Member Element (opens in a new tab)
Base weakness
The code contains a function or method that operates in a multi-threaded environment but owns an unsafe non-final static storable or member data element.

GCVE source: db.gcve.eu
Csaf Category: csaf_security_advisory
Csaf Version: 2.0
Publisher: Red Hat Product Security
Advisory ID: RHSA-2026:27789
Vendor Severity: high
CVE Count: 17
Additional Cves: CVE-2026-31669, CVE-2026-31772, CVE-2026-31787, CVE-2026-43260, CVE-2026-43279, CVE-2026-43414, CVE-2026-45984, CVE-2026-46056, CVE-2026-46117, CVE-2026-46125, CVE-2026-46135, CVE-2026-46145, CVE-2026-46152, CVE-2026-46166, CVE-2026-46173, CVE-2026-46331

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2026, 10:33 UTC

WeaknessesCWE-364, CWE-763, CWE-787 +7

Technical details

References

Community reviews

Related threats