CVE-2026-23413
- Source
- https://cve.org/CVERecord?id=CVE-2026-23413
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-23413.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-23413
- Downstream
BELL (1)
DEBIAN (1)
openSUSE (1)
SUSE (10)
- Related
- Published
- 2026-04-02T11:40:54Z
- Modified
- 2026-10-08T02:50:39Z
- Severity
-
- 7.8 (High) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
- Summary
- clsact: Fix use-after-free in init/destroy rollback asymmetry
- Details
-
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.
- Database specific
{ "cna_assigner": "Linux", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23413.json" }- References
-
- https://git.kernel.org/stable/c/0509b762bc5e8ea7b8391130730c6d8502fc6e69
- https://git.kernel.org/stable/c/37bef86e5428d59f70a4da82b80f9a8f252fecbe
- https://git.kernel.org/stable/c/4c9af67f99aa3e51b522c54968ab3ac8272be41c
- https://git.kernel.org/stable/c/a0671125d4f55e1e98d9bde8a0b671941987e208
- https://git.kernel.org/stable/c/a73d95b57bf9faebdfed591bcb7ed9292062a84c
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23413.json
- https://nvd.nist.gov/vuln/detail/CVE-2026-23413
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced230bb13650b0f186f540500fd5f5f7096a822a2aFixeda73d95b57bf9faebdfed591bcb7ed9292062a84c
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced1cb6f0bae50441f4b4b32a28315853b279c7404eFixed37bef86e5428d59f70a4da82b80f9a8f252fecbeFixed4c9af67f99aa3e51b522c54968ab3ac8272be41cFixed0509b762bc5e8ea7b8391130730c6d8502fc6e69Fixeda0671125d4f55e1e98d9bde8a0b671941987e208
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced6.6.41Fixed6.6.130
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced6.9.10Fixed6.10
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducedf61ecf1bd5b562ebfd7d430ccb31619857e80857
Affected versions
v6.*
Linux / Kernel
Package
- Name
- Kernel