跳转到帖子

Red Hat: CVE-2024-26704: kernel: ext4: fix double-free of blocks due to wrong extents moved_len (Multiple Advisories)

recommended_posts

发布于
  • Members

Red Hat: CVE-2024-26704: kernel: ext4: fix double-free of blocks due to wrong extents moved_len (Multiple Advisories)

Severity
5
CVSS
(AV:L/AC:L/Au:S/C:N/I:N/A:C)
Published
04/03/2024
Created
07/26/2024
Added
07/25/2024
Modified
02/10/2025

Description

In the Linux kernel, the following vulnerability has been resolved: ext4: fix double-free of blocks due to wrong extents moved_len In ext4_move_extents(), moved_len is only updated when all moves are successfully executed, and only discards orig_inode and donor_inode preallocations when moved_len is not zero. When the loop fails to exit after successfully moving some extents, moved_len is not updated and remains at 0, so it does not discard the preallocations. If the moved extents overlap with the preallocated extents, the overlapped extents are freed twice in ext4_mb_release_inode_pa() and ext4_process_freed_data() (as described in commit 94d7c16cbbbd ("ext4: Fix double-free of blocks with EXT4_IOC_MOVE_EXT")), and bb_free is incremented twice. Hence when trim is executed, a zero-division bug is triggered in mb_update_avg_fragment_size() because bb_free is not zero and bb_fragments is zero. Therefore, update move_len after each extent move to avoid the issue.

Solution(s)

  • redhat-upgrade-kernel
  • redhat-upgrade-kernel-rt

References

  • CVE-2024-26704
  • RHSA-2024:10771
  • RHSA-2024:4823
  • RHSA-2024:4831
  • RHSA-2024:5101
  • RHSA-2024:5102
  • RHSA-2024:5255
  • RHSA-2024:9315
View more
  • 查看数 703
  • 已创建
  • 最后回复

参与讨论

你可立刻发布并稍后注册。 如果你有帐户,立刻登录发布帖子。
注意:你的帖子需要版主批准后才能看到。

游客
回帖…