Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-46733: btrfs: fix qgroup reserve leaks in cow_file_range

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 159f0f61b283ea71e827dd0c18c5dce197de1fa2, 30479f31d44d47ed00ae0c7453d9b253537005b2, 84464db2ec2a55b9313d5f264da196a37ec80994.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 159f0f61b283ea71e827dd0c18c5dce197de1fa2, 30479f31d44d47ed00ae0c7453d9b253537005b2, 84464db2ec2a55b9313d5f264da196a37ec80994 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix qgroup reserve leaks in cow_file_range In the buffered write path, the dirty page owns the qgroup reserve until it creates an ordered_extent. Therefore, any errors that occur before the ordered_extent is created must free that reservation, or else the space is leaked. The fstest generic/475 exercises various IO error paths, and is able to trigger errors in cow_file_range where we fail to get to allocating the ordered extent. Note that because we *do* clear delalloc, we are likely to remove the inode from the delalloc list, so the inodes/pages to not have invalidate/launder called on them in the commit abort path. This results in failures at the unmount stage of the test that look like: BTRFS: error (device dm-8 state EA) in cleanup_transaction:2018: errno=-5 IO failure BTRFS: error (device dm-8 state EA) in btrfs_replace_file_extents:2416: errno=-5 IO failure BTRFS warning (device dm-8 state EA): qgroup 0/5 has unreleased space, type 0 rsv 28672 ------------[ cut here ]------------ WARNING: CPU: 3 PID: 22588 at fs/btrfs/disk-io.c:4333 close_ctree+0x222/0x4d0 [btrfs] Modules linked in: btrfs blake2b_generic libcrc32c xor zstd_compress raid6_pq CPU: 3 PID: 22588 Comm: umount Kdump: loaded Tainted: G W 6.10.0-rc7-gab56fde445b8 #21 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.16.3-1-1 04/01/2014 RIP: 0010:close_ctree+0x222/0x4d0 [btrfs] RSP: 0018:ffffb4465283be00 EFLAGS: 00010202 RAX: 0000000000000001 RBX: ffffa1a1818e1000 RCX: 0000000000000001 RDX: 0000000000000000 RSI: ffffb4465283bbe0 RDI: ffffa1a19374fcb8 RBP: ffffa1a1818e13c0 R08: 0000000100028b16 R09: 0000000000000000 R10: 0000000000000003 R11: 0000000000000003 R12: ffffa1a18ad7972c R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 FS: 00007f9168312b80(0000) GS:ffffa1a4afcc0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f91683c9140 CR3: 000000010acaa000 CR4: 00000000000006f0 Call Trace: <TASK> ? close_ctree+0x222/0x4d0 [btrfs] ? __warn.cold+0x8e/0xea ? close_ctree+0x222/0x4d0 [btrfs] ? report_bug+0xff/0x140 ? handle_bug+0x3b/0x70 ? exc_invalid_op+0x17/0x70 ? asm_exc_invalid_op+0x1a/0x20 ? close_ctree+0x222/0x4d0 [btrfs] generic_shutdown_super+0x70/0x160 kill_anon_super+0x11/0x40 btrfs_kill_super+0x11/0x20 [btrfs] deactivate_locked_super+0x2e/0xa0 cleanup_mnt+0xb5/0x150 task_work_run+0x57/0x80 syscall_exit_to_user_mode+0x121/0x130 do_syscall_64+0xab/0x1a0 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f916847a887 ---[ end trace 0000000000000000 ]--- BTRFS error (device dm-8 state EA): qgroup reserved space leaked Cases 2 and 3 in the out_reserve path both pertain to this type of leak and must free the reserved qgroup data. Because it is already an error path, I opted not to handle the possible errors in btrfs_free_qgroup_data.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Sep 18, 2024
Updated
Jun 17, 2026
EPSS
0.1% · 6th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-46733

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernelbefore 6.1.135
  • linux linux kernel6.2 and later · before 6.6.88
  • linux linux kernel6.7 and later · before 6.10.9
  • linux linux kernel6.11

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.9affected
    • 7dbeaad0af7d0a1a2a8e41d04e90964368ddfcc5 and later · before 159f0f61b283ea71e827dd0c18c5dce197de1fa2affected · git
    • 7dbeaad0af7d0a1a2a8e41d04e90964368ddfcc5 and later · before 84464db2ec2a55b9313d5f264da196a37ec80994affected · git
    • 7dbeaad0af7d0a1a2a8e41d04e90964368ddfcc5 and later · before e42ef22bc10f0309c0c65d8d6ca8b4127a674b7faffected · git
    • 7dbeaad0af7d0a1a2a8e41d04e90964368ddfcc5 and later · before 30479f31d44d47ed00ae0c7453d9b253537005b2affected · git
    • before 5.9not affected · semver
    • 6.1.135 and later · up to and including 6.1.*not affected · semver
    • 6.6.88 and later · up to and including 6.6.*not affected · semver
    • 6.10.9 and later · up to and including 6.10.*not affected · semver
    • 6.11 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:11linux-6.1before 6.1.137-1~deb11u16.1.137-1~deb11u1
