btrfs: zoned: initialize device's zone info for seeding
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.15.79, 6.0.9
- CVEs
- CVE-2022-49831
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 8 Nov 2026, 01:55 UTC · Revision 1
Source evidence
btrfs: zoned: initialize device's zone info for seeding
core-osv · Original sourcePublished 1 May 2025, 14:09 UTC
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.
osv:CVE-2022-49831
Kernel
Fixed versions: 5.15.79, 6.0.9
Complete source record
{
"id": "1fc1d379a21a883d4727d67584454d3ce75355fc606ce321ffa90751cc1d61b0",
"url": "https://osv.dev/vulnerability/CVE-2022-49831",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "btrfs: zoned: initialize device's zone info for seeding",
"summary": "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.",
"evidence": "osv:CVE-2022-49831",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.15.79",
"evidence": "/affected/1/ranges"
},
{
"value": "6.0.9",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2022-49831",
"aliases": [
"CVE-2022-49831"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "7365104236ade0bf22edd7724c8fd438b0342ee4"
},
{
"fixed": "91c38504e589dadbcde47b1cacdfc5b684154d44"
},
{
"fixed": "544f38a738343d7e75f104e5e9d1ade58d8b71bd"
},
{
"fixed": "a8d1b1647bf8244a5f270538e9e636e2657fffa3"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49831.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.12.0"
},
{
"fixed": "5.15.79"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.0.9"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49831.json"
}
}
],
"modified": "2026-10-28T02:30:52.771596460Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/544f38a738343d7e75f104e5e9d1ade58d8b71bd",
"https://git.kernel.org/stable/c/91c38504e589dadbcde47b1cacdfc5b684154d44",
"https://git.kernel.org/stable/c/a8d1b1647bf8244a5f270538e9e636e2657fffa3",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49831.json",
"https://nvd.nist.gov/vuln/detail/CVE-2022-49831",
"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/2022/49xxx/CVE-2022-49831.json"
}
},
"related_cves": [
{
"value": "CVE-2022-49831",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 521542,
"published_at": "2025-05-01T14:09:49.617+00:00"
}