btrfs: handle lack of space when cleaning up verity items
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.
CVE-2026-98279
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2026-98279
Linux
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Linux
Source reference: /containers/cna/affected/1/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "146054090b0859b28fc39015c7704ccc3c3a347f",
"lessThan": "4b7ecabd87dc40998fe7870d7975279649229a3b",
"versionType": "git"
},
{
"status": "affected",
"version": "146054090b0859b28fc39015c7704ccc3c3a347f",
"lessThan": "efa5780b84f066f419a667f6b9542368b2f62074",
"versionType": "git"
},
{
"status": "affected",
"version": "146054090b0859b28fc39015c7704ccc3c3a347f",
"lessThan": "76bf149cd0298544631e756670b89c399c7acbca",
"versionType": "git"
}
],
"programFiles": [
"fs/btrfs/inode.c",
"fs/btrfs/verity.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "5.15"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "5.15",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "6.18.54",
"versionType": "semver",
"lessThanOrEqual": "6.18.*"
},
{
"status": "unaffected",
"version": "7.2.8",
"versionType": "semver",
"lessThanOrEqual": "7.2.*"
},
{
"status": "unaffected",
"version": "7.3",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"fs/btrfs/inode.c",
"fs/btrfs/verity.c"
],
"defaultStatus": "affected"
}
]- Related CVEs
- CVE-2026-98279
Source reference:
/cveMetadata/cveId
Publisher severity
No explicit severity was provided.
- Event
- #38357 · Revision 1
- Added to Heist Feed
- Publisher date