Debian:12linuxbefore 6.1.135-16.1.135-1
Debian:13linuxbefore 6.10.9-16.10.9-1
openSUSE:Leap 15.6dtb-aarch64before 6.4.0-150600.23.70.16.4.0-150600.23.70.1
openSUSE:Leap 15.6kernel-64kbbefore 6.4.0-150600.23.70.16.4.0-150600.23.70.1
openSUSE:Leap 15.6kernel-debugbefore 6.4.0-150600.23.70.16.4.0-150600.23.70.1
openSUSE:Leap 15.6kernel-defaultbefore 6.4.0-150600.23.70.16.4.0-150600.23.70.1
openSUSE:Leap 15.6kernel-default-basebefore 6.4.0-150600.23.70.1.150600.12.30.26.4.0-150600.23.70.1.150600.12.30.2
openSUSE:Leap 15.6kernel-docsbefore 6.4.0-150600.23.70.16.4.0-150600.23.70.1
openSUSE:Leap 15.6kernel-kvmsmallbefore 6.4.0-150600.23.70.16.4.0-150600.23.70.1
openSUSE:Leap 15.6kernel-obs-buildbefore 6.4.0-150600.23.70.16.4.0-150600.23.70.1
openSUSE:Leap 15.6kernel-obs-qabefore 6.4.0-150600.23.70.16.4.0-150600.23.70.1
openSUSE:Leap 15.6kernel-rtbefore 6.4.0-150600.10.52.16.4.0-150600.10.52.1
openSUSE:Leap 15.6kernel-rt_debugbefore 6.4.0-150600.10.52.16.4.0-150600.10.52.1
openSUSE:Leap 15.6kernel-sourcebefore 6.4.0-150600.23.70.16.4.0-150600.23.70.1
openSUSE:Leap 15.6kernel-source-rtbefore 6.4.0-150600.10.52.16.4.0-150600.10.52.1
openSUSE:Leap 15.6kernel-symsbefore 6.4.0-150600.23.70.16.4.0-150600.23.70.1
openSUSE:Leap 15.6kernel-syms-rtbefore 6.4.0-150600.10.52.16.4.0-150600.10.52.1
openSUSE:Leap 15.6kernel-zfcpdumpbefore 6.4.0-150600.23.70.16.4.0-150600.23.70.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_15before 1-150600.13.3.21-150600.13.3.2
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6-RT_Update_15before 1-150600.1.3.11-150600.1.3.1
SUSE:Linux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_4before 1-150700.15.3.21-150700.15.3.2
SUSE:Linux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7-RT_Update_4before 1-150700.1.3.21-150700.1.3.2
SUSE:Linux Enterprise Module for Basesystem 15 SP6kernel-64kbbefore 6.4.0-150600.23.70.16.4.0-150600.23.70.1

+35

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-46731Sep 18, 2024 · drm/amd/pm: fix the Out-of-bounds read warning
    28Monitor
  • ← EarlierCVE-2024-46732Sep 18, 2024 · drm/amd/display: Assign linear_pitch_alignment even for VM
    22Monitor
  • Later →CVE-2024-46734Sep 18, 2024 · btrfs: fix race between direct IO write and fsync when using same fd
    18Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux159f0f61b283ea71e827dd0c18c5dce197de1fa2Vendor (CNA)
Linux Linux30479f31d44d47ed00ae0c7453d9b253537005b2Vendor (CNA)
Linux Linux84464db2ec2a55b9313d5f264da196a37ec80994Vendor (CNA)
Linux Linuxe42ef22bc10f0309c0c65d8d6ca8b4127a674b7fVendor (CNA)
debian:linux6.1.135-1 · Debian:12Package registry (OSV)
debian:linux-6.16.1.137-1~deb11u1 · Debian:11Package registry (OSV)
opensuse:dtb-aarch646.4.0-150600.23.70.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-64kb6.4.0-150600.23.70.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-debug6.4.0-150600.23.70.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default6.4.0-150600.23.70.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default-base6.4.0-150600.23.70.1.150600.12.30.2 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-docs6.4.0-150600.23.70.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-kvmsmall6.4.0-150600.23.70.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-obs-build6.4.0-150600.23.70.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-rt6.4.0-150600.10.52.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-rt_debug6.4.0-150600.10.52.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-source-rt6.4.0-150600.10.52.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-syms-rt6.4.0-150600.10.52.1 · openSUSE:Leap 15.6Package registry (OSV)
suse:kernel-64kb6.4.0-150600.23.70.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-64kb6.4.0-150700.53.16.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)
suse:kernel-default6.4.0-150600.23.70.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-default6.4.0-150700.53.16.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)
suse:kernel-default-base6.4.0-150600.23.70.1.150600.12.30.2 · SUSE:Linux Enterprise Module for Basesystem 15 SP6Package registry (OSV)
suse:kernel-default-base6.4.0-150700.53.16.1.150700.17.11.2 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)
suse:kernel-docs6.4.0-150700.53.16.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6-RT_Update_151-150600.1.3.1 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-obs-build6.4.0-150700.53.16.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7Package registry (OSV)
suse:kernel-rt6.4.0-150600.10.52.1 · SUSE:Real Time Module 15 SP6Package registry (OSV)
suse:kernel-rt_debug6.4.0-150600.10.52.1 · SUSE:Real Time Module 15 SP6Package registry (OSV)
suse:kernel-source6.4.0-150700.53.16.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP7Package registry (OSV)

+3

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records