CVE-2022-49912 json
btrfs: fix ulist leaks in error paths of qgroup self tests
published 2025-05-01 18 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-12870
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 10%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix ulist leaks in error paths of qgroup self tests
In the test_no_shared_qgroup() and test_multiple_refs() qgroup self tests, if we fail to add the tree ref, remove the extent item or remove the extent ref, we are returning from the test function without freeing the "old_roots" ulist that was allocated by the previous calls to btrfs_find_all_roots(). Fix that by calling ulist_free() before returning.
Patch / fix
- Linux Linux 4.9.333, 4.14.299, 4.19.265, 5.4.224, 5.10.154, 5.15.78, 6.0.8, 6.1
- linux Debian 14, Debian 13, Debian 12 6.0.8-1
debian advisories DEBIAN-CVE-2022-49912
- linux Ubuntu 18.04 LTS 4.15.0-206.217
- linux Ubuntu 20.04 LTS 5.4.0-139.156
- linux Ubuntu 22.04 LTS 5.15.0-60.66
- linux-aws Ubuntu 18.04 LTS 4.15.0-1151.164
- linux-aws Ubuntu 20.04 LTS 5.4.0-1096.104
- linux-aws Ubuntu 22.04 LTS 5.15.0-1030.34
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1100.109
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1029.36
ubuntu advisories UBUNTU-CVE-2022-49912
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/d81370396025cf63a7a1b5f8bb25a3479203b2ca commit
- git.kernel.org/stable/c/3f58283d83a588ff5da62fc150de19e798ed2ec2 commit
- git.kernel.org/stable/c/203204798831c35d855ecc6417d98267d2d2184b commit
- git.kernel.org/stable/c/5d1a47ebf84540e40b5b43fc21aef0d6c0f627d9 commit
- git.kernel.org/stable/c/0a0dead4ad1a2e2a9bdf133ef45111d7c8daef84 commit
- git.kernel.org/stable/c/f46ea5fa3320dca4fe0c0926b49a5f14cb85de62 commit
- git.kernel.org/stable/c/da7003434bcab0ae9aba3f2c003e734cae093326 commit
- git.kernel.org/stable/c/d37de92b38932d40e4a251e876cc388f9aee5f42 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-49912 updated
kernel: btrfs: fix ulist leaks in error paths of qgroup self tests
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-401 Missing Release of Memory after Effective Lifetime
- Technology feeds
References
-
git.kernel.org
/stable/c/d81370396025cf63a7a1b5f8bb25a3479203b2ca
patch
-
git.kernel.org
/stable/c/3f58283d83a588ff5da62fc150de19e798ed2ec2
patch
-
git.kernel.org
/stable/c/203204798831c35d855ecc6417d98267d2d2184b
patch
-
git.kernel.org
/stable/c/5d1a47ebf84540e40b5b43fc21aef0d6c0f627d9
patch
-
git.kernel.org
/stable/c/0a0dead4ad1a2e2a9bdf133ef45111d7c8daef84
patch
-
git.kernel.org
/stable/c/f46ea5fa3320dca4fe0c0926b49a5f14cb85de62
patch
-
git.kernel.org
/stable/c/da7003434bcab0ae9aba3f2c003e734cae093326
patch
-
git.kernel.org
/stable/c/d37de92b38932d40e4a251e876cc388f9aee5f42
patch
Sources
- CVE List CVE-2022-49912
- NVD CVE-2022-49912
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.