Vulnerabilidades

*** Pendiente de traducción *** Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> scsi: ses: Fix slab-out-of-bounds in ses_enclosure_data_process()<br /> <br /> A fix for:<br /> <br /> BUG: KASAN: slab-out-of-bounds in ses_enclosure_data_process+0x949/0xe30 [ses]<br /> Read of size 1 at addr ffff88a1b043a451 by task systemd-udevd/3271<br /> <br /> Checking after (and before in next loop) addl_desc_ptr[1] is sufficient, we<br /> expect the size to be sanitized before first access to addl_desc_ptr[1].<br /> Make sure we don&amp;#39;t walk beyond end of page.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> nilfs2: fix use-after-free bug of nilfs_root in nilfs_evict_inode()<br /> <br /> During unmount process of nilfs2, nothing holds nilfs_root structure after<br /> nilfs2 detaches its writer in nilfs_detach_log_writer(). However, since<br /> nilfs_evict_inode() uses nilfs_root for some cleanup operations, it may<br /> cause use-after-free read if inodes are left in "garbage_list" and<br /> released by nilfs_dispose_list() at the end of nilfs_detach_log_writer().<br /> <br /> Fix this issue by modifying nilfs_evict_inode() to only clear inode<br /> without additional metadata changes that use nilfs_root if the file system<br /> is degraded to read-only or the writer is detached.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/amd/display: populate subvp cmd info only for the top pipe<br /> <br /> [Why]<br /> System restart observed while changing the display resolution<br /> to 8k with extended mode. Sytem restart was caused by a page fault.<br /> <br /> [How]<br /> When the driver populates subvp info it did it for both the pipes using<br /> vblank which caused an outof bounds array access causing the page fault.<br /> added checks to allow the top pipe only to fix this issue.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> clk: clocking-wizard: Fix Oops in clk_wzrd_register_divider()<br /> <br /> Smatch detected this potential error pointer dereference<br /> clk_wzrd_register_divider(). If devm_clk_hw_register() fails then<br /> it sets "hw" to an error pointer and then dereferences it on the<br /> next line. Return the error directly instead.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: mwifiex: fix memory leak in mwifiex_histogram_read()<br /> <br /> Always free the zeroed page on return from &amp;#39;mwifiex_histogram_read()&amp;#39;.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> l2tp: Avoid possible recursive deadlock in l2tp_tunnel_register()<br /> <br /> When a file descriptor of pppol2tp socket is passed as file descriptor<br /> of UDP socket, a recursive deadlock occurs in l2tp_tunnel_register().<br /> This situation is reproduced by the following program:<br /> <br /> int main(void)<br /> {<br /> int sock;<br /> struct sockaddr_pppol2tp addr;<br /> <br /> sock = socket(AF_PPPOX, SOCK_DGRAM, PX_PROTO_OL2TP);<br /> if (sock

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> iommufd: IOMMUFD_DESTROY should not increase the refcount<br /> <br /> syzkaller found a race where IOMMUFD_DESTROY increments the refcount:<br /> <br /> obj = iommufd_get_object(ucmd-&gt;ictx, cmd-&gt;id, IOMMUFD_OBJ_ANY);<br /> if (IS_ERR(obj))<br /> return PTR_ERR(obj);<br /> iommufd_ref_to_users(obj);<br /> /* See iommufd_ref_to_users() */<br /> if (!iommufd_object_destroy_user(ucmd-&gt;ictx, obj))<br /> <br /> As part of the sequence to join the two existing primitives together.<br /> <br /> Allowing the refcount the be elevated without holding the destroy_rwsem<br /> violates the assumption that all temporary refcount elevations are<br /> protected by destroy_rwsem. Racing IOMMUFD_DESTROY with<br /> iommufd_object_destroy_user() will cause spurious failures:<br /> <br /> WARNING: CPU: 0 PID: 3076 at drivers/iommu/iommufd/device.c:477 iommufd_access_destroy+0x18/0x20 drivers/iommu/iommufd/device.c:478<br /> Modules linked in:<br /> CPU: 0 PID: 3076 Comm: syz-executor.0 Not tainted 6.3.0-rc1-syzkaller #0<br /> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/03/2023<br /> RIP: 0010:iommufd_access_destroy+0x18/0x20 drivers/iommu/iommufd/device.c:477<br /> Code: e8 3d 4e 00 00 84 c0 74 01 c3 0f 0b c3 0f 1f 44 00 00 f3 0f 1e fa 48 89 fe 48 8b bf a8 00 00 00 e8 1d 4e 00 00 84 c0 74 01 c3 0b c3 0f 1f 44 00 00 41 57 41 56 41 55 4c 8d ae d0 00 00 00 41<br /> RSP: 0018:ffffc90003067e08 EFLAGS: 00010246<br /> RAX: 0000000000000000 RBX: ffff888109ea0300 RCX: 0000000000000000<br /> RDX: 0000000000000001 RSI: 0000000000000000 RDI: 00000000ffffffff<br /> RBP: 0000000000000004 R08: 0000000000000000 R09: ffff88810bbb3500<br /> R10: ffff88810bbb3e48 R11: 0000000000000000 R12: ffffc90003067e88<br /> R13: ffffc90003067ea8 R14: ffff888101249800 R15: 00000000fffffffe<br /> FS: 00007ff7254fe6c0(0000) GS:ffff888237c00000(0000) knlGS:0000000000000000<br /> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> CR2: 0000555557262da8 CR3: 000000010a6fd000 CR4: 0000000000350ef0<br /> Call Trace:<br /> <br /> iommufd_test_create_access drivers/iommu/iommufd/selftest.c:596 [inline]<br /> iommufd_test+0x71c/0xcf0 drivers/iommu/iommufd/selftest.c:813<br /> iommufd_fops_ioctl+0x10f/0x1b0 drivers/iommu/iommufd/main.c:337<br /> vfs_ioctl fs/ioctl.c:51 [inline]<br /> __do_sys_ioctl fs/ioctl.c:870 [inline]<br /> __se_sys_ioctl fs/ioctl.c:856 [inline]<br /> __x64_sys_ioctl+0x84/0xc0 fs/ioctl.c:856<br /> do_syscall_x64 arch/x86/entry/common.c:50 [inline]<br /> do_syscall_64+0x38/0x80 arch/x86/entry/common.c:80<br /> entry_SYSCALL_64_after_hwframe+0x63/0xcd<br /> <br /> The solution is to not increment the refcount on the IOMMUFD_DESTROY path<br /> at all. Instead use the xa_lock to serialize everything. The refcount<br /> check == 1 and xa_erase can be done under a single critical region. This<br /> avoids the need for any refcount incrementing.<br /> <br /> It has the downside that if userspace races destroy with other operations<br /> it will get an EBUSY instead of waiting, but this is kind of racing is<br /> already dangerous.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> f2fs: fix information leak in f2fs_move_inline_dirents()<br /> <br /> When converting an inline directory to a regular one, f2fs is leaking<br /> uninitialized memory to disk because it doesn&amp;#39;t initialize the entire<br /> directory block. Fix this by zero-initializing the block.<br /> <br /> This bug was introduced by commit 4ec17d688d74 ("f2fs: avoid unneeded<br /> initializing when converting inline dentry"), which didn&amp;#39;t consider the<br /> security implications of leaking uninitialized memory to disk.<br /> <br /> This was found by running xfstest generic/435 on a KMSAN-enabled kernel.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> HID: wacom: Use ktime_t rather than int when dealing with timestamps<br /> <br /> Code which interacts with timestamps needs to use the ktime_t type<br /> returned by functions like ktime_get. The int type does not offer<br /> enough space to store these values, and attempting to use it is a<br /> recipe for problems. In this particular case, overflows would occur<br /> when calculating/storing timestamps leading to incorrect values being<br /> reported to userspace. In some cases these bad timestamps cause input<br /> handling in userspace to appear hung.

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ethtool: Fix uninitialized number of lanes<br /> <br /> It is not possible to set the number of lanes when setting link modes<br /> using the legacy IOCTL ethtool interface. Since &amp;#39;struct<br /> ethtool_link_ksettings&amp;#39; is not initialized in this path, drivers receive<br /> an uninitialized number of lanes in &amp;#39;struct<br /> ethtool_link_ksettings::lanes&amp;#39;.<br /> <br /> When this information is later queried from drivers, it results in the<br /> ethtool code making decisions based on uninitialized memory, leading to<br /> the following KMSAN splat [1]. In practice, this most likely only<br /> happens with the tun driver that simply returns whatever it got in the<br /> set operation.<br /> <br /> As far as I can tell, this uninitialized memory is not leaked to user<br /> space thanks to the &amp;#39;ethtool_ops-&gt;cap_link_lanes_supported&amp;#39; check in<br /> linkmodes_prepare_data().<br /> <br /> Fix by initializing the structure in the IOCTL path. Did not find any<br /> more call sites that pass an uninitialized structure when calling<br /> &amp;#39;ethtool_ops::set_link_ksettings()&amp;#39;.<br /> <br /> [1]<br /> BUG: KMSAN: uninit-value in ethnl_update_linkmodes net/ethtool/linkmodes.c:273 [inline]<br /> BUG: KMSAN: uninit-value in ethnl_set_linkmodes+0x190b/0x19d0 net/ethtool/linkmodes.c:333<br /> ethnl_update_linkmodes net/ethtool/linkmodes.c:273 [inline]<br /> ethnl_set_linkmodes+0x190b/0x19d0 net/ethtool/linkmodes.c:333<br /> ethnl_default_set_doit+0x88d/0xde0 net/ethtool/netlink.c:640<br /> genl_family_rcv_msg_doit net/netlink/genetlink.c:968 [inline]<br /> genl_family_rcv_msg net/netlink/genetlink.c:1048 [inline]<br /> genl_rcv_msg+0x141a/0x14c0 net/netlink/genetlink.c:1065<br /> netlink_rcv_skb+0x3f8/0x750 net/netlink/af_netlink.c:2577<br /> genl_rcv+0x40/0x60 net/netlink/genetlink.c:1076<br /> netlink_unicast_kernel net/netlink/af_netlink.c:1339 [inline]<br /> netlink_unicast+0xf41/0x1270 net/netlink/af_netlink.c:1365<br /> netlink_sendmsg+0x127d/0x1430 net/netlink/af_netlink.c:1942<br /> sock_sendmsg_nosec net/socket.c:724 [inline]<br /> sock_sendmsg net/socket.c:747 [inline]<br /> ____sys_sendmsg+0xa24/0xe40 net/socket.c:2501<br /> ___sys_sendmsg+0x2a1/0x3f0 net/socket.c:2555<br /> __sys_sendmsg net/socket.c:2584 [inline]<br /> __do_sys_sendmsg net/socket.c:2593 [inline]<br /> __se_sys_sendmsg net/socket.c:2591 [inline]<br /> __x64_sys_sendmsg+0x36b/0x540 net/socket.c:2591<br /> do_syscall_x64 arch/x86/entry/common.c:50 [inline]<br /> do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80<br /> entry_SYSCALL_64_after_hwframe+0x63/0xcd<br /> <br /> Uninit was stored to memory at:<br /> tun_get_link_ksettings+0x37/0x60 drivers/net/tun.c:3544<br /> __ethtool_get_link_ksettings+0x17b/0x260 net/ethtool/ioctl.c:441<br /> ethnl_set_linkmodes+0xee/0x19d0 net/ethtool/linkmodes.c:327<br /> ethnl_default_set_doit+0x88d/0xde0 net/ethtool/netlink.c:640<br /> genl_family_rcv_msg_doit net/netlink/genetlink.c:968 [inline]<br /> genl_family_rcv_msg net/netlink/genetlink.c:1048 [inline]<br /> genl_rcv_msg+0x141a/0x14c0 net/netlink/genetlink.c:1065<br /> netlink_rcv_skb+0x3f8/0x750 net/netlink/af_netlink.c:2577<br /> genl_rcv+0x40/0x60 net/netlink/genetlink.c:1076<br /> netlink_unicast_kernel net/netlink/af_netlink.c:1339 [inline]<br /> netlink_unicast+0xf41/0x1270 net/netlink/af_netlink.c:1365<br /> netlink_sendmsg+0x127d/0x1430 net/netlink/af_netlink.c:1942<br /> sock_sendmsg_nosec net/socket.c:724 [inline]<br /> sock_sendmsg net/socket.c:747 [inline]<br /> ____sys_sendmsg+0xa24/0xe40 net/socket.c:2501<br /> ___sys_sendmsg+0x2a1/0x3f0 net/socket.c:2555<br /> __sys_sendmsg net/socket.c:2584 [inline]<br /> __do_sys_sendmsg net/socket.c:2593 [inline]<br /> __se_sys_sendmsg net/socket.c:2591 [inline]<br /> __x64_sys_sendmsg+0x36b/0x540 net/socket.c:2591<br /> do_syscall_x64 arch/x86/entry/common.c:50 [inline]<br /> do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80<br /> entry_SYSCALL_64_after_hwframe+0x63/0xcd<br /> <br /> Uninit was stored to memory at:<br /> tun_set_link_ksettings+0x37/0x60 drivers/net/tun.c:3553<br /> ethtool_set_link_ksettings+0x600/0x690 net/ethtool/ioctl.c:609<br /> __dev_ethtool net/ethtool/ioctl.c:3024 [inline]<br /> dev_ethtool+0x1db9/0x2a70 net/ethtool/ioctl.c:3078<br /> dev_ioctl+0xb07/0x1270 net/core/dev_ioctl.c:524<br /> sock_do_ioctl+0x295/0x540 net/socket.c:1213<br /> sock_i<br /> ---truncated---

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> crypto: api - Use work queue in crypto_destroy_instance<br /> <br /> The function crypto_drop_spawn expects to be called in process<br /> context. However, when an instance is unregistered while it still<br /> has active users, the last user may cause the instance to be freed<br /> in atomic context.<br /> <br /> Fix this by delaying the freeing to a work queue.