CLSA-2024-1731431756 kernel: Fix of 30 CVEs

tty: ngsm: Fix use-after-free in gsmcleanupmux CVE-2024-50073 - drm/amdkfd: amdkfdfreegttmem clear the correct pointer CVE-2024-49991 - ext4: fix timer use-after-free on failed mount CVE-2024-49960 - ext4: avoid use-after-free in ext4extshowleaf CVE-2024-49889 - ext4: fix slab-use-after-free in...

kernel: ext4: correct grp validation in ext4_mb_good_group

A NULL pointer dereference vulnerability was found in the ext4 filesystem in the Linux kernel. In ext4mbgoodgroup, the group corruption check accesses the grp structure memory before verifying that grp is not NULL. If grp is NULL, this leads to a kernel crash. The fix adds a NULL check before...

ext4: fix slab-use-after-free in ext4_split_extent_at()

...

ext4: aovid use-after-free in ext4_ext_insert_extent()

...

CVE-2024-50191

In the Linux kernel, the following vulnerability has been resolved: ext4: don't set SBRDONLY after filesystem errors When the filesystem is mounted with errors=remount-ro, we were setting SBRDONLY flag to stop all filesystem modifications. We knew this misses proper locking sb-sumount and does no...

UBUNTU-CVE-2024-50191

In the Linux kernel, the following vulnerability has been resolved: ext4: don't set SBRDONLY after filesystem errors When the filesystem is mounted with errors=remount-ro, we were setting SBRDONLY flag to stop all filesystem modifications. We knew this misses proper locking sb-sumount and does no...

CVE-2024-50191

In the Linux kernel, the following vulnerability has been resolved: ext4: don't set SBRDONLY after filesystem errors When the filesystem is mounted with errors=remount-ro, we were setting SBRDONLY flag to stop all filesystem modifications. We knew this misses proper locking sb-sumount and does no...

kernel: ext4: fix uninitialized ratelimit_state->lock access in __ext4_fill_super()

A vulnerability was found in the Linux kernel's ext4 filesystem within the ext4fillsuper function, where uninitialized access to ratelimitstate-lock can occur, where the sysfs interface is registered before properly initializing rs-lock, potentially allowing other processes to modify rs-interval ...

kernel: ext4: fix uninitialized ratelimit_state->lock access in __ext4_fill_super()

A vulnerability was found in the Linux kernel's ext4 filesystem within the ext4fillsuper function, where uninitialized access to ratelimitstate-lock can occur, where the sysfs interface is registered before properly initializing rs-lock, potentially allowing other processes to modify rs-interval ...

kernel: ext4: fix uninitialized ratelimit_state->lock access in __ext4_fill_super()

A vulnerability was found in the Linux kernel's ext4 filesystem within the ext4fillsuper function, where uninitialized access to ratelimitstate-lock can occur, where the sysfs interface is registered before properly initializing rs-lock, potentially allowing other processes to modify rs-interval ...

SUSE CVE-2024-49968

In the Linux kernel, the following vulnerability has been resolved: ext4: filesystems without casefold feature cannot be mounted with siphash When mounting the ext4 filesystem, if the default hash version is set to DXHASHSIPHASH but the casefold feature is not set, exit the mounting...

SUSE CVE-2024-49880

In the Linux kernel, the following vulnerability has been resolved: ext4: fix off by one issue in allocflexgd Wesley reported an issue: ================================================================== EXT4-fs dm-5: resizing filesystem from 7168 to 786432 blocks ------------ cut here -----------...

SUSE CVE-2024-49884

In the Linux kernel, the following vulnerability has been resolved: ext4: fix slab-use-after-free in ext4splitextentat We hit the following use-after-free: ================================================================== BUG: KASAN: slab-use-after-free in ext4splitextentat+0xba8/0xcc0 Read of...

CVE-2024-49968

In the Linux kernel, the following vulnerability has been resolved: ext4: filesystems without casefold feature cannot be mounted with siphash When mounting the ext4 filesystem, if the default hash version is set to DXHASHSIPHASH but the casefold feature is not set, exit the mounting...

CVE-2024-49880

In the Linux kernel, the following vulnerability has been resolved: ext4: fix off by one issue in allocflexgd Wesley reported an issue: ================================================================== EXT4-fs dm-5: resizing filesystem from 7168 to 786432 blocks ------------ cut here -----------...

CVE-2024-49968

In the Linux kernel, the following vulnerability has been resolved: ext4: filesystems without casefold feature cannot be mounted with siphash When mounting the ext4 filesystem, if the default hash version is set to DXHASHSIPHASH but the casefold feature is not set, exit the mounting...

AZL-52344 CVE-2024-49968 affecting package kernel for versions less than 6.6.121.1-1

In the Linux kernel, the following vulnerability has been resolved: ext4: filesystems without casefold feature cannot be mounted with siphash When mounting the ext4 filesystem, if the default hash version is set to DXHASHSIPHASH but the casefold feature is not set, exit the mounting...

CVE-2024-49968

CVE-2024-49968 (from Miracle Linux AXSA advisory) concerns Linux kernel ext4. The vulnerability occurs when mounting an ext4 filesystem that does not have the casefold feature while the default hash version is DX_HASH_SIPHASH; in this scenario the mount operation exits, effectively preventing mou...

CVE-2024-49968 ext4: filesystems without casefold feature cannot be mounted with siphash

In the Linux kernel, the following vulnerability has been resolved: ext4: filesystems without casefold feature cannot be mounted with siphash When mounting the ext4 filesystem, if the default hash version is set to DXHASHSIPHASH but the casefold feature is not set, exit the mounting...

CVE-2024-49960

CVE-2024-49960 concerns ext4 on the Linux kernel. The issue is a timer use-after-free during failed mounts: the s_err_report timer can remain active while sbi is freed, because ext4_handle_error re-arms the timer before kfree(sbi). The root cause is not canceling the s_err_report timer after ext4...