# CVE-2026-97545: xfs: don't leak new_bp if xfs_btree_bload_drop_buf fails

> A local attacker can cause a denial of service by triggering a buffer leak in the XFS filesystem when an IO error occurs during btree block loading.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **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-97545, DEBIAN-CVE-2026-97545, GHSA-3937-hvp2-9q25, UBUNTU-CVE-2026-97545

## What is CVE-2026-97545?

CVE-2026-97545 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:

xfs: don't leak new_bp if xfs_btree_bload_drop_buf fails

LOLLM observes that in xfs_btree_bload_prep_block,
xfs_btree_bload_drop_buf can hit an IO error if writing the delwri
buffer list to disk fails.  In this case, we fail to release new_bp,
which means we lose a locked buffer.  Fix that.

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


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

Apply the vendor's patch.

## Is CVE-2026-97545 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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