CVE-2022-49831 Details
Description
In the Linux kernel, the following vulnerability has been resolved: btrfs: zoned: initialize device's zone info for seeding When performing seeding on a zoned filesystem it is necessary to initialize each zoned device's btrfs_zoned_device_info structure, otherwise mounting the filesystem will cause a NULL pointer dereference. This was uncovered by fstests' testcase btrfs/163.
A vulnerability in the Linux kernel's Btrfs file system handling of zoned devices can lead to a NULL pointer dereference. This issue arises during the seeding process on a zoned filesystem, where the Btrfs zoned device information structure for each zoned device must be properly initialized. Failure to do so results in a NULL pointer dereference when the filesystem is mounted. This vulnerability was identified through the fstests Btrfs test case 163.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/544f38a738343d7e75f104e5e9d1ade58d8b71bd | kernel.org | Patch |
| https://git.kernel.org/stable/c/91c38504e589dadbcde47b1cacdfc5b684154d44 | kernel.org | Patch |
| https://git.kernel.org/stable/c/a8d1b1647bf8244a5f270538e9e636e2657fffa3 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-476 | NULL Pointer Dereference | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | < 5.15.79 >= 5.16, < 6.0.9 6.1 rc1 6.1 rc2 6.1 rc3 6.1 rc4 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 10, 2025 | Initial Analysis | [email protected] |
| May 1, 2025 | New CVE Received | kernel.org |