# CVE-2026-97542: xfs: bail out on bitmap errors in xrep_agfl_fill

> A missing error check in the XFS filesystem repair code can lead to inconsistent data and potential system instability or denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **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:** AZL-104478, BELL-CVE-2026-97542, DEBIAN-CVE-2026-97542, GHSA-jp6c-38x7-hq3p, UBUNTU-CVE-2026-97542

## What is CVE-2026-97542?

CVE-2026-97542 is a denial of service 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: bail out on bitmap errors in xrep_agfl_fill

LOLLM also points out that the xagb_bitmap_set call in xrep_agfl_fill
can fail, but we don't check the result of xagb_bitmap_walk, so we
silently drop the error and proceed with inconsistent incore data.
That shouldn't be allowed.

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


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

Apply the vendor's patch.

## Is CVE-2026-97542 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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