Skip to content
Fencer Intel
high 7.8

CVE-2026-23413 json

clsact: Fix use-after-free in init/destroy rollback asymmetry

published 7mo ago modified 21d ago also EUVD-2026-18192

cvss
7.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 5%
public exploits
0
none known

Summary

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.

Patch / fix

  • Linux Linux 6.6.130, 6.10, 6.12.78, 6.18.20, 6.19.10, 7.0
  • linux Debian 13 6.12.85-1
  • linux Debian 14 6.19.10-1

debian advisories DEBIAN-CVE-2026-23413

  • linux Ubuntu 24.04 LTS 6.8.0-136.136
  • linux-aws Ubuntu 24.04 LTS 6.8.0-1061.64
  • linux-gcp Ubuntu 24.04 LTS 6.8.0-1064.72
  • linux-gke Ubuntu 24.04 LTS 6.8.0-1059.67
  • linux-ibm Ubuntu 24.04 LTS 6.8.0-1061.62
  • linux-azure Ubuntu 24.04 LTS 6.8.0-1063.71
  • linux-gkeop Ubuntu 24.04 LTS 6.8.0-1046.50
  • linux-raspi Ubuntu 24.04 LTS 6.8.0-1061.65

ubuntu advisories UBUNTU-CVE-2026-23413

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-rt Real Time Module 15 SP7 6.4.0-150700.7.37.2
  • kernel-syms-rt Real Time Module 15 SP7 6.4.0-150700.7.37.1
  • kernel-source-rt Real Time Module 15 SP7 6.4.0-150700.7.37.2
  • kernel-rt Linux Micro 6.2 6.12.0-160000.28.1
  • kernel-64kb Linux Micro 6.2 6.12.0-160000.28.1
  • kernel-source Linux Micro 6.2 6.12.0-160000.28.1
  • kernel-default Linux Micro 6.2 6.12.0-160000.28.1
  • kernel-default-base Linux Micro 6.2 6.12.0-160000.27.1.160000.2.8

suse advisories SUSE-SU-2026:1573-1SUSE-SU-2026:21237-1SUSE-SU-2026:21230-1SUSE-SU-2026:21255-1SUSE-SU-2026:21123-1SUSE-SU-2026:21114-1

  • kernel-rt openSUSE Leap 16.0 6.12.0-160000.28.1
  • dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.28.1
  • kernel-64kb openSUSE Leap 16.0 6.12.0-160000.28.1
  • kernel-syms openSUSE Leap 16.0 6.12.0-160000.28.1
  • kernel-azure openSUSE Leap 16.0 6.12.0-160000.28.1
  • kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.28.1
  • kernel-source openSUSE Leap 16.0 6.12.0-160000.28.1
  • kernel-default openSUSE Leap 16.0 6.12.0-160000.28.1

opensuse advisories openSUSE-SU-2026:20572-1

Is CVE-2026-23413 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-23413 updated cvss 5.5

kernel: clsact: Fix use-after-free in init/destroy rollback asymmetry

  • Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +82 more Red Hat Enterprise Linux 10 kernel
    affected: no fix available “Fix deferred”
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 kernel-rt, kernel-rt-selftests-internal
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
24d ago

Exploit prediction

0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Linux Linux

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.