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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.18.54, 7.2.8
- CVEs
- CVE-2026-98279
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 10:27 UTC · Revision 1
Source evidence
btrfs: handle lack of space when cleaning up verity items
core-osv · Original sourcePublished 6 Oct 2026, 08:45 UTC
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.
osv:CVE-2026-98279
Kernel
Fixed versions: 6.18.54, 7.2.8
Complete source record
{
"id": "f3bb0a0670382d733be8513189603c0adfabd49697faf93d5d7dc5862f2013ef",
"url": "https://osv.dev/vulnerability/CVE-2026-98279",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "btrfs: handle lack of space when cleaning up verity items",
"summary": "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.",
"evidence": "osv:CVE-2026-98279",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.18.54",
"evidence": "/affected/1/ranges"
},
{
"value": "7.2.8",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-98279",
"aliases": [
"CVE-2026-98279"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "146054090b0859b28fc39015c7704ccc3c3a347f"
},
{
"fixed": "4b7ecabd87dc40998fe7870d7975279649229a3b"
},
{
"fixed": "efa5780b84f066f419a667f6b9542368b2f62074"
},
{
"fixed": "76bf149cd0298544631e756670b89c399c7acbca"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98279.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.15.0"
},
{
"fixed": "6.18.54"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.2.8"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98279.json"
}
}
],
"modified": "2026-10-28T02:30:27.953767435Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/4b7ecabd87dc40998fe7870d7975279649229a3b",
"https://git.kernel.org/stable/c/76bf149cd0298544631e756670b89c399c7acbca",
"https://git.kernel.org/stable/c/efa5780b84f066f419a667f6b9542368b2f62074",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98279.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-98279",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98279.json"
}
},
"related_cves": [
{
"value": "CVE-2026-98279",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 494537,
"published_at": "2026-10-06T08:45:39.114+00:00"
}