# CVE-2026-97901: genetlink: pin family module during policy dump

> A use-after-free in the Linux kernel's generic netlink policy dump allows local attackers to execute arbitrary code or escalate privileges by unloading a module during a pending dump.

- **Severity:** Not scored
- **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 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-104715, BELL-CVE-2026-97901, DEBIAN-CVE-2026-97901, GHSA-5pgr-jp8q-29xm, UBUNTU-CVE-2026-97901

## What is CVE-2026-97901?

CVE-2026-97901 is an use after free vulnerability in Linux, published on 25 Sep 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:

genetlink: pin family module during policy dump

The generic netlink controller's policy dump keeps pointers to the target
family's operation and policy tables in its callback state.  A dump may be
split across multiple skbs and remain pending after the initial request.

Netlink pins the module which owns the dump callback, but in this case
that is the controller's owner rather than the target family's owner.  The
target family can consequently be unregistered and its module unloaded
while a policy dump is pending.  Advancing the dump then dereferences
policy memory from the unloaded module.

Take a reference to the target family's module when the dump starts.
Drop it from the error and done paths.  This matches the lifetime for which
the dump context retains the family and policy pointers.

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


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

Apply the vendor's patch.

## Is CVE-2026-97901 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97901 is an use after free vulnerability in Linux, published on 25 Sep 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-97901 in the wild and no public exploit code.

Affected product: Linux. 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-97901/ (Markdown: https://insights.sbomify.com/CVE-2026-97901/index.md)
```

## Sources

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

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