Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> phy: ralink: mt7621-pci: add sentinel to quirks table<br /> <br /> With mt7621 soc_dev_attr fixed to register the soc as a device,<br /> kernel will experience an oops in soc_device_match_attr<br /> <br /> This quirk test was introduced in the staging driver in<br /> commit 9445ccb3714c ("staging: mt7621-pci-phy: add quirks for &amp;#39;E2&amp;#39;<br /> revision using &amp;#39;soc_device_attribute&amp;#39;"). The staging driver was removed,<br /> and later re-added in commit d87da32372a0 ("phy: ralink: Add PHY driver<br /> for MT7621 PCIe PHY") for kernel 5.11

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> capabilities: fix undefined behavior in bit shift for CAP_TO_MASK<br /> <br /> Shifting signed 32-bit value by 31 bits is undefined, so changing<br /> significant bit to unsigned. The UBSAN warning calltrace like below:<br /> <br /> UBSAN: shift-out-of-bounds in security/commoncap.c:1252:2<br /> left shift of 1 by 31 places cannot be represented in type &amp;#39;int&amp;#39;<br /> Call Trace:<br /> <br /> dump_stack_lvl+0x7d/0xa5<br /> dump_stack+0x15/0x1b<br /> ubsan_epilogue+0xe/0x4e<br /> __ubsan_handle_shift_out_of_bounds+0x1e7/0x20c<br /> cap_task_prctl+0x561/0x6f0<br /> security_task_prctl+0x5a/0xb0<br /> __x64_sys_prctl+0x61/0x8f0<br /> do_syscall_64+0x58/0x80<br /> entry_SYSCALL_64_after_hwframe+0x63/0xcd<br />

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network<br /> <br /> When copying a `struct ifaddrlblmsg` to the network, __ifal_reserved<br /> remained uninitialized, resulting in a 1-byte infoleak:<br /> <br /> BUG: KMSAN: kernel-network-infoleak in __netdev_start_xmit ./include/linux/netdevice.h:4841<br /> __netdev_start_xmit ./include/linux/netdevice.h:4841<br /> netdev_start_xmit ./include/linux/netdevice.h:4857<br /> xmit_one net/core/dev.c:3590<br /> dev_hard_start_xmit+0x1dc/0x800 net/core/dev.c:3606<br /> __dev_queue_xmit+0x17e8/0x4350 net/core/dev.c:4256<br /> dev_queue_xmit ./include/linux/netdevice.h:3009<br /> __netlink_deliver_tap_skb net/netlink/af_netlink.c:307<br /> __netlink_deliver_tap+0x728/0xad0 net/netlink/af_netlink.c:325<br /> netlink_deliver_tap net/netlink/af_netlink.c:338<br /> __netlink_sendskb net/netlink/af_netlink.c:1263<br /> netlink_sendskb+0x1d9/0x200 net/netlink/af_netlink.c:1272<br /> netlink_unicast+0x56d/0xf50 net/netlink/af_netlink.c:1360<br /> nlmsg_unicast ./include/net/netlink.h:1061<br /> rtnl_unicast+0x5a/0x80 net/core/rtnetlink.c:758<br /> ip6addrlbl_get+0xfad/0x10f0 net/ipv6/addrlabel.c:628<br /> rtnetlink_rcv_msg+0xb33/0x1570 net/core/rtnetlink.c:6082<br /> ...<br /> Uninit was created at:<br /> slab_post_alloc_hook+0x118/0xb00 mm/slab.h:742<br /> slab_alloc_node mm/slub.c:3398<br /> __kmem_cache_alloc_node+0x4f2/0x930 mm/slub.c:3437<br /> __do_kmalloc_node mm/slab_common.c:954<br /> __kmalloc_node_track_caller+0x117/0x3d0 mm/slab_common.c:975<br /> kmalloc_reserve net/core/skbuff.c:437<br /> __alloc_skb+0x27a/0xab0 net/core/skbuff.c:509<br /> alloc_skb ./include/linux/skbuff.h:1267<br /> nlmsg_new ./include/net/netlink.h:964<br /> ip6addrlbl_get+0x490/0x10f0 net/ipv6/addrlabel.c:608<br /> rtnetlink_rcv_msg+0xb33/0x1570 net/core/rtnetlink.c:6082<br /> netlink_rcv_skb+0x299/0x550 net/netlink/af_netlink.c:2540<br /> rtnetlink_rcv+0x26/0x30 net/core/rtnetlink.c:6109<br /> netlink_unicast_kernel net/netlink/af_netlink.c:1319<br /> netlink_unicast+0x9ab/0xf50 net/netlink/af_netlink.c:1345<br /> netlink_sendmsg+0xebc/0x10f0 net/netlink/af_netlink.c:1921<br /> ...<br /> <br /> This patch ensures that the reserved field is always initialized.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: wwan: iosm: fix memory leak in ipc_pcie_read_bios_cfg<br /> <br /> ipc_pcie_read_bios_cfg() is using the acpi_evaluate_dsm() to<br /> obtain the wwan power state configuration from BIOS but is<br /> not freeing the acpi_object. The acpi_evaluate_dsm() returned<br /> acpi_object to be freed.<br /> <br /> Free the acpi_object after use.

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: marvell: prestera: fix memory leak in prestera_rxtx_switch_init()<br /> <br /> When prestera_sdma_switch_init() failed, the memory pointed to by<br /> sw-&gt;rxtx isn&amp;#39;t released. Fix it. Only be compiled, not be tested.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> dmaengine: ti: k3-udma-glue: fix memory leak when register device fail<br /> <br /> If device_register() fails, it should call put_device() to give<br /> up reference, the name allocated in dev_set_name() can be freed<br /> in callback function kobject_cleanup().

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> dmaengine: mv_xor_v2: Fix a resource leak in mv_xor_v2_remove()<br /> <br /> A clk_prepare_enable() call in the probe is not balanced by a corresponding<br /> clk_disable_unprepare() in the remove function.<br /> <br /> Add the missing call.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> octeontx2-pf: Fix SQE threshold checking<br /> <br /> Current way of checking available SQE count which is based on<br /> HW updated SQB count could result in driver submitting an SQE<br /> even before CQE for the previously transmitted SQE at the same<br /> index is processed in NAPI resulting losing SKB pointers,<br /> hence a leak. Fix this by checking a consumer index which<br /> is updated once CQE is processed.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: lapbether: fix issue of invalid opcode in lapbeth_open()<br /> <br /> If lapb_register() failed when lapb device goes to up for the first time,<br /> the NAPI is not disabled. As a result, the invalid opcode issue is<br /> reported when the lapb device goes to up for the second time.<br /> <br /> The stack info is as follows:<br /> [ 1958.311422][T11356] kernel BUG at net/core/dev.c:6442!<br /> [ 1958.312206][T11356] invalid opcode: 0000 [#1] PREEMPT SMP KASAN<br /> [ 1958.315979][T11356] RIP: 0010:napi_enable+0x16a/0x1f0<br /> [ 1958.332310][T11356] Call Trace:<br /> [ 1958.332817][T11356] <br /> [ 1958.336135][T11356] lapbeth_open+0x18/0x90<br /> [ 1958.337446][T11356] __dev_open+0x258/0x490<br /> [ 1958.341672][T11356] __dev_change_flags+0x4d4/0x6a0<br /> [ 1958.345325][T11356] dev_change_flags+0x93/0x160<br /> [ 1958.346027][T11356] devinet_ioctl+0x1276/0x1bf0<br /> [ 1958.346738][T11356] inet_ioctl+0x1c8/0x2d0<br /> [ 1958.349638][T11356] sock_ioctl+0x5d1/0x750<br /> [ 1958.356059][T11356] __x64_sys_ioctl+0x3ec/0x1790<br /> [ 1958.365594][T11356] do_syscall_64+0x35/0x80<br /> [ 1958.366239][T11356] entry_SYSCALL_64_after_hwframe+0x46/0xb0<br /> [ 1958.377381][T11356]

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> can: j1939: j1939_send_one(): fix missing CAN header initialization<br /> <br /> The read access to struct canxl_frame::len inside of a j1939 created<br /> skbuff revealed a missing initialization of reserved and later filled<br /> elements in struct can_frame.<br /> <br /> This patch initializes the 8 byte CAN header with zero.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> udf: Fix a slab-out-of-bounds write bug in udf_find_entry()<br /> <br /> Syzbot reported a slab-out-of-bounds Write bug:<br /> <br /> loop0: detected capacity change from 0 to 2048<br /> ==================================================================<br /> BUG: KASAN: slab-out-of-bounds in udf_find_entry+0x8a5/0x14f0<br /> fs/udf/namei.c:253<br /> Write of size 105 at addr ffff8880123ff896 by task syz-executor323/3610<br /> <br /> CPU: 0 PID: 3610 Comm: syz-executor323 Not tainted<br /> 6.1.0-rc2-syzkaller-00105-gb229b6ca5abb #0<br /> Hardware name: Google Compute Engine/Google Compute Engine, BIOS<br /> Google 10/11/2022<br /> Call Trace:<br /> <br /> __dump_stack lib/dump_stack.c:88 [inline]<br /> dump_stack_lvl+0x1b1/0x28e lib/dump_stack.c:106<br /> print_address_description+0x74/0x340 mm/kasan/report.c:284<br /> print_report+0x107/0x1f0 mm/kasan/report.c:395<br /> kasan_report+0xcd/0x100 mm/kasan/report.c:495<br /> kasan_check_range+0x2a7/0x2e0 mm/kasan/generic.c:189<br /> memcpy+0x3c/0x60 mm/kasan/shadow.c:66<br /> udf_find_entry+0x8a5/0x14f0 fs/udf/namei.c:253<br /> udf_lookup+0xef/0x340 fs/udf/namei.c:309<br /> lookup_open fs/namei.c:3391 [inline]<br /> open_last_lookups fs/namei.c:3481 [inline]<br /> path_openat+0x10e6/0x2df0 fs/namei.c:3710<br /> do_filp_open+0x264/0x4f0 fs/namei.c:3740<br /> do_sys_openat2+0x124/0x4e0 fs/open.c:1310<br /> do_sys_open fs/open.c:1326 [inline]<br /> __do_sys_creat fs/open.c:1402 [inline]<br /> __se_sys_creat fs/open.c:1396 [inline]<br /> __x64_sys_creat+0x11f/0x160 fs/open.c:1396<br /> do_syscall_x64 arch/x86/entry/common.c:50 [inline]<br /> do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80<br /> entry_SYSCALL_64_after_hwframe+0x63/0xcd<br /> RIP: 0033:0x7ffab0d164d9<br /> Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89<br /> f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 3d 01<br /> f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48<br /> RSP: 002b:00007ffe1a7e6bb8 EFLAGS: 00000246 ORIG_RAX: 0000000000000055<br /> RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007ffab0d164d9<br /> RDX: 00007ffab0d164d9 RSI: 0000000000000000 RDI: 0000000020000180<br /> RBP: 00007ffab0cd5a10 R08: 0000000000000000 R09: 0000000000000000<br /> R10: 00005555573552c0 R11: 0000000000000246 R12: 00007ffab0cd5aa0<br /> R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000<br /> <br /> <br /> Allocated by task 3610:<br /> kasan_save_stack mm/kasan/common.c:45 [inline]<br /> kasan_set_track+0x3d/0x60 mm/kasan/common.c:52<br /> ____kasan_kmalloc mm/kasan/common.c:371 [inline]<br /> __kasan_kmalloc+0x97/0xb0 mm/kasan/common.c:380<br /> kmalloc include/linux/slab.h:576 [inline]<br /> udf_find_entry+0x7b6/0x14f0 fs/udf/namei.c:243<br /> udf_lookup+0xef/0x340 fs/udf/namei.c:309<br /> lookup_open fs/namei.c:3391 [inline]<br /> open_last_lookups fs/namei.c:3481 [inline]<br /> path_openat+0x10e6/0x2df0 fs/namei.c:3710<br /> do_filp_open+0x264/0x4f0 fs/namei.c:3740<br /> do_sys_openat2+0x124/0x4e0 fs/open.c:1310<br /> do_sys_open fs/open.c:1326 [inline]<br /> __do_sys_creat fs/open.c:1402 [inline]<br /> __se_sys_creat fs/open.c:1396 [inline]<br /> __x64_sys_creat+0x11f/0x160 fs/open.c:1396<br /> do_syscall_x64 arch/x86/entry/common.c:50 [inline]<br /> do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80<br /> entry_SYSCALL_64_after_hwframe+0x63/0xcd<br /> <br /> The buggy address belongs to the object at ffff8880123ff800<br /> which belongs to the cache kmalloc-256 of size 256<br /> The buggy address is located 150 bytes inside of<br /> 256-byte region [ffff8880123ff800, ffff8880123ff900)<br /> <br /> The buggy address belongs to the physical page:<br /> page:ffffea000048ff80 refcount:1 mapcount:0 mapping:0000000000000000<br /> index:0x0 pfn:0x123fe<br /> head:ffffea000048ff80 order:1 compound_mapcount:0 compound_pincount:0<br /> flags: 0xfff00000010200(slab|head|node=0|zone=1|lastcpupid=0x7ff)<br /> raw: 00fff00000010200 ffffea00004b8500 dead000000000003 ffff888012041b40<br /> raw: 0000000000000000 0000000080100010 00000001ffffffff 0000000000000000<br /> page dumped because: kasan: bad access detected<br /> page_owner tracks the page as allocated<br /> page last allocated via order 0, migratetype Unmovable, gfp_mask 0x0(),<br /> pid 1, tgid 1 (swapper/0), ts 1841222404, free_ts 0<br /> create_dummy_stack mm/page_owner.c:<br /> ---truncated---