mbox series

[SRU,Mantic,Jammy,0/1] CVE-2024-23850

Message ID 20240228222410.43705-1-bethany.jamison@canonical.com
Headers show
Series CVE-2024-23850 | expand

Message

Bethany Jamison Feb. 28, 2024, 10:24 p.m. UTC 
[Impact]

In btrfs_get_root_ref in fs/btrfs/disk-io.c in the Linux kernel through
6.7.1, there can be an assertion failure and crash because a subvolume can
be read out too soon after its root item is inserted upon subvolume
creation.

[Fix]

Mantic: Clean cherry-pick.
Jammy: Mantic patch applied cleanly.

[Test Case]

Compile and boot tested.

[Where problems could occur]

This affects those who use a kernel 6.7.1 and older and make subvolumes
for btrfs.

Qu Wenruo (1):
  btrfs: do not ASSERT() if the newly created subvolume already got read

 fs/btrfs/disk-io.c | 13 +++++++++++--
 1 file changed, 11 insertions(+), 2 deletions(-)

Comments

Andrei Gherzan Feb. 29, 2024, 1:38 p.m. UTC | #1 
On 24/02/28 04:24PM, Bethany Jamison wrote:
> [Impact]
> 
> In btrfs_get_root_ref in fs/btrfs/disk-io.c in the Linux kernel through
> 6.7.1, there can be an assertion failure and crash because a subvolume can
> be read out too soon after its root item is inserted upon subvolume
> creation.
> 
> [Fix]
> 
> Mantic: Clean cherry-pick.
> Jammy: Mantic patch applied cleanly.
> 
> [Test Case]
> 
> Compile and boot tested.
> 
> [Where problems could occur]
> 
> This affects those who use a kernel 6.7.1 and older and make subvolumes
> for btrfs.
> 
> Qu Wenruo (1):
>   btrfs: do not ASSERT() if the newly created subvolume already got read
> 
>  fs/btrfs/disk-io.c | 13 +++++++++++--
>  1 file changed, 11 insertions(+), 2 deletions(-)

Acked-by: Andrei Gherzan <andrei.gherzan@canonical.com>
Tim Gardner Feb. 29, 2024, 2:04 p.m. UTC | #2 
On 2/28/24 3:24 PM, Bethany Jamison wrote:
> [Impact]
> 
> In btrfs_get_root_ref in fs/btrfs/disk-io.c in the Linux kernel through
> 6.7.1, there can be an assertion failure and crash because a subvolume can
> be read out too soon after its root item is inserted upon subvolume
> creation.
> 
> [Fix]
> 
> Mantic: Clean cherry-pick.
> Jammy: Mantic patch applied cleanly.
> 
> [Test Case]
> 
> Compile and boot tested.
> 
> [Where problems could occur]
> 
> This affects those who use a kernel 6.7.1 and older and make subvolumes
> for btrfs.
> 
> Qu Wenruo (1):
>    btrfs: do not ASSERT() if the newly created subvolume already got read
> 
>   fs/btrfs/disk-io.c | 13 +++++++++++--
>   1 file changed, 11 insertions(+), 2 deletions(-)
> 
Acked-by: Tim Gardner <tim.gardner@canonical.com>
Stefan Bader March 1, 2024, 9 a.m. UTC | #3 
On 28.02.24 23:24, Bethany Jamison wrote:
> [Impact]
> 
> In btrfs_get_root_ref in fs/btrfs/disk-io.c in the Linux kernel through
> 6.7.1, there can be an assertion failure and crash because a subvolume can
> be read out too soon after its root item is inserted upon subvolume
> creation.
> 
> [Fix]
> 
> Mantic: Clean cherry-pick.
> Jammy: Mantic patch applied cleanly.
> 
> [Test Case]
> 
> Compile and boot tested.
> 
> [Where problems could occur]
> 
> This affects those who use a kernel 6.7.1 and older and make subvolumes
> for btrfs.
> 
> Qu Wenruo (1):
>    btrfs: do not ASSERT() if the newly created subvolume already got read
> 
>   fs/btrfs/disk-io.c | 13 +++++++++++--
>   1 file changed, 11 insertions(+), 2 deletions(-)
> 

Applied to mantic,jammy:linux/master-next. Thanks.

-Stefan