CVE-2026-23413 Details
Description
In the Linux kernel, the following vulnerability has been resolved: clsact: Fix use-after-free in init/destroy rollback asymmetry Fix a use-after-free in the clsact qdisc upon init/destroy rollback asymmetry. The latter is achieved by first fully initializing a clsact instance, and then in a second step having a replacement failure for the new clsact qdisc instance. clsact_init() initializes ingress first and then takes care of the egress part. This can fail midway, for example, via tcf_block_get_ext(). Upon failure, the kernel will trigger the clsact_destroy() callback. Commit 1cb6f0bae504 ("bpf: Fix too early release of tcx_entry") details the way how the transition is happening. If tcf_block_get_ext on the q->ingress_block ends up failing, we took the tcx_miniq_inc reference count on the ingress side, but not yet on the egress side. clsact_destroy() tests whether the {ingress,egress}_entry was non-NULL. However, even in midway failure on the replacement, both are in fact non-NULL with a valid egress_entry from the previous clsact instance. What we really need to test for is whether the qdisc instance-specific ingress or egress side previously got initialized. This adds a small helper for checking the miniq initialization called mini_qdisc_pair_inited, and utilizes that upon clsact_destroy() in order to fix the use-after-free scenario. Convert the ingress_destroy() side as well so both are consistent to each other.
A use-after-free vulnerability has been identified in the Linux kernel's clsact queuing discipline (qdisc) management. This issue arises from an asymmetry in the initialization and destruction process of clsact instances. The problem occurs when the clsact_init function successfully initializes the ingress side but fails to complete the egress initialization, leaving the egress entry from a previous instance valid. When the clsact_destroy function is called, it incorrectly assumes both entries are uninitialized, leading to a use-after-free condition. The vulnerability has been addressed by adding a helper function to check the initialization status of the qdisc entries before destruction, ensuring a consistent and safe cleanup process.
Users can upgrade to the latest version of the Linux kernel where this vulnerability has been fixed. Instructions for upgrading the kernel can be found in the official Linux kernel documentation.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Oct 16, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/0509b762bc5e8ea7b8391130730c6d8502fc6e69 | kernel.org | Patch |
| https://git.kernel.org/stable/c/37bef86e5428d59f70a4da82b80f9a8f252fecbe | kernel.org | Patch |
| https://git.kernel.org/stable/c/4c9af67f99aa3e51b522c54968ab3ac8272be41c | kernel.org | Patch |
| https://git.kernel.org/stable/c/a0671125d4f55e1e98d9bde8a0b671941987e208 | kernel.org | Patch |
| https://git.kernel.org/stable/c/a73d95b57bf9faebdfed591bcb7ed9292062a84c | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-416 | Use After Free | [email protected] |
| CWE-416 | Use After Free | CISA-ADP |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.6.41, < 6.6.130 >= 6.9.10, < 6.10 >= 6.10.1, < 6.12.78 >= 6.13, < 6.18.20 >= 6.19, < 6.19.10 6.10 - 7.0 rc1 7.0 rc2 7.0 rc3 7.0 rc4 7.0 rc5 7.0 rc6 7.0 rc7 |
CPE
Remediation
| |
Change History
7 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 19, 2026 | CVE Modified | CISA-ADP |
| Oct 16, 2026 | CVE Modified | kernel.org |
| Oct 16, 2026 | CVE Modified | CISA-ADP |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Apr 27, 2026 | CVE Modified | kernel.org |
| Apr 24, 2026 | Initial Analysis | [email protected] |
| Apr 2, 2026 | New CVE Received | kernel.org |