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.
Published: 2026-10-06
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Denial of Service (Filesystem Read‑Only state)
Action: Immediate Patch
AI Analysis

Impact

In the Linux kernel, enabling btrfs verity can trigger a rollback when the qgroup limit or lack of space is reached. The rollback operation was incorrectly implemented, failing to reserve the needed metadata space. This flaw represents a resource exhaustion weakness and a failure to properly release critical resources (CWE-459). As a result, the rollback fails, rendering the entire filesystem read‑only and preventing orphan cleanups from succeeding on the next mount. The consequence is a denial of service where the filesystem cannot be mounted read‑write, and any subsequent attempt to mount read‑write will fail, leaving subvolumes unreachable or the entire system in a read‑only state.

Affected Systems

The flaw resides in the kernel code that powers btrfs on Linux. All Linux distributions that ship a kernel version containing this code are affected, regardless of distribution metadata, until the patch that adds the global reserve calls for orphan cleanup, verity removal, and rollback is applied.

Risk and Exploitability

The EPSS score of < 1% indicates a very low probability of exploitation, and the vulnerability is not listed in the CISA KEV catalog. The CVSS score of 5.5 indicates a moderate severity. The impact is a local denial of service that can arise when an attacker with root or equivalent privileges triggers a qgroup limit or a full‑filesystem condition during a verity operation. The attack requires kernel‑level interaction and is not exploitable over the network, but it presents a real threat whenever privileged access is available.

Generated by OpenCVE AI on October 11, 2026 at 05:30 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that includes the btrfs fix that adds global reservation handling for orphan cleanup, verity removal, and rollback.
  • If an immediate kernel upgrade is not possible, avoid reaching the qgroup limit or full‑filesystem state by ensuring sufficient free space before enabling verity and by adjusting qgroup limits if needed.
  • If the filesystem becomes read‑only, remount it as read‑only, manually run orphan cleanup with global reservation, and then remount read‑write after freeing enough space.

Generated by OpenCVE AI on October 11, 2026 at 05:30 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 11 Oct 2026 04:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-399

Sun, 11 Oct 2026 00:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-459
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate


Tue, 06 Oct 2026 16:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-399

Tue, 06 Oct 2026 09:00:00 +0000

Type Values Removed Values Added
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.
Title btrfs: handle lack of space when cleaning up verity items
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-19T09:16:50.852Z

Reserved: 2026-09-25T10:25:14.334Z

Link: CVE-2026-98279

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-06T09:18:17.783

Modified: 2026-10-19T10:18:29.343

Link: CVE-2026-98279

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-10-06T00:00:00Z

Links: CVE-2026-98279 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-11T05:45:16Z

Weaknesses