# CVE-2026-31422: net/sched: cls_flow: fix NULL pointer dereference on shared blocks

> A NULL pointer dereference in the Linux kernel's cls_flow scheduler allows local attackers to cause a denial of service via crafted network filters.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Apr 2026
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-82703, BELL-CVE-2026-31422, DEBIAN-CVE-2026-31422, GHSA-6pmm-j8mh-qwgf, ROOT-OS-DEBIAN-11-CVE-2026-31422, ROOT-OS-DEBIAN-12-CVE-2026-31422, ROOT-OS-DEBIAN-13-CVE-2026-31422, ROOT-OS-UBUNTU-2204-CVE-2026-31422, ROOT-OS-UBUNTU-2404-CVE-2026-31422, UBUNTU-CVE-2026-31422

## What is CVE-2026-31422?

CVE-2026-31422 is a medium-severity vulnerability in Linux kernel, published on 13 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

net/sched: cls_flow: fix NULL pointer dereference on shared blocks

flow_change() calls tcf_block_q() and dereferences q->handle to derive
a default baseclass.  Shared blocks leave block->q NULL, causing a NULL
deref when a flow filter without a fully qualified baseclass is created
on a shared block.

Check tcf_block_shared() before accessing block->q and return -EINVAL
for shared blocks.  This avoids the null-deref shown below:

=======================================================================
KASAN: null-ptr-deref in range [0x0000000000000038-0x000000000000003f]
RIP: 0010:flow_change (net/sched/cls_flow.c:508)
Call Trace:
 tc_new_tfilter (net/sched/cls_api.c:2432)
 rtnetlink_rcv_msg (net/core/rtnetlink.c:6980)
 [...]
=======================================================================

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2026-31422?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-31422?

Apply the vendor's patch.

## Is CVE-2026-31422 being exploited?

There is no known exploitation of CVE-2026-31422 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-31422 and fix it if it is affected.

What it is: CVE-2026-31422 is a medium-severity vulnerability in Linux kernel, published on 13 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-31422 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-31422/ (Markdown: https://insights.sbomify.com/CVE-2026-31422/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-31422
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-31422
- OSV: https://osv.dev/vulnerability/CVE-2026-31422

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-31422/
Summaries are generated and may contain mistakes; the official description above is the record.