Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> crypto: xilinx - call finalize with bh disabled<br /> <br /> When calling crypto_finalize_request, BH should be disabled to avoid<br /> triggering the following calltrace:<br /> <br /> ------------[ cut here ]------------<br /> WARNING: CPU: 2 PID: 74 at crypto/crypto_engine.c:58 crypto_finalize_request+0xa0/0x118<br /> Modules linked in: cryptodev(O)<br /> CPU: 2 PID: 74 Comm: firmware:zynqmp Tainted: G O 6.8.0-rc1-yocto-standard #323<br /> Hardware name: ZynqMP ZCU102 Rev1.0 (DT)<br /> pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)<br /> pc : crypto_finalize_request+0xa0/0x118<br /> lr : crypto_finalize_request+0x104/0x118<br /> sp : ffffffc085353ce0<br /> x29: ffffffc085353ce0 x28: 0000000000000000 x27: ffffff8808ea8688<br /> x26: ffffffc081715038 x25: 0000000000000000 x24: ffffff880100db00<br /> x23: ffffff880100da80 x22: 0000000000000000 x21: 0000000000000000<br /> x20: ffffff8805b14000 x19: ffffff880100da80 x18: 0000000000010450<br /> x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000<br /> x14: 0000000000000003 x13: 0000000000000000 x12: ffffff880100dad0<br /> x11: 0000000000000000 x10: ffffffc0832dcd08 x9 : ffffffc0812416d8<br /> x8 : 00000000000001f4 x7 : ffffffc0830d2830 x6 : 0000000000000001<br /> x5 : ffffffc082091000 x4 : ffffffc082091658 x3 : 0000000000000000<br /> x2 : ffffffc7f9653000 x1 : 0000000000000000 x0 : ffffff8802d20000<br /> Call trace:<br /> crypto_finalize_request+0xa0/0x118<br /> crypto_finalize_aead_request+0x18/0x30<br /> zynqmp_handle_aes_req+0xcc/0x388<br /> crypto_pump_work+0x168/0x2d8<br /> kthread_worker_fn+0xfc/0x3a0<br /> kthread+0x118/0x138<br /> ret_from_fork+0x10/0x20<br /> irq event stamp: 40<br /> hardirqs last enabled at (39): [] _raw_spin_unlock_irqrestore+0x70/0xb0<br /> hardirqs last disabled at (40): [] el1_dbg+0x28/0x90<br /> softirqs last enabled at (36): [] kernel_neon_begin+0x8c/0xf0<br /> softirqs last disabled at (34): [] kernel_neon_begin+0x60/0xf0<br /> ---[ end trace 0000000000000000 ]---

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> dm: call the resume method on internal suspend<br /> <br /> There is this reported crash when experimenting with the lvm2 testsuite.<br /> The list corruption is caused by the fact that the postsuspend and resume<br /> methods were not paired correctly; there were two consecutive calls to the<br /> origin_postsuspend function. The second call attempts to remove the<br /> "hash_list" entry from a list, while it was already removed by the first<br /> call.<br /> <br /> Fix __dm_internal_resume so that it calls the preresume and resume<br /> methods of the table&amp;#39;s targets.<br /> <br /> If a preresume method of some target fails, we are in a tricky situation.<br /> We can&amp;#39;t return an error because dm_internal_resume isn&amp;#39;t supposed to<br /> return errors. We can&amp;#39;t return success, because then the "resume" and<br /> "postsuspend" methods would not be paired correctly. So, we set the<br /> DMF_SUSPENDED flag and we fake normal suspend - it may confuse userspace<br /> tools, but it won&amp;#39;t cause a kernel crash.<br /> <br /> ------------[ cut here ]------------<br /> kernel BUG at lib/list_debug.c:56!<br /> invalid opcode: 0000 [#1] PREEMPT SMP<br /> CPU: 1 PID: 8343 Comm: dmsetup Not tainted 6.8.0-rc6 #4<br /> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014<br /> RIP: 0010:__list_del_entry_valid_or_report+0x77/0xc0<br /> <br /> RSP: 0018:ffff8881b831bcc0 EFLAGS: 00010282<br /> RAX: 000000000000004e RBX: ffff888143b6eb80 RCX: 0000000000000000<br /> RDX: 0000000000000001 RSI: ffffffff819053d0 RDI: 00000000ffffffff<br /> RBP: ffff8881b83a3400 R08: 00000000fffeffff R09: 0000000000000058<br /> R10: 0000000000000000 R11: ffffffff81a24080 R12: 0000000000000001<br /> R13: ffff88814538e000 R14: ffff888143bc6dc0 R15: ffffffffa02e4bb0<br /> FS: 00000000f7c0f780(0000) GS:ffff8893f0a40000(0000) knlGS:0000000000000000<br /> CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033<br /> CR2: 0000000057fb5000 CR3: 0000000143474000 CR4: 00000000000006b0<br /> Call Trace:<br /> <br /> ? die+0x2d/0x80<br /> ? do_trap+0xeb/0xf0<br /> ? __list_del_entry_valid_or_report+0x77/0xc0<br /> ? do_error_trap+0x60/0x80<br /> ? __list_del_entry_valid_or_report+0x77/0xc0<br /> ? exc_invalid_op+0x49/0x60<br /> ? __list_del_entry_valid_or_report+0x77/0xc0<br /> ? asm_exc_invalid_op+0x16/0x20<br /> ? table_deps+0x1b0/0x1b0 [dm_mod]<br /> ? __list_del_entry_valid_or_report+0x77/0xc0<br /> origin_postsuspend+0x1a/0x50 [dm_snapshot]<br /> dm_table_postsuspend_targets+0x34/0x50 [dm_mod]<br /> dm_suspend+0xd8/0xf0 [dm_mod]<br /> dev_suspend+0x1f2/0x2f0 [dm_mod]<br /> ? table_deps+0x1b0/0x1b0 [dm_mod]<br /> ctl_ioctl+0x300/0x5f0 [dm_mod]<br /> dm_compat_ctl_ioctl+0x7/0x10 [dm_mod]<br /> __x64_compat_sys_ioctl+0x104/0x170<br /> do_syscall_64+0x184/0x1b0<br /> entry_SYSCALL_64_after_hwframe+0x46/0x4e<br /> RIP: 0033:0xf7e6aead<br /> <br /> ---[ end trace 0000000000000000 ]---

