# CVE-2026-74427: afs: Fix netns teardown to cancel the preallocation charger

> A race condition in Linux kernel AFS network namespace teardown can cause a denial of service by failing to cancel preallocation work items.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** BELL-CVE-2026-74427, DEBIAN-CVE-2026-74427, GHSA-2hj8-22xr-w775, UBUNTU-CVE-2026-74427

## What is CVE-2026-74427?

CVE-2026-74427 is a critical vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

afs: Fix netns teardown to cancel the preallocation charger

Fix the teardown of an afs network namespace to make sure it cancels the
work item that keeps the preallocated rxrpc call/conn/peer queue charged
before incoming calls are disabled (i.e. listen 0).

Also, if net->live is false because the afs netns is being deleted, make
afs_charge_preallocation() skip charging and make afs_rx_new_call() avoid
requeuing the charger.

(This was found by AI review).

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


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

Apply the vendor's patch.

## Is CVE-2026-74427 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74427 is a critical vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-74427 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-74427/ (Markdown: https://insights.sbomify.com/CVE-2026-74427/index.md)
```

## Sources

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

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