# CVE-2026-23392: netfilter: nf_tables: release flowtable after rcu grace period on error

> A use-after-free vulnerability in the Linux kernel netfilter subsystem allows attackers to potentially execute code or cause a denial of service via specific error paths.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 25 Mar 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-80585, BELL-CVE-2026-23392, DEBIAN-CVE-2026-23392, GHSA-f5vj-m443-mgw6, ROOT-OS-DEBIAN-11-CVE-2026-23392, ROOT-OS-DEBIAN-12-CVE-2026-23392, ROOT-OS-DEBIAN-13-CVE-2026-23392, ROOT-OS-UBUNTU-2204-CVE-2026-23392, ROOT-OS-UBUNTU-2404-CVE-2026-23392, UBUNTU-CVE-2026-23392

## What is CVE-2026-23392?

CVE-2026-23392 is a high-severity use after free vulnerability in Linux kernel, published on 25 Mar 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:

netfilter: nf_tables: release flowtable after rcu grace period on error

Call synchronize_rcu() after unregistering the hooks from error path,
since a hook that already refers to this flowtable can be already
registered, exposing this flowtable to packet path and nfnetlink_hook
control plane.

This error path is rare, it should only happen by reaching the maximum
number hooks or by failing to set up to hardware offload, just call
synchronize_rcu().

There is a check for already used device hooks by different flowtable
that could result in EEXIST at this late stage. The hook parser can be
updated to perform this check earlier to this error path really becomes
rarely exercised.

Uncovered by KASAN reported as use-after-free from nfnetlink_hook path
when dumping hooks.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2026-23392 being exploited?

There is no known exploitation of CVE-2026-23392 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-23392 and fix it if it is affected.

What it is: CVE-2026-23392 is a high-severity use after free vulnerability in Linux kernel, published on 25 Mar 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-23392 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-23392/ (Markdown: https://insights.sbomify.com/CVE-2026-23392/index.md)
```

## Sources

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

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