Missing Authorization vulnerability in Undsgn Uncode Core.This issue affects Uncode Core: from n/a through 2.8.8.<br /> <br />

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: b43: Stop/wake correct queue in DMA Tx path when QoS is disabled<br /> <br /> When QoS is disabled, the queue priority value will not map to the correct<br /> ieee80211 queue since there is only one queue. Stop/wake queue 0 when QoS<br /> is disabled to prevent trying to stop/wake a non-existent queue and failing<br /> to stop/wake the actual queue instantiated.<br /> <br /> Log of issue before change (with kernel parameter qos=0):<br /> [ +5.112651] ------------[ cut here ]------------<br /> [ +0.000005] WARNING: CPU: 7 PID: 25513 at net/mac80211/util.c:449 __ieee80211_wake_queue+0xd5/0x180 [mac80211]<br /> [ +0.000067] Modules linked in: b43(O) snd_seq_dummy snd_hrtimer snd_seq snd_seq_device nft_chain_nat xt_MASQUERADE nf_nat xfrm_user xfrm_algo xt_addrtype overlay ccm af_packet amdgpu snd_hda_codec_cirrus snd_hda_codec_generic ledtrig_audio drm_exec amdxcp gpu_sched xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6t_rpfilter ipt_rpfilter xt_pkttype xt_LOG nf_log_syslog xt_tcpudp nft_compat nf_tables nfnetlink sch_fq_codel btusb uinput iTCO_wdt ctr btrtl intel_pmc_bxt i915 intel_rapl_msr mei_hdcp mei_pxp joydev at24 watchdog btintel atkbd libps2 serio radeon btbcm vivaldi_fmap btmtk intel_rapl_common snd_hda_codec_hdmi bluetooth uvcvideo nls_iso8859_1 applesmc nls_cp437 x86_pkg_temp_thermal snd_hda_intel intel_powerclamp vfat videobuf2_vmalloc coretemp fat snd_intel_dspcfg crc32_pclmul uvc polyval_clmulni snd_intel_sdw_acpi loop videobuf2_memops snd_hda_codec tun drm_suballoc_helper polyval_generic drm_ttm_helper drm_buddy tap ecdh_generic videobuf2_v4l2 gf128mul macvlan ttm ghash_clmulni_intel ecc tg3<br /> [ +0.000044] videodev bridge snd_hda_core rapl crc16 drm_display_helper cec mousedev snd_hwdep evdev intel_cstate bcm5974 hid_appleir videobuf2_common stp mac_hid libphy snd_pcm drm_kms_helper acpi_als mei_me intel_uncore llc mc snd_timer intel_gtt industrialio_triggered_buffer apple_mfi_fastcharge i2c_i801 mei snd lpc_ich agpgart ptp i2c_smbus thunderbolt apple_gmux i2c_algo_bit kfifo_buf video industrialio soundcore pps_core wmi tiny_power_button sbs sbshc button ac cordic bcma mac80211 cfg80211 ssb rfkill libarc4 kvm_intel kvm drm irqbypass fuse backlight firmware_class efi_pstore configfs efivarfs dmi_sysfs ip_tables x_tables autofs4 dm_crypt cbc encrypted_keys trusted asn1_encoder tee tpm rng_core input_leds hid_apple led_class hid_generic usbhid hid sd_mod t10_pi crc64_rocksoft crc64 crc_t10dif crct10dif_generic ahci libahci libata uhci_hcd ehci_pci ehci_hcd crct10dif_pclmul crct10dif_common sha512_ssse3 sha512_generic sha256_ssse3 sha1_ssse3 aesni_intel usbcore scsi_mod libaes crypto_simd cryptd scsi_common<br /> [ +0.000055] usb_common rtc_cmos btrfs blake2b_generic libcrc32c crc32c_generic crc32c_intel xor raid6_pq dm_snapshot dm_bufio dm_mod dax [last unloaded: b43(O)]<br /> [ +0.000009] CPU: 7 PID: 25513 Comm: irq/17-b43 Tainted: G W O 6.6.7 #1-NixOS<br /> [ +0.000003] Hardware name: Apple Inc. MacBookPro8,3/Mac-942459F5819B171B, BIOS 87.0.0.0.0 06/13/2019<br /> [ +0.000001] RIP: 0010:__ieee80211_wake_queue+0xd5/0x180 [mac80211]<br /> [ +0.000046] Code: 00 45 85 e4 0f 85 9b 00 00 00 48 8d bd 40 09 00 00 f0 48 0f ba ad 48 09 00 00 00 72 0f 5b 5d 41 5c 41 5d 41 5e e9 cb 6d 3c d0 0b 5b 5d 41 5c 41 5d 41 5e c3 cc cc cc cc 48 8d b4 16 94 00 00<br /> [ +0.000002] RSP: 0018:ffffc90003c77d60 EFLAGS: 00010097<br /> [ +0.000001] RAX: 0000000000000001 RBX: 0000000000000002 RCX: 0000000000000000<br /> [ +0.000001] RDX: 0000000000000000 RSI: 0000000000000002 RDI: ffff88820b924900<br /> [ +0.000002] RBP: ffff88820b924900 R08: ffffc90003c77d90 R09: 000000000003bfd0<br /> [ +0.000001] R10: ffff88820b924900 R11: ffffc90003c77c68 R12: 0000000000000000<br /> [ +0.000001] R13: 0000000000000000 R14: ffffc90003c77d90 R15: ffffffffc0fa6f40<br /> [ +0.000001] FS: 0000000000000000(0000) GS:ffff88846fb80000(0000) knlGS:0000000000000000<br /> [ +0.000001] CS: 0010 DS: 0<br /> ---truncated---

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> powerpc/rtas: use correct function name for resetting TCE tables<br /> <br /> The PAPR spec spells the function name as<br /> <br /> "ibm,reset-pe-dma-windows"<br /> <br /> but in practice firmware uses the singular form:<br /> <br /> "ibm,reset-pe-dma-window"<br /> <br /> in the device tree. Since we have the wrong spelling in the RTAS<br /> function table, reverse lookups (token -&gt; name) fail and warn:<br /> <br /> unexpected failed lookup for token 86<br /> WARNING: CPU: 1 PID: 545 at arch/powerpc/kernel/rtas.c:659 __do_enter_rtas_trace+0x2a4/0x2b4<br /> CPU: 1 PID: 545 Comm: systemd-udevd Not tainted 6.8.0-rc4 #30<br /> Hardware name: IBM,9105-22A POWER10 (raw) 0x800200 0xf000006 of:IBM,FW1060.00 (NL1060_028) hv:phyp pSeries<br /> NIP [c0000000000417f0] __do_enter_rtas_trace+0x2a4/0x2b4<br /> LR [c0000000000417ec] __do_enter_rtas_trace+0x2a0/0x2b4<br /> Call Trace:<br /> __do_enter_rtas_trace+0x2a0/0x2b4 (unreliable)<br /> rtas_call+0x1f8/0x3e0<br /> enable_ddw.constprop.0+0x4d0/0xc84<br /> dma_iommu_dma_supported+0xe8/0x24c<br /> dma_set_mask+0x5c/0xd8<br /> mlx5_pci_init.constprop.0+0xf0/0x46c [mlx5_core]<br /> probe_one+0xfc/0x32c [mlx5_core]<br /> local_pci_probe+0x68/0x12c<br /> pci_call_probe+0x68/0x1ec<br /> pci_device_probe+0xbc/0x1a8<br /> really_probe+0x104/0x570<br /> __driver_probe_device+0xb8/0x224<br /> driver_probe_device+0x54/0x130<br /> __driver_attach+0x158/0x2b0<br /> bus_for_each_dev+0xa8/0x120<br /> driver_attach+0x34/0x48<br /> bus_add_driver+0x174/0x304<br /> driver_register+0x8c/0x1c4<br /> __pci_register_driver+0x68/0x7c<br /> mlx5_init+0xb8/0x118 [mlx5_core]<br /> do_one_initcall+0x60/0x388<br /> do_init_module+0x7c/0x2a4<br /> init_module_from_file+0xb4/0x108<br /> idempotent_init_module+0x184/0x34c<br /> sys_finit_module+0x90/0x114<br /> <br /> And oopses are possible when lockdep is enabled or the RTAS<br /> tracepoints are active, since those paths dereference the result of<br /> the lookup.<br /> <br /> Use the correct spelling to match firmware&amp;#39;s behavior, adjusting the<br /> related constants to match.

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 /> netlink: add nla be16/32 types to minlen array<br /> <br /> BUG: KMSAN: uninit-value in nla_validate_range_unsigned lib/nlattr.c:222 [inline]<br /> BUG: KMSAN: uninit-value in nla_validate_int_range lib/nlattr.c:336 [inline]<br /> BUG: KMSAN: uninit-value in validate_nla lib/nlattr.c:575 [inline]<br /> BUG: KMSAN: uninit-value in __nla_validate_parse+0x2e20/0x45c0 lib/nlattr.c:631<br /> nla_validate_range_unsigned lib/nlattr.c:222 [inline]<br /> nla_validate_int_range lib/nlattr.c:336 [inline]<br /> validate_nla lib/nlattr.c:575 [inline]<br /> ...<br /> <br /> The message in question matches this policy:<br /> <br /> [NFTA_TARGET_REV] = NLA_POLICY_MAX(NLA_BE32, 255),<br /> <br /> but because NLA_BE32 size in minlen array is 0, the validation<br /> code will read past the malformed (too small) attribute.<br /> <br /> Note: Other attributes, e.g. BITFIELD32, SINT, UINT.. are also missing:<br /> those likely should be added too.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> mm/debug_vm_pgtable: fix BUG_ON with pud advanced test<br /> <br /> Architectures like powerpc add debug checks to ensure we find only devmap<br /> PUD pte entries. These debug checks are only done with CONFIG_DEBUG_VM. <br /> This patch marks the ptes used for PUD advanced test devmap pte entries so<br /> that we don&amp;#39;t hit on debug checks on architecture like ppc64 as below.<br /> <br /> WARNING: CPU: 2 PID: 1 at arch/powerpc/mm/book3s64/radix_pgtable.c:1382 radix__pud_hugepage_update+0x38/0x138<br /> ....<br /> NIP [c0000000000a7004] radix__pud_hugepage_update+0x38/0x138<br /> LR [c0000000000a77a8] radix__pudp_huge_get_and_clear+0x28/0x60<br /> Call Trace:<br /> [c000000004a2f950] [c000000004a2f9a0] 0xc000000004a2f9a0 (unreliable)<br /> [c000000004a2f980] [000d34c100000000] 0xd34c100000000<br /> [c000000004a2f9a0] [c00000000206ba98] pud_advanced_tests+0x118/0x334<br /> [c000000004a2fa40] [c00000000206db34] debug_vm_pgtable+0xcbc/0x1c48<br /> [c000000004a2fc10] [c00000000000fd28] do_one_initcall+0x60/0x388<br /> <br /> Also<br /> <br /> kernel BUG at arch/powerpc/mm/book3s64/pgtable.c:202!<br /> ....<br /> <br /> NIP [c000000000096510] pudp_huge_get_and_clear_full+0x98/0x174<br /> LR [c00000000206bb34] pud_advanced_tests+0x1b4/0x334<br /> Call Trace:<br /> [c000000004a2f950] [000d34c100000000] 0xd34c100000000 (unreliable)<br /> [c000000004a2f9a0] [c00000000206bb34] pud_advanced_tests+0x1b4/0x334<br /> [c000000004a2fa40] [c00000000206db34] debug_vm_pgtable+0xcbc/0x1c48<br /> [c000000004a2fc10] [c00000000000fd28] do_one_initcall+0x60/0x388

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> netfilter: nf_conntrack_h323: Add protection for bmp length out of range<br /> <br /> UBSAN load reports an exception of BRK#5515 SHIFT_ISSUE:Bitwise shifts<br /> that are out of bounds for their data type.<br /> <br /> vmlinux get_bitmap(b=75) + 712<br /> <br /> vmlinux decode_seq(bs=0xFFFFFFD008037000, f=0xFFFFFFD008037018, level=134443100) + 1956<br /> <br /> vmlinux decode_choice(base=0xFFFFFFD0080370F0, level=23843636) + 1216<br /> <br /> vmlinux decode_seq(f=0xFFFFFFD0080371A8, level=134443500) + 812<br /> <br /> vmlinux decode_choice(base=0xFFFFFFD008037280, level=0) + 1216<br /> <br /> vmlinux DecodeRasMessage() + 304<br /> <br /> vmlinux ras_help() + 684<br /> <br /> vmlinux nf_confirm() + 188<br /> <br /> <br /> Due to abnormal data in skb-&gt;data, the extension bitmap length<br /> exceeds 32 when decoding ras message then uses the length to make<br /> a shift operation. It will change into negative after several loop.<br /> UBSAN load could detect a negative shift as an undefined behaviour<br /> and reports exception.<br /> So we add the protection to avoid the length exceeding 32. Or else<br /> it will return out of range error and stop decoding.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net/ipv6: avoid possible UAF in ip6_route_mpath_notify()<br /> <br /> syzbot found another use-after-free in ip6_route_mpath_notify() [1]<br /> <br /> Commit f7225172f25a ("net/ipv6: prevent use after free in<br /> ip6_route_mpath_notify") was not able to fix the root cause.<br /> <br /> We need to defer the fib6_info_release() calls after<br /> ip6_route_mpath_notify(), in the cleanup phase.<br /> <br /> [1]<br /> BUG: KASAN: slab-use-after-free in rt6_fill_node+0x1460/0x1ac0<br /> Read of size 4 at addr ffff88809a07fc64 by task syz-executor.2/23037<br /> <br /> CPU: 0 PID: 23037 Comm: syz-executor.2 Not tainted 6.8.0-rc4-syzkaller-01035-gea7f3cfaa588 #0<br /> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024<br /> Call Trace:<br /> <br /> __dump_stack lib/dump_stack.c:88 [inline]<br /> dump_stack_lvl+0x1e7/0x2e0 lib/dump_stack.c:106<br /> print_address_description mm/kasan/report.c:377 [inline]<br /> print_report+0x167/0x540 mm/kasan/report.c:488<br /> kasan_report+0x142/0x180 mm/kasan/report.c:601<br /> rt6_fill_node+0x1460/0x1ac0<br /> inet6_rt_notify+0x13b/0x290 net/ipv6/route.c:6184<br /> ip6_route_mpath_notify net/ipv6/route.c:5198 [inline]<br /> ip6_route_multipath_add net/ipv6/route.c:5404 [inline]<br /> inet6_rtm_newroute+0x1d0f/0x2300 net/ipv6/route.c:5517<br /> rtnetlink_rcv_msg+0x885/0x1040 net/core/rtnetlink.c:6597<br /> netlink_rcv_skb+0x1e3/0x430 net/netlink/af_netlink.c:2543<br /> netlink_unicast_kernel net/netlink/af_netlink.c:1341 [inline]<br /> netlink_unicast+0x7ea/0x980 net/netlink/af_netlink.c:1367<br /> netlink_sendmsg+0xa3b/0xd70 net/netlink/af_netlink.c:1908<br /> sock_sendmsg_nosec net/socket.c:730 [inline]<br /> __sock_sendmsg+0x221/0x270 net/socket.c:745<br /> ____sys_sendmsg+0x525/0x7d0 net/socket.c:2584<br /> ___sys_sendmsg net/socket.c:2638 [inline]<br /> __sys_sendmsg+0x2b0/0x3a0 net/socket.c:2667<br /> do_syscall_64+0xf9/0x240<br /> entry_SYSCALL_64_after_hwframe+0x6f/0x77<br /> RIP: 0033:0x7f73dd87dda9<br /> Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 e1 20 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b0 ff ff ff f7 d8 64 89 01 48<br /> RSP: 002b:00007f73de6550c8 EFLAGS: 00000246 ORIG_RAX: 000000000000002e<br /> RAX: ffffffffffffffda RBX: 00007f73dd9ac050 RCX: 00007f73dd87dda9<br /> RDX: 0000000000000000 RSI: 0000000020000140 RDI: 0000000000000005<br /> RBP: 00007f73dd8ca47a R08: 0000000000000000 R09: 0000000000000000<br /> R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000<br /> R13: 000000000000006e R14: 00007f73dd9ac050 R15: 00007ffdbdeb7858<br /> <br /> <br /> Allocated by task 23037:<br /> kasan_save_stack mm/kasan/common.c:47 [inline]<br /> kasan_save_track+0x3f/0x80 mm/kasan/common.c:68<br /> poison_kmalloc_redzone mm/kasan/common.c:372 [inline]<br /> __kasan_kmalloc+0x98/0xb0 mm/kasan/common.c:389<br /> kasan_kmalloc include/linux/kasan.h:211 [inline]<br /> __do_kmalloc_node mm/slub.c:3981 [inline]<br /> __kmalloc+0x22e/0x490 mm/slub.c:3994<br /> kmalloc include/linux/slab.h:594 [inline]<br /> kzalloc include/linux/slab.h:711 [inline]<br /> fib6_info_alloc+0x2e/0xf0 net/ipv6/ip6_fib.c:155<br /> ip6_route_info_create+0x445/0x12b0 net/ipv6/route.c:3758<br /> ip6_route_multipath_add net/ipv6/route.c:5298 [inline]<br /> inet6_rtm_newroute+0x744/0x2300 net/ipv6/route.c:5517<br /> rtnetlink_rcv_msg+0x885/0x1040 net/core/rtnetlink.c:6597<br /> netlink_rcv_skb+0x1e3/0x430 net/netlink/af_netlink.c:2543<br /> netlink_unicast_kernel net/netlink/af_netlink.c:1341 [inline]<br /> netlink_unicast+0x7ea/0x980 net/netlink/af_netlink.c:1367<br /> netlink_sendmsg+0xa3b/0xd70 net/netlink/af_netlink.c:1908<br /> sock_sendmsg_nosec net/socket.c:730 [inline]<br /> __sock_sendmsg+0x221/0x270 net/socket.c:745<br /> ____sys_sendmsg+0x525/0x7d0 net/socket.c:2584<br /> ___sys_sendmsg net/socket.c:2638 [inline]<br /> __sys_sendmsg+0x2b0/0x3a0 net/socket.c:2667<br /> do_syscall_64+0xf9/0x240<br /> entry_SYSCALL_64_after_hwframe+0x6f/0x77<br /> <br /> Freed by task 16:<br /> kasan_save_stack mm/kasan/common.c:47 [inline]<br /> kasan_save_track+0x3f/0x80 mm/kasan/common.c:68<br /> kasan_save_free_info+0x4e/0x60 mm/kasan/generic.c:640<br /> poison_slab_object+0xa6/0xe0 m<br /> ---truncated---

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> igc: avoid returning frame twice in XDP_REDIRECT<br /> <br /> When a frame can not be transmitted in XDP_REDIRECT<br /> (e.g. due to a full queue), it is necessary to free<br /> it by calling xdp_return_frame_rx_napi.<br /> <br /> However, this is the responsibility of the caller of<br /> the ndo_xdp_xmit (see for example bq_xmit_all in<br /> kernel/bpf/devmap.c) and thus calling it inside<br /> igc_xdp_xmit (which is the ndo_xdp_xmit of the igc<br /> driver) as well will lead to memory corruption.<br /> <br /> In fact, bq_xmit_all expects that it can return all<br /> frames after the last successfully transmitted one.<br /> Therefore, break for the first not transmitted frame,<br /> but do not call xdp_return_frame_rx_napi in igc_xdp_xmit.<br /> This is equally implemented in other Intel drivers<br /> such as the igb.<br /> <br /> There are two alternatives to this that were rejected:<br /> 1. Return num_frames as all the frames would have been<br /> transmitted and release them inside igc_xdp_xmit.<br /> While it might work technically, it is not what<br /> the return value is meant to represent (i.e. the<br /> number of SUCCESSFULLY transmitted packets).<br /> 2. Rework kernel/bpf/devmap.c and all drivers to<br /> support non-consecutively dropped packets.<br /> Besides being complex, it likely has a negative<br /> performance impact without a significant gain<br /> since it is anyway unlikely that the next frame<br /> can be transmitted if the previous one was dropped.<br /> <br /> The memory corruption can be reproduced with<br /> the following script which leads to a kernel panic<br /> after a few seconds. It basically generates more<br /> traffic than a i225 NIC can transmit and pushes it<br /> via XDP_REDIRECT from a virtual interface to the<br /> physical interface where frames get dropped.<br /> <br /> #!/bin/bash<br /> INTERFACE=enp4s0<br /> INTERFACE_IDX=`cat /sys/class/net/$INTERFACE/ifindex`<br /> <br /> sudo ip link add dev veth1 type veth peer name veth2<br /> sudo ip link set up $INTERFACE<br /> sudo ip link set up veth1<br /> sudo ip link set up veth2<br /> <br /> cat

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ice: fix uninitialized dplls mutex usage<br /> <br /> The pf-&gt;dplls.lock mutex is initialized too late, after its first use.<br /> Move it to the top of ice_dpll_init.<br /> Note that the "err_exit" error path destroys the mutex. And the mutex is<br /> the last thing destroyed in ice_dpll_deinit.<br /> This fixes the following warning with CONFIG_DEBUG_MUTEXES:<br /> <br /> ice 0000:10:00.0: The DDP package was successfully loaded: ICE OS Default Package version 1.3.36.0<br /> ice 0000:10:00.0: 252.048 Gb/s available PCIe bandwidth (16.0 GT/s PCIe x16 link)<br /> ice 0000:10:00.0: PTP init successful<br /> ------------[ cut here ]------------<br /> DEBUG_LOCKS_WARN_ON(lock-&gt;magic != lock)<br /> WARNING: CPU: 0 PID: 410 at kernel/locking/mutex.c:587 __mutex_lock+0x773/0xd40<br /> Modules linked in: crct10dif_pclmul crc32_pclmul crc32c_intel polyval_clmulni polyval_generic ice(+) nvme nvme_c&gt;<br /> CPU: 0 PID: 410 Comm: kworker/0:4 Not tainted 6.8.0-rc5+ #3<br /> Hardware name: HPE ProLiant DL110 Gen10 Plus/ProLiant DL110 Gen10 Plus, BIOS U56 10/19/2023<br /> Workqueue: events work_for_cpu_fn<br /> RIP: 0010:__mutex_lock+0x773/0xd40<br /> Code: c0 0f 84 1d f9 ff ff 44 8b 35 0d 9c 69 01 45 85 f6 0f 85 0d f9 ff ff 48 c7 c6 12 a2 a9 85 48 c7 c7 12 f1 a&gt;<br /> RSP: 0018:ff7eb1a3417a7ae0 EFLAGS: 00010286<br /> RAX: 0000000000000000 RBX: 0000000000000002 RCX: 0000000000000000<br /> RDX: 0000000000000002 RSI: ffffffff85ac2bff RDI: 00000000ffffffff<br /> RBP: ff7eb1a3417a7b80 R08: 0000000000000000 R09: 00000000ffffbfff<br /> R10: ff7eb1a3417a7978 R11: ff32b80f7fd2e568 R12: 0000000000000000<br /> R13: 0000000000000000 R14: 0000000000000000 R15: ff32b7f02c50e0d8<br /> FS: 0000000000000000(0000) GS:ff32b80efe800000(0000) knlGS:0000000000000000<br /> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> CR2: 000055b5852cc000 CR3: 000000003c43a004 CR4: 0000000000771ef0<br /> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000<br /> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400<br /> PKRU: 55555554<br /> Call Trace:<br /> <br /> ? __warn+0x84/0x170<br /> ? __mutex_lock+0x773/0xd40<br /> ? report_bug+0x1c7/0x1d0<br /> ? prb_read_valid+0x1b/0x30<br /> ? handle_bug+0x42/0x70<br /> ? exc_invalid_op+0x18/0x70<br /> ? asm_exc_invalid_op+0x1a/0x20<br /> ? __mutex_lock+0x773/0xd40<br /> ? rcu_is_watching+0x11/0x50<br /> ? __kmalloc_node_track_caller+0x346/0x490<br /> ? ice_dpll_lock_status_get+0x28/0x50 [ice]<br /> ? __pfx_ice_dpll_lock_status_get+0x10/0x10 [ice]<br /> ? ice_dpll_lock_status_get+0x28/0x50 [ice]<br /> ice_dpll_lock_status_get+0x28/0x50 [ice]<br /> dpll_device_get_one+0x14f/0x2e0<br /> dpll_device_event_send+0x7d/0x150<br /> dpll_device_register+0x124/0x180<br /> ice_dpll_init_dpll+0x7b/0xd0 [ice]<br /> ice_dpll_init+0x224/0xa40 [ice]<br /> ? _dev_info+0x70/0x90<br /> ice_load+0x468/0x690 [ice]<br /> ice_probe+0x75b/0xa10 [ice]<br /> ? _raw_spin_unlock_irqrestore+0x4f/0x80<br /> ? process_one_work+0x1a3/0x500<br /> local_pci_probe+0x47/0xa0<br /> work_for_cpu_fn+0x17/0x30<br /> process_one_work+0x20d/0x500<br /> worker_thread+0x1df/0x3e0<br /> ? __pfx_worker_thread+0x10/0x10<br /> kthread+0x103/0x140<br /> ? __pfx_kthread+0x10/0x10<br /> ret_from_fork+0x31/0x50<br /> ? __pfx_kthread+0x10/0x10<br /> ret_from_fork_asm+0x1b/0x30<br /> <br /> irq event stamp: 125197<br /> hardirqs last enabled at (125197): [] finish_task_switch.isra.0+0x12d/0x3d0<br /> hardirqs last disabled at (125196): [] __schedule+0xea4/0x19f0<br /> softirqs last enabled at (105334): [] napi_get_frags_check+0x1a/0x60<br /> softirqs last disabled at (105332): [] napi_get_frags_check+0x1a/0x60<br /> ---[ end trace 0000000000000000 ]---