ALT-PU-2025-1861-2
Package kernel-image-un-def updated to version 6.1.127-alt1 for branch p10 in task 371045.
Closed vulnerabilities
Modified: 2025-02-11
CVE-2024-57887
In the Linux kernel, the following vulnerability has been resolved: drm: adv7511: Fix use-after-free in adv7533_attach_dsi() The host_node pointer was assigned and freed in adv7533_parse_dt(), and later, adv7533_attach_dsi() uses the same. Fix this use-after-free issue by dropping of_node_put() in adv7533_parse_dt() and calling of_node_put() in error path of probe() and also in the remove().
- https://git.kernel.org/stable/c/1f49aaf55652580ae63ab83d67211fe6a55d83dc
- https://git.kernel.org/stable/c/81adbd3ff21c1182e06aa02c6be0bfd9ea02d8e8
- https://git.kernel.org/stable/c/acec80d9f126cd3fa764bbe3d96bc0cb5cd2b087
- https://git.kernel.org/stable/c/ca9d077350fa21897de8bf64cba23b198740aab5
- https://git.kernel.org/stable/c/d208571943ffddc438a7ce533d5d0b9219806242
Modified: 2025-02-13
CVE-2024-57892
In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix slab-use-after-free due to dangling pointer dqi_priv When mounting ocfs2 and then remounting it as read-only, a slab-use-after-free occurs after the user uses a syscall to quota_getnextquota. Specifically, sb_dqinfo(sb, type)->dqi_priv is the dangling pointer. During the remounting process, the pointer dqi_priv is freed but is never set as null leaving it to be accessed. Additionally, the read-only option for remounting sets the DQUOT_SUSPENDED flag instead of setting the DQUOT_USAGE_ENABLED flags. Moreover, later in the process of getting the next quota, the function ocfs2_get_next_id is called and only checks the quota usage flags and not the quota suspended flags. To fix this, I set dqi_priv to null when it is freed after remounting with read-only and put a check for DQUOT_SUSPENDED in ocfs2_get_next_id. [akpm@linux-foundation.org: coding-style cleanups]
- https://git.kernel.org/stable/c/2d431192486367eee03cc28d0b53b97dafcb8e63
- https://git.kernel.org/stable/c/2e3d203b1adede46bbba049e497765d67865be18
- https://git.kernel.org/stable/c/58f9e20e2a7602e1dd649a1ec4790077c251cb6c
- https://git.kernel.org/stable/c/5f3fd772d152229d94602bca243fbb658068a597
- https://git.kernel.org/stable/c/8ff6f635a08c30559ded0c110c7ce03ba7747d11
- https://git.kernel.org/stable/c/ba950a02d8d23811aa1120affd3adedcfac6153d
- https://git.kernel.org/stable/c/f44e6d70c100614c211703f065cad448050e4a0e
Modified: 2025-02-02
CVE-2024-57940
In the Linux kernel, the following vulnerability has been resolved: exfat: fix the infinite loop in exfat_readdir() If the file system is corrupted so that a cluster is linked to itself in the cluster chain, and there is an unused directory entry in the cluster, 'dentry' will not be incremented, causing condition 'dentry < max_dentries' unable to prevent an infinite loop. This infinite loop causes s_lock not to be released, and other tasks will hang, such as exfat_sync_fs(). This commit stops traversing the cluster chain when there is unused directory entry in the cluster to avoid this infinite loop.
- https://git.kernel.org/stable/c/28c21f0ac5293a4bf19b3e0e32005d6dd31a6c17
- https://git.kernel.org/stable/c/31beabd0f47f8c3ed9965ba861c9e5b252d4920a
- https://git.kernel.org/stable/c/d8cfbb8723bd3d3222f360227a1cc15227189ca6
- https://git.kernel.org/stable/c/d9ea94f5cd117d56e573696d0045ab3044185a15
- https://git.kernel.org/stable/c/dc1d7afceb982e8f666e70a582e6b5aa806de063
- https://git.kernel.org/stable/c/fee873761bd978d077d8c55334b4966ac4cb7b59