CVE-2026-23216VulnerabilityPublished 11 Jun 2026Updated 30 Oct 2026

Red Hat Security Advisory: kernel security update

Affects Linux kernelSource GCVE Database

Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-23216· High

Not known to be exploited · fixed in Red Hat package updates : patch Linux kernel soon.

Data as of 30 Oct 2026, 06:59 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in ba684191437380a07b27666eb4e72748be1ea201, 275016a551ba1a068a3bd6171b18611726b67110, 9411a89e9e7135cc459178fa77a3f1d6191ae903 +4

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Feb 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 ≥ e48354ce078c079996f89d715dfa44814b4eba01, < ba684191437380a07b27666eb4e72748be1ea201	Fixed in ba684191437380a07b27666eb4e72748be1ea201
LinuxLinux	Affected ≥ e48354ce078c079996f89d715dfa44814b4eba01, < 275016a551ba1a068a3bd6171b18611726b67110	Fixed in 275016a551ba1a068a3bd6171b18611726b67110
LinuxLinux	Affected ≥ e48354ce078c079996f89d715dfa44814b4eba01, < 9411a89e9e7135cc459178fa77a3f1d6191ae903	Fixed in 9411a89e9e7135cc459178fa77a3f1d6191ae903
LinuxLinux	Affected ≥ e48354ce078c079996f89d715dfa44814b4eba01, < 8518f072fc92921418cd9ed4268dd4f3e9a8fd75	Fixed in 8518f072fc92921418cd9ed4268dd4f3e9a8fd75
LinuxLinux	Affected ≥ e48354ce078c079996f89d715dfa44814b4eba01, < 3835e49e146a4e6e7787b29465f1a23379b6ec44	Fixed in 3835e49e146a4e6e7787b29465f1a23379b6ec44
LinuxLinux	Affected ≥ e48354ce078c079996f89d715dfa44814b4eba01, < 73b487d44bf4f92942629d578381f89c326ff77f	Fixed in 73b487d44bf4f92942629d578381f89c326ff77f

AI-suggested

Red Hat has released updated kernel packages for Red Hat Enterprise Linux 8 and 9 that address these vulnerabilities. Users should apply the provided security updates promptly following Red Hat's official guidance at https://access.redhat.com/articles/11258. A system reboot is required for the updates to take effect. No additional mitigation steps are indicated beyond applying the official patches.

Description

The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements. Security Fix(es): * kernel: scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() (CVE-2026-23216) * kernel: gfs2: Fix use-after-free in iomap inline data write path (CVE-2026-45984) * kernel: RDMA/vmw_pvrdma: Fix double free on pvrdma_alloc_ucontext() error path (CVE-2026-46189) Bug Fix(es) and Enhancement(s): * [RHEL 8.10.z] Add an .sbat section to the x86 kernel (JIRA:RHEL-182788) * Incorrect message "NFS: Server wrote zero bytes" is shown in the logs (JIRA:RHEL-147665) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Impact

The vulnerabilities addressed include use-after-free and double free bugs that can cause denial of service or potential memory corruption within the Linux kernel. These issues affect core kernel components such as SCSI target, bonding driver, networking subsystems, and RDMA drivers. Exploitation could lead to system instability or crashes. No known exploits in the wild have been reported at this time. The impact is rated as important by Red Hat Product Security.

Summary

This Red Hat security advisory addresses multiple vulnerabilities in the Linux kernel packages for Red Hat Enterprise Linux 8 and 9. Key fixes include resolving use-after-free vulnerabilities in the iscsi target (CVE-2026-23216), bonding driver (CVE-2026-31419), ALSA 6fire disconnect (CVE-2026-31581), and net mana add_adev error path (CVE-2026-43056). Other fixes cover double free issues in RDMA components (CVE-2026-45852, CVE-2026-46189), safe access to master conntrack (CVE-2026-43116), and validation of length in dlm_search_rsb_tree (CVE-2026-43125). These vulnerabilities could lead to denial of service or memory corruption. The advisory provides updated kernel packages for affected Red Hat Enterprise Linux versions and requires a reboot to apply the updates.

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-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-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-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).
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).
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-843Access of Resource Using Incompatible Type (Type Confusion) (opens in a new tab)
Base weakness
The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.
CWE-130Improper Handling of Length Parameter Inconsistency (opens in a new tab)
Base weakness
The product parses a formatted message or structure, but it does not handle or incorrectly handles a length field that is inconsistent with the actual length of the associated data.
Implementation
When processing structured incoming data containing a size field followed by raw data, ensure that you identify and resolve any inconsistencies between the size field and the actual size of the data.
Implementation
Do not let the user control the size of the buffer.
Implementation
Validate that the length of the user-supplied data is consistent with the buffer size.
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)
Attack patterns
Buffer Overflow via Parameter Expansion (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-131Incorrect Calculation of Buffer Size (opens in a new tab)
Base weaknessLikelihood of exploit: High
The product does not correctly calculate the size to be used when allocating a buffer.
Implementation
When allocating a buffer for the purpose of transforming, converting, or encoding an input, allocate enough memory to handle the largest possible encoding. For example, in a routine that converts "&" characters to "&" for HTML entity encoding, the output buffer needs to be at least 5 times as large as the input…
Implementation
Understand the programming language's underlying representation and how it interacts with numeric calculation (CWE-681). Pay close attention to byte size discrepancies, precision, signed/unsigned distinctions, truncation, conversion and casting between types, "not-a-number" calculations, and how the language handles…
Implementation · Input Validation
Perform input validation on any numeric input by ensuring that it is within the expected range. Enforce that the input meets both the minimum and maximum requirements for the expected range.
Attack patterns
Overflow Buffers (opens in a new tab)
Buffer Overflow via Parameter Expansion (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-366Race Condition within a Thread (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
If two threads of execution use a resource simultaneously, there exists the possibility that resources may be used while invalid, in turn making the state of execution undefined.
Architecture and Design
Use locking functionality. This is the recommended solution. Implement some form of locking mechanism around code which alters or reads persistent data in a multithreaded environment.
Architecture and Design
Create resource-locking validation checks. If no inherent locking mechanisms exist, use flags and signals to enforce your own blocking scheme when resources are being used by other threads 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)
Attack patterns
Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions (opens in a new tab)
Leveraging Race Conditions (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).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Aug 2026, 20:34 UTC

WeaknessesCWE-413, CWE-826, CWE-1341 +8

Technical details

References

Community reviews

Related threats