# CVE-2026-97585: afs: Fix double-unmap of directory block

> A double-unmap vulnerability in the Linux kernel AFS filesystem allows local attackers to cause denial of service or potentially execute code.

- **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:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-97585, DEBIAN-CVE-2026-97585, GHSA-cgwc-p322-356w, UBUNTU-CVE-2026-97585

## What is CVE-2026-97585?

CVE-2026-97585 is a memory corruption 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:

afs: Fix double-unmap of directory block

Fix afs_edit_dir_remove() to use a cleanup function to unmap the block
pointed to by afs_dir_iter::block if it's left pointing to something rather
than manually kunmapping the blocks.  Manually kunmapping without clearing
iter.blocks can result in a double-kunmap if afs_dir_find_block() is called
twice in a row (which would be the case if the block being modified is not
first in the hash chain).

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


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

Apply the vendor's patch.

## Is CVE-2026-97585 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97585 is a memory corruption 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-97585 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-97585/ (Markdown: https://insights.sbomify.com/CVE-2026-97585/index.md)
```

## Sources

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

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