Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> hfs: fix general protection fault in hfs_find_init()<br /> <br /> The hfs_find_init() method can trigger the crash<br /> if tree pointer is NULL:<br /> <br /> [ 45.746290][ T9787] Oops: general protection fault, probably for non-canonical address 0xdffffc0000000008: 0000 [#1] SMP KAI<br /> [ 45.747287][ T9787] KASAN: null-ptr-deref in range [0x0000000000000040-0x0000000000000047]<br /> [ 45.748716][ T9787] CPU: 2 UID: 0 PID: 9787 Comm: repro Not tainted 6.16.0-rc3 #10 PREEMPT(full)<br /> [ 45.750250][ T9787] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014<br /> [ 45.751983][ T9787] RIP: 0010:hfs_find_init+0x86/0x230<br /> [ 45.752834][ T9787] Code: c1 ea 03 80 3c 02 00 0f 85 9a 01 00 00 4c 8d 6b 40 48 c7 45 18 00 00 00 00 48 b8 00 00 00 00 00 fc<br /> [ 45.755574][ T9787] RSP: 0018:ffffc90015157668 EFLAGS: 00010202<br /> [ 45.756432][ T9787] RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff819a4d09<br /> [ 45.757457][ T9787] RDX: 0000000000000008 RSI: ffffffff819acd3a RDI: ffffc900151576e8<br /> [ 45.758282][ T9787] RBP: ffffc900151576d0 R08: 0000000000000005 R09: 0000000000000000<br /> [ 45.758943][ T9787] R10: 0000000080000000 R11: 0000000000000001 R12: 0000000000000004<br /> [ 45.759619][ T9787] R13: 0000000000000040 R14: ffff88802c50814a R15: 0000000000000000<br /> [ 45.760293][ T9787] FS: 00007ffb72734540(0000) GS:ffff8880cec64000(0000) knlGS:0000000000000000<br /> [ 45.761050][ T9787] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> [ 45.761606][ T9787] CR2: 00007f9bd8225000 CR3: 000000010979a000 CR4: 00000000000006f0<br /> [ 45.762286][ T9787] Call Trace:<br /> [ 45.762570][ T9787] <br /> [ 45.762824][ T9787] hfs_ext_read_extent+0x190/0x9d0<br /> [ 45.763269][ T9787] ? submit_bio_noacct_nocheck+0x2dd/0xce0<br /> [ 45.763766][ T9787] ? __pfx_hfs_ext_read_extent+0x10/0x10<br /> [ 45.764250][ T9787] hfs_get_block+0x55f/0x830<br /> [ 45.764646][ T9787] block_read_full_folio+0x36d/0x850<br /> [ 45.765105][ T9787] ? __pfx_hfs_get_block+0x10/0x10<br /> [ 45.765541][ T9787] ? const_folio_flags+0x5b/0x100<br /> [ 45.765972][ T9787] ? __pfx_hfs_read_folio+0x10/0x10<br /> [ 45.766415][ T9787] filemap_read_folio+0xbe/0x290<br /> [ 45.766840][ T9787] ? __pfx_filemap_read_folio+0x10/0x10<br /> [ 45.767325][ T9787] ? __filemap_get_folio+0x32b/0xbf0<br /> [ 45.767780][ T9787] do_read_cache_folio+0x263/0x5c0<br /> [ 45.768223][ T9787] ? __pfx_hfs_read_folio+0x10/0x10<br /> [ 45.768666][ T9787] read_cache_page+0x5b/0x160<br /> [ 45.769070][ T9787] hfs_btree_open+0x491/0x1740<br /> [ 45.769481][ T9787] hfs_mdb_get+0x15e2/0x1fb0<br /> [ 45.769877][ T9787] ? __pfx_hfs_mdb_get+0x10/0x10<br /> [ 45.770316][ T9787] ? find_held_lock+0x2b/0x80<br /> [ 45.770731][ T9787] ? lockdep_init_map_type+0x5c/0x280<br /> [ 45.771200][ T9787] ? lockdep_init_map_type+0x5c/0x280<br /> [ 45.771674][ T9787] hfs_fill_super+0x38e/0x720<br /> [ 45.772092][ T9787] ? __pfx_hfs_fill_super+0x10/0x10<br /> [ 45.772549][ T9787] ? snprintf+0xbe/0x100<br /> [ 45.772931][ T9787] ? __pfx_snprintf+0x10/0x10<br /> [ 45.773350][ T9787] ? do_raw_spin_lock+0x129/0x2b0<br /> [ 45.773796][ T9787] ? find_held_lock+0x2b/0x80<br /> [ 45.774215][ T9787] ? set_blocksize+0x40a/0x510<br /> [ 45.774636][ T9787] ? sb_set_blocksize+0x176/0x1d0<br /> [ 45.775087][ T9787] ? setup_bdev_super+0x369/0x730<br /> [ 45.775533][ T9787] get_tree_bdev_flags+0x384/0x620<br /> [ 45.775985][ T9787] ? __pfx_hfs_fill_super+0x10/0x10<br /> [ 45.776453][ T9787] ? __pfx_get_tree_bdev_flags+0x10/0x10<br /> [ 45.776950][ T9787] ? bpf_lsm_capable+0x9/0x10<br /> [ 45.777365][ T9787] ? security_capable+0x80/0x260<br /> [ 45.777803][ T9787] vfs_get_tree+0x8e/0x340<br /> [ 45.778203][ T9787] path_mount+0x13de/0x2010<br /> [ 45.778604][ T9787] ? kmem_cache_free+0x2b0/0x4c0<br /> [ 45.779052][ T9787] ? __pfx_path_mount+0x10/0x10<br /> [ 45.779480][ T9787] ? getname_flags.part.0+0x1c5/0x550<br /> [ 45.779954][ T9787] ? putname+0x154/0x1a0<br /> [ 45.780335][ T9787] __x64_sys_mount+0x27b/0x300<br /> [ 45.780758][ T9787] ? __pfx___x64_sys_mount+0x10/0x10<br /> [ 45.781232][ T9787] <br /> ---truncated---

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: kcm: Fix race condition in kcm_unattach()<br /> <br /> syzbot found a race condition when kcm_unattach(psock)<br /> and kcm_release(kcm) are executed at the same time.<br /> <br /> kcm_unattach() is missing a check of the flag<br /> kcm-&gt;tx_stopped before calling queue_work().<br /> <br /> If the kcm has a reserved psock, kcm_unattach() might get executed<br /> between cancel_work_sync() and unreserve_psock() in kcm_release(),<br /> requeuing kcm-&gt;tx_work right before kcm gets freed in kcm_done().<br /> <br /> Remove kcm-&gt;tx_stopped and replace it by the less<br /> error-prone disable_work_sync().

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: hibmcge: fix the division by zero issue<br /> <br /> When the network port is down, the queue is released, and ring-&gt;len is 0.<br /> In debugfs, hbg_get_queue_used_num() will be called,<br /> which may lead to a division by zero issue.<br /> <br /> This patch adds a check, if ring-&gt;len is 0,<br /> hbg_get_queue_used_num() directly returns 0.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> sctp: linearize cloned gso packets in sctp_rcv<br /> <br /> A cloned head skb still shares these frag skbs in fraglist with the<br /> original head skb. It&amp;#39;s not safe to access these frag skbs.<br /> <br /> syzbot reported two use-of-uninitialized-memory bugs caused by this:<br /> <br /> BUG: KMSAN: uninit-value in sctp_inq_pop+0x15b7/0x1920 net/sctp/inqueue.c:211<br /> sctp_inq_pop+0x15b7/0x1920 net/sctp/inqueue.c:211<br /> sctp_assoc_bh_rcv+0x1a7/0xc50 net/sctp/associola.c:998<br /> sctp_inq_push+0x2ef/0x380 net/sctp/inqueue.c:88<br /> sctp_backlog_rcv+0x397/0xdb0 net/sctp/input.c:331<br /> sk_backlog_rcv+0x13b/0x420 include/net/sock.h:1122<br /> __release_sock+0x1da/0x330 net/core/sock.c:3106<br /> release_sock+0x6b/0x250 net/core/sock.c:3660<br /> sctp_wait_for_connect+0x487/0x820 net/sctp/socket.c:9360<br /> sctp_sendmsg_to_asoc+0x1ec1/0x1f00 net/sctp/socket.c:1885<br /> sctp_sendmsg+0x32b9/0x4a80 net/sctp/socket.c:2031<br /> inet_sendmsg+0x25a/0x280 net/ipv4/af_inet.c:851<br /> sock_sendmsg_nosec net/socket.c:718 [inline]<br /> <br /> and<br /> <br /> BUG: KMSAN: uninit-value in sctp_assoc_bh_rcv+0x34e/0xbc0 net/sctp/associola.c:987<br /> sctp_assoc_bh_rcv+0x34e/0xbc0 net/sctp/associola.c:987<br /> sctp_inq_push+0x2a3/0x350 net/sctp/inqueue.c:88<br /> sctp_backlog_rcv+0x3c7/0xda0 net/sctp/input.c:331<br /> sk_backlog_rcv+0x142/0x420 include/net/sock.h:1148<br /> __release_sock+0x1d3/0x330 net/core/sock.c:3213<br /> release_sock+0x6b/0x270 net/core/sock.c:3767<br /> sctp_wait_for_connect+0x458/0x820 net/sctp/socket.c:9367<br /> sctp_sendmsg_to_asoc+0x223a/0x2260 net/sctp/socket.c:1886<br /> sctp_sendmsg+0x3910/0x49f0 net/sctp/socket.c:2032<br /> inet_sendmsg+0x269/0x2a0 net/ipv4/af_inet.c:851<br /> sock_sendmsg_nosec net/socket.c:712 [inline]<br /> <br /> This patch fixes it by linearizing cloned gso packets in sctp_rcv().

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> hfsplus: fix slab-out-of-bounds in hfsplus_bnode_read()<br /> <br /> The hfsplus_bnode_read() method can trigger the issue:<br /> <br /> [ 174.852007][ T9784] ==================================================================<br /> [ 174.852709][ T9784] BUG: KASAN: slab-out-of-bounds in hfsplus_bnode_read+0x2f4/0x360<br /> [ 174.853412][ T9784] Read of size 8 at addr ffff88810b5fc6c0 by task repro/9784<br /> [ 174.854059][ T9784]<br /> [ 174.854272][ T9784] CPU: 1 UID: 0 PID: 9784 Comm: repro Not tainted 6.16.0-rc3 #7 PREEMPT(full)<br /> [ 174.854281][ T9784] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014<br /> [ 174.854286][ T9784] Call Trace:<br /> [ 174.854289][ T9784] <br /> [ 174.854292][ T9784] dump_stack_lvl+0x10e/0x1f0<br /> [ 174.854305][ T9784] print_report+0xd0/0x660<br /> [ 174.854315][ T9784] ? __virt_addr_valid+0x81/0x610<br /> [ 174.854323][ T9784] ? __phys_addr+0xe8/0x180<br /> [ 174.854330][ T9784] ? hfsplus_bnode_read+0x2f4/0x360<br /> [ 174.854337][ T9784] kasan_report+0xc6/0x100<br /> [ 174.854346][ T9784] ? hfsplus_bnode_read+0x2f4/0x360<br /> [ 174.854354][ T9784] hfsplus_bnode_read+0x2f4/0x360<br /> [ 174.854362][ T9784] hfsplus_bnode_dump+0x2ec/0x380<br /> [ 174.854370][ T9784] ? __pfx_hfsplus_bnode_dump+0x10/0x10<br /> [ 174.854377][ T9784] ? hfsplus_bnode_write_u16+0x83/0xb0<br /> [ 174.854385][ T9784] ? srcu_gp_start+0xd0/0x310<br /> [ 174.854393][ T9784] ? __mark_inode_dirty+0x29e/0xe40<br /> [ 174.854402][ T9784] hfsplus_brec_remove+0x3d2/0x4e0<br /> [ 174.854411][ T9784] __hfsplus_delete_attr+0x290/0x3a0<br /> [ 174.854419][ T9784] ? __pfx_hfs_find_1st_rec_by_cnid+0x10/0x10<br /> [ 174.854427][ T9784] ? __pfx___hfsplus_delete_attr+0x10/0x10<br /> [ 174.854436][ T9784] ? __asan_memset+0x23/0x50<br /> [ 174.854450][ T9784] hfsplus_delete_all_attrs+0x262/0x320<br /> [ 174.854459][ T9784] ? __pfx_hfsplus_delete_all_attrs+0x10/0x10<br /> [ 174.854469][ T9784] ? rcu_is_watching+0x12/0xc0<br /> [ 174.854476][ T9784] ? __mark_inode_dirty+0x29e/0xe40<br /> [ 174.854483][ T9784] hfsplus_delete_cat+0x845/0xde0<br /> [ 174.854493][ T9784] ? __pfx_hfsplus_delete_cat+0x10/0x10<br /> [ 174.854507][ T9784] hfsplus_unlink+0x1ca/0x7c0<br /> [ 174.854516][ T9784] ? __pfx_hfsplus_unlink+0x10/0x10<br /> [ 174.854525][ T9784] ? down_write+0x148/0x200<br /> [ 174.854532][ T9784] ? __pfx_down_write+0x10/0x10<br /> [ 174.854540][ T9784] vfs_unlink+0x2fe/0x9b0<br /> [ 174.854549][ T9784] do_unlinkat+0x490/0x670<br /> [ 174.854557][ T9784] ? __pfx_do_unlinkat+0x10/0x10<br /> [ 174.854565][ T9784] ? __might_fault+0xbc/0x130<br /> [ 174.854576][ T9784] ? getname_flags.part.0+0x1c5/0x550<br /> [ 174.854584][ T9784] __x64_sys_unlink+0xc5/0x110<br /> [ 174.854592][ T9784] do_syscall_64+0xc9/0x480<br /> [ 174.854600][ T9784] entry_SYSCALL_64_after_hwframe+0x77/0x7f<br /> [ 174.854608][ T9784] RIP: 0033:0x7f6fdf4c3167<br /> [ 174.854614][ T9784] Code: f0 ff ff 73 01 c3 48 8b 0d 26 0d 0e 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 08<br /> [ 174.854622][ T9784] RSP: 002b:00007ffcb948bca8 EFLAGS: 00000206 ORIG_RAX: 0000000000000057<br /> [ 174.854630][ T9784] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f6fdf4c3167<br /> [ 174.854636][ T9784] RDX: 00007ffcb948bcc0 RSI: 00007ffcb948bcc0 RDI: 00007ffcb948bd50<br /> [ 174.854641][ T9784] RBP: 00007ffcb948cd90 R08: 0000000000000001 R09: 00007ffcb948bb40<br /> [ 174.854645][ T9784] R10: 00007f6fdf564fc0 R11: 0000000000000206 R12: 0000561e1bc9c2d0<br /> [ 174.854650][ T9784] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000<br /> [ 174.854658][ T9784] <br /> [ 174.854661][ T9784]<br /> [ 174.879281][ T9784] Allocated by task 9784:<br /> [ 174.879664][ T9784] kasan_save_stack+0x20/0x40<br /> [ 174.880082][ T9784] kasan_save_track+0x14/0x30<br /> [ 174.880500][ T9784] __kasan_kmalloc+0xaa/0xb0<br /> [ 174.880908][ T9784] __kmalloc_noprof+0x205/0x550<br /> [ 174.881337][ T9784] __hfs_bnode_create+0x107/0x890<br /> [ 174.881779][ T9784] hfsplus_bnode_find+0x2d0/0xd10<br /> [ 174.882222][ T9784] hfsplus_brec_find+0x2b0/0x520<br /> [ 174.882659][ T9784] hfsplus_delete_all_attrs+0x23b/0x3<br /> ---truncated---

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> smb/server: avoid deadlock when linking with ReplaceIfExists<br /> <br /> If smb2_create_link() is called with ReplaceIfExists set and the name<br /> does exist then a deadlock will happen.<br /> <br /> ksmbd_vfs_kern_path_locked() will return with success and the parent<br /> directory will be locked. ksmbd_vfs_remove_file() will then remove the<br /> file. ksmbd_vfs_link() will then be called while the parent is still<br /> locked. It will try to lock the same parent and will deadlock.<br /> <br /> This patch moves the ksmbd_vfs_kern_path_unlock() call to *before*<br /> ksmbd_vfs_link() and then simplifies the code, removing the file_present<br /> flag variable.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> hfsplus: don&amp;#39;t use BUG_ON() in hfsplus_create_attributes_file()<br /> <br /> When the volume header contains erroneous values that do not reflect<br /> the actual state of the filesystem, hfsplus_fill_super() assumes that<br /> the attributes file is not yet created, which later results in hitting<br /> BUG_ON() when hfsplus_create_attributes_file() is called. Replace this<br /> BUG_ON() with -EIO error with a message to suggest running fsck tool.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc()<br /> <br /> The hfsplus_readdir() method is capable to crash by calling<br /> hfsplus_uni2asc():<br /> <br /> [ 667.121659][ T9805] ==================================================================<br /> [ 667.122651][ T9805] BUG: KASAN: slab-out-of-bounds in hfsplus_uni2asc+0x902/0xa10<br /> [ 667.123627][ T9805] Read of size 2 at addr ffff88802592f40c by task repro/9805<br /> [ 667.124578][ T9805]<br /> [ 667.124876][ T9805] CPU: 3 UID: 0 PID: 9805 Comm: repro Not tainted 6.16.0-rc3 #1 PREEMPT(full)<br /> [ 667.124886][ T9805] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014<br /> [ 667.124890][ T9805] Call Trace:<br /> [ 667.124893][ T9805] <br /> [ 667.124896][ T9805] dump_stack_lvl+0x10e/0x1f0<br /> [ 667.124911][ T9805] print_report+0xd0/0x660<br /> [ 667.124920][ T9805] ? __virt_addr_valid+0x81/0x610<br /> [ 667.124928][ T9805] ? __phys_addr+0xe8/0x180<br /> [ 667.124934][ T9805] ? hfsplus_uni2asc+0x902/0xa10<br /> [ 667.124942][ T9805] kasan_report+0xc6/0x100<br /> [ 667.124950][ T9805] ? hfsplus_uni2asc+0x902/0xa10<br /> [ 667.124959][ T9805] hfsplus_uni2asc+0x902/0xa10<br /> [ 667.124966][ T9805] ? hfsplus_bnode_read+0x14b/0x360<br /> [ 667.124974][ T9805] hfsplus_readdir+0x845/0xfc0<br /> [ 667.124984][ T9805] ? __pfx_hfsplus_readdir+0x10/0x10<br /> [ 667.124994][ T9805] ? stack_trace_save+0x8e/0xc0<br /> [ 667.125008][ T9805] ? iterate_dir+0x18b/0xb20<br /> [ 667.125015][ T9805] ? trace_lock_acquire+0x85/0xd0<br /> [ 667.125022][ T9805] ? lock_acquire+0x30/0x80<br /> [ 667.125029][ T9805] ? iterate_dir+0x18b/0xb20<br /> [ 667.125037][ T9805] ? down_read_killable+0x1ed/0x4c0<br /> [ 667.125044][ T9805] ? putname+0x154/0x1a0<br /> [ 667.125051][ T9805] ? __pfx_down_read_killable+0x10/0x10<br /> [ 667.125058][ T9805] ? apparmor_file_permission+0x239/0x3e0<br /> [ 667.125069][ T9805] iterate_dir+0x296/0xb20<br /> [ 667.125076][ T9805] __x64_sys_getdents64+0x13c/0x2c0<br /> [ 667.125084][ T9805] ? __pfx___x64_sys_getdents64+0x10/0x10<br /> [ 667.125091][ T9805] ? __x64_sys_openat+0x141/0x200<br /> [ 667.125126][ T9805] ? __pfx_filldir64+0x10/0x10<br /> [ 667.125134][ T9805] ? do_user_addr_fault+0x7fe/0x12f0<br /> [ 667.125143][ T9805] do_syscall_64+0xc9/0x480<br /> [ 667.125151][ T9805] entry_SYSCALL_64_after_hwframe+0x77/0x7f<br /> [ 667.125158][ T9805] RIP: 0033:0x7fa8753b2fc9<br /> [ 667.125164][ T9805] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 48<br /> [ 667.125172][ T9805] RSP: 002b:00007ffe96f8e0f8 EFLAGS: 00000217 ORIG_RAX: 00000000000000d9<br /> [ 667.125181][ T9805] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fa8753b2fc9<br /> [ 667.125185][ T9805] RDX: 0000000000000400 RSI: 00002000000063c0 RDI: 0000000000000004<br /> [ 667.125190][ T9805] RBP: 00007ffe96f8e110 R08: 00007ffe96f8e110 R09: 00007ffe96f8e110<br /> [ 667.125195][ T9805] R10: 0000000000000000 R11: 0000000000000217 R12: 0000556b1e3b4260<br /> [ 667.125199][ T9805] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000<br /> [ 667.125207][ T9805] <br /> [ 667.125210][ T9805]<br /> [ 667.145632][ T9805] Allocated by task 9805:<br /> [ 667.145991][ T9805] kasan_save_stack+0x20/0x40<br /> [ 667.146352][ T9805] kasan_save_track+0x14/0x30<br /> [ 667.146717][ T9805] __kasan_kmalloc+0xaa/0xb0<br /> [ 667.147065][ T9805] __kmalloc_noprof+0x205/0x550<br /> [ 667.147448][ T9805] hfsplus_find_init+0x95/0x1f0<br /> [ 667.147813][ T9805] hfsplus_readdir+0x220/0xfc0<br /> [ 667.148174][ T9805] iterate_dir+0x296/0xb20<br /> [ 667.148549][ T9805] __x64_sys_getdents64+0x13c/0x2c0<br /> [ 667.148937][ T9805] do_syscall_64+0xc9/0x480<br /> [ 667.149291][ T9805] entry_SYSCALL_64_after_hwframe+0x77/0x7f<br /> [ 667.149809][ T9805]<br /> [ 667.150030][ T9805] The buggy address belongs to the object at ffff88802592f000<br /> [ 667.150030][ T9805] which belongs to the cache kmalloc-2k of size 2048<br /> [ 667.151282][ T9805] The buggy address is located 0 bytes to the right of<br /> [ 667.151282][ T9805] allocated 1036-byte region [ffff88802592f000, ffff88802592f40c)<br /> [ 667.1<br /> ---truncated---

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> hfs: fix slab-out-of-bounds in hfs_bnode_read()<br /> <br /> This patch introduces is_bnode_offset_valid() method that checks<br /> the requested offset value. Also, it introduces<br /> check_and_correct_requested_length() method that checks and<br /> correct the requested length (if it is necessary). These methods<br /> are used in hfs_bnode_read(), hfs_bnode_write(), hfs_bnode_clear(),<br /> hfs_bnode_copy(), and hfs_bnode_move() with the goal to prevent<br /> the access out of allocated memory and triggering the crash.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> gfs2: Validate i_depth for exhash directories<br /> <br /> A fuzzer test introduced corruption that ends up with a depth of 0 in<br /> dir_e_read(), causing an undefined shift by 32 at:<br /> <br /> index = hash &gt;&gt; (32 - dip-&gt;i_depth);<br /> <br /> As calculated in an open-coded way in dir_make_exhash(), the minimum<br /> depth for an exhash directory is ilog2(sdp-&gt;sd_hash_ptrs) and 0 is<br /> invalid as sdp-&gt;sd_hash_ptrs is fixed as sdp-&gt;bsize / 16 at mount time.<br /> <br /> So we can avoid the undefined behaviour by checking for depth values<br /> lower than the minimum in gfs2_dinode_in(). Values greater than the<br /> maximum are already being checked for there.<br /> <br /> Also switch the calculation in dir_make_exhash() to use ilog2() to<br /> clarify how the depth is calculated.<br /> <br /> Tested with the syzkaller repro.c and xfstests &amp;#39;-g quick&amp;#39;.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> fs/ntfs3: Add sanity check for file name<br /> <br /> The length of the file name should be smaller than the directory entry size.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ASoC: core: Check for rtd == NULL in snd_soc_remove_pcm_runtime()<br /> <br /> snd_soc_remove_pcm_runtime() might be called with rtd == NULL which will<br /> leads to null pointer dereference.<br /> This was reproduced with topology loading and marking a link as ignore<br /> due to missing hardware component on the system.<br /> On module removal the soc_tplg_remove_link() would call<br /> snd_soc_remove_pcm_runtime() with rtd == NULL since the link was ignored,<br /> no runtime was created.