[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025050137-CVE-2022-49831-751b@gregkh>
Date: Thu, 1 May 2025 16:10:21 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-49831: btrfs: zoned: initialize device's zone info for seeding
From: Greg Kroah-Hartman <gregkh@...nel.org>
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.
The Linux kernel CVE team has assigned CVE-2022-49831 to this issue.
Affected and fixed versions
===========================
Fixed in 5.15.79 with commit 91c38504e589dadbcde47b1cacdfc5b684154d44
Fixed in 6.0.9 with commit 544f38a738343d7e75f104e5e9d1ade58d8b71bd
Fixed in 6.1 with commit a8d1b1647bf8244a5f270538e9e636e2657fffa3
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2022-49831
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
fs/btrfs/disk-io.c
fs/btrfs/volumes.c
fs/btrfs/volumes.h
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/91c38504e589dadbcde47b1cacdfc5b684154d44
https://git.kernel.org/stable/c/544f38a738343d7e75f104e5e9d1ade58d8b71bd
https://git.kernel.org/stable/c/a8d1b1647bf8244a5f270538e9e636e2657fffa3
Powered by blists - more mailing lists