CVE-2022-49075

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix qgroup reserve overflow the qgroup limit We use extent_changeset->bytes_changed in qgroup_reserve_data() to record how many bytes we set for EXTENT_QGROUP_RESERVED state. Currently the bytes_changed is set as "unsigned int", and it will overflow if we try to fallocate a range larger than 4GiB. The result is we reserve less bytes and eventually break the qgroup limit. Unlike regular buffered/direct write, which we use one changeset for each ordered extent, which can never be larger than 256M. For fallocate, we use one changeset for the whole range, thus it no longer respects the 256M per extent limit, and caused the problem. The following example test script reproduces the problem: $ cat qgroup-overflow.sh #!/bin/bash DEV=/dev/sdj MNT=/mnt/sdj mkfs.btrfs -f $DEV mount $DEV $MNT # Set qgroup limit to 2GiB. btrfs quota enable $MNT btrfs qgroup limit 2G $MNT # Try to fallocate a 3GiB file. This should fail. echo echo "Try to fallocate a 3GiB file..." fallocate -l 3G $MNT/3G.file # Try to fallocate a 5GiB file. echo echo "Try to fallocate a 5GiB file..." fallocate -l 5G $MNT/5G.file # See we break the qgroup limit. echo sync btrfs qgroup show -r $MNT umount $MNT When running the test: $ ./qgroup-overflow.sh (...) Try to fallocate a 3GiB file... fallocate: fallocate failed: Disk quota exceeded Try to fallocate a 5GiB file... qgroupid         rfer         excl     max_rfer --------         ----         ----     -------- 0/5           5.00GiB      5.00GiB      2.00GiB Since we have no control of how bytes_changed is used, it's better to set it to u64.

• CWE-190

• https://git.kernel.org/stable/c/0355387ea5b02d353c9415613fab908fac5c52a6Patch
• https://git.kernel.org/stable/c/44277c50fdba5019ca25bfad1b71e2561b0de11bPatch
• https://git.kernel.org/stable/c/4b98799e181b4326a613108cf37acc1f55d21b45Patch
• https://git.kernel.org/stable/c/6bfff81286d4491f02dad7814bae5c77c9ad2320Patch
• https://git.kernel.org/stable/c/7941b74ed49b6db25efbef2256ebef843c11a010Patch
• https://git.kernel.org/stable/c/82ae73ac963cee877ce34f7c31b2b456b516e96cPatch
• https://git.kernel.org/stable/c/b642b52d0b50f4d398cb4293f64992d0eed2e2cePatch
• https://git.kernel.org/stable/c/f3d97b22a708bf9e3f3ac2ba232bcefd0b0c136bPatch

Published

Feb 26, 2025

Last Modified

Aug 4, 2026

Status

Modified

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2022-4907Uninitialized Use in FFmpeg in Google Chrome prior to 108.0.…8.8
• CVE-2022-49070In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2022-49071In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2022-49072In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2022-49073In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2022-49074In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2022-49076In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2022-49077In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2022-49078In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2022-49079In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2022-4908Inappropriate implementation in iFrame Sandbox in Google Chr…4.3
• CVE-2022-49080In the Linux kernel, the following vulnerability has been re…5.5