Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc<br /> <br /> A NULL sock pointer is passed into l2cap_sock_alloc() when it is called<br /> from l2cap_sock_new_connection_cb() and the error handling paths should<br /> also be aware of it.<br /> <br /> Seemingly a more elegant solution would be to swap bt_sock_alloc() and<br /> l2cap_chan_create() calls since they are not interdependent to that moment<br /> but then l2cap_chan_create() adds the soon to be deallocated and still<br /> dummy-initialized channel to the global list accessible by many L2CAP<br /> paths. The channel would be removed from the list in short period of time<br /> but be a bit more straight-forward here and just check for NULL instead of<br /> changing the order of function calls.<br /> <br /> Found by Linux Verification Center (linuxtesting.org) with SVACE static<br /> analysis tool.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> binfmt_flat: Fix integer overflow bug on 32 bit systems<br /> <br /> Most of these sizes and counts are capped at 256MB so the math doesn&amp;#39;t<br /> result in an integer overflow. The "relocs" count needs to be checked<br /> as well. Otherwise on 32bit systems the calculation of "full_data"<br /> could be wrong.<br /> <br /> full_data = data_len + relocs * sizeof(unsigned long);

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/xe/tracing: Fix a potential TP_printk UAF<br /> <br /> The commit<br /> afd2627f727b ("tracing: Check "%s" dereference via the field and not the TP_printk format")<br /> exposes potential UAFs in the xe_bo_move trace event.<br /> <br /> Fix those by avoiding dereferencing the<br /> xe_mem_type_to_name[] array at TP_printk time.<br /> <br /> Since some code refactoring has taken place, explicit backporting may<br /> be needed for kernels older than 6.10.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm: zynqmp_dp: Fix integer overflow in zynqmp_dp_rate_get()<br /> <br /> This patch fixes a potential integer overflow in the zynqmp_dp_rate_get()<br /> <br /> The issue comes up when the expression<br /> drm_dp_bw_code_to_link_rate(dp-&gt;test.bw_code) * 10000 is evaluated using 32-bit<br /> Now the constant is a compatible 64-bit type.<br /> <br /> Resolves coverity issues: CID 1636340 and CID 1635811

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/msm/gem: prevent integer overflow in msm_ioctl_gem_submit()<br /> <br /> The "submit-&gt;cmd[i].size" and "submit-&gt;cmd[i].offset" variables are u32<br /> values that come from the user via the submit_lookup_cmds() function.<br /> This addition could lead to an integer wrapping bug so use size_add()<br /> to prevent that.<br /> <br /> Patchwork: https://patchwork.freedesktop.org/patch/624696/

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> fs/ntfs3: Mark inode as bad as soon as error detected in mi_enum_attr()<br /> <br /> Extended the `mi_enum_attr()` function interface with an additional<br /> parameter, `struct ntfs_inode *ni`, to allow marking the inode<br /> as bad as soon as an error is detected.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> NFS: Fix potential buffer overflowin nfs_sysfs_link_rpc_client()<br /> <br /> name is char[64] where the size of clnt-&gt;cl_program-&gt;name remains<br /> unknown. Invoking strcat() directly will also lead to potential buffer<br /> overflow. Change them to strscpy() and strncat() to fix potential<br /> issues.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> firmware: qcom: scm: smc: Handle missing SCM device<br /> <br /> Commit ca61d6836e6f ("firmware: qcom: scm: fix a NULL-pointer<br /> dereference") makes it explicit that qcom_scm_get_tzmem_pool() can<br /> return NULL, therefore its users should handle this.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> scsi: ufs: bsg: Set bsg_queue to NULL after removal<br /> <br /> Currently, this does not cause any issues, but I believe it is necessary to<br /> set bsg_queue to NULL after removing it to prevent potential use-after-free<br /> (UAF) access.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> media: vidtv: Fix a null-ptr-deref in vidtv_mux_stop_thread<br /> <br /> syzbot report a null-ptr-deref in vidtv_mux_stop_thread. [1]<br /> <br /> If dvb-&gt;mux is not initialized successfully by vidtv_mux_init() in the<br /> vidtv_start_streaming(), it will trigger null pointer dereference about mux<br /> in vidtv_mux_stop_thread().<br /> <br /> Adjust the timing of streaming initialization and check it before<br /> stopping it.<br /> <br /> [1]<br /> KASAN: null-ptr-deref in range [0x0000000000000128-0x000000000000012f]<br /> CPU: 0 UID: 0 PID: 5842 Comm: syz-executor248 Not tainted 6.13.0-rc4-syzkaller-00012-g9b2ffa6148b1 #0<br /> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024<br /> RIP: 0010:vidtv_mux_stop_thread+0x26/0x80 drivers/media/test-drivers/vidtv/vidtv_mux.c:471<br /> Code: 90 90 90 90 66 0f 1f 00 55 53 48 89 fb e8 82 2e c8 f9 48 8d bb 28 01 00 00 48 b8 00 00 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 b6 04 02 84 c0 74 02 7e 3b 0f b6 ab 28 01 00 00 31 ff 89 ee e8<br /> RSP: 0018:ffffc90003f2faa8 EFLAGS: 00010202<br /> RAX: dffffc0000000000 RBX: 0000000000000000 RCX: ffffffff87cfb125<br /> RDX: 0000000000000025 RSI: ffffffff87d120ce RDI: 0000000000000128<br /> RBP: ffff888029b8d220 R08: 0000000000000005 R09: 0000000000000000<br /> R10: 0000000000000000 R11: 0000000000000003 R12: ffff888029b8d188<br /> R13: ffffffff8f590aa0 R14: ffffc9000581c5c8 R15: ffff888029a17710<br /> FS: 00007f7eef5156c0(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000<br /> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> CR2: 00007f7eef5e635c CR3: 0000000076ca6000 CR4: 00000000003526f0<br /> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000<br /> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400<br /> Call Trace:<br /> <br /> vidtv_stop_streaming drivers/media/test-drivers/vidtv/vidtv_bridge.c:209 [inline]<br /> vidtv_stop_feed+0x151/0x250 drivers/media/test-drivers/vidtv/vidtv_bridge.c:252<br /> dmx_section_feed_stop_filtering+0x90/0x160 drivers/media/dvb-core/dvb_demux.c:1000<br /> dvb_dmxdev_feed_stop.isra.0+0x1ee/0x270 drivers/media/dvb-core/dmxdev.c:486<br /> dvb_dmxdev_filter_stop+0x22a/0x3a0 drivers/media/dvb-core/dmxdev.c:559<br /> dvb_dmxdev_filter_free drivers/media/dvb-core/dmxdev.c:840 [inline]<br /> dvb_demux_release+0x92/0x550 drivers/media/dvb-core/dmxdev.c:1246<br /> __fput+0x3f8/0xb60 fs/file_table.c:450<br /> task_work_run+0x14e/0x250 kernel/task_work.c:239<br /> get_signal+0x1d3/0x2610 kernel/signal.c:2790<br /> arch_do_signal_or_restart+0x90/0x7e0 arch/x86/kernel/signal.c:337<br /> exit_to_user_mode_loop kernel/entry/common.c:111 [inline]<br /> exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline]<br /> __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]<br /> syscall_exit_to_user_mode+0x150/0x2a0 kernel/entry/common.c:218<br /> do_syscall_64+0xda/0x250 arch/x86/entry/common.c:89<br /> entry_SYSCALL_64_after_hwframe+0x77/0x7f

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: rtw89: fix race between cancel_hw_scan and hw_scan completion<br /> <br /> The rtwdev-&gt;scanning flag isn&amp;#39;t protected by mutex originally, so<br /> cancel_hw_scan can pass the condition, but suddenly hw_scan completion<br /> unset the flag and calls ieee80211_scan_completed() that will free<br /> local-&gt;hw_scan_req. Then, cancel_hw_scan raises null-ptr-deref and<br /> use-after-free. Fix it by moving the check condition to where<br /> protected by mutex.<br /> <br /> KASAN: null-ptr-deref in range [0x0000000000000088-0x000000000000008f]<br /> CPU: 2 PID: 6922 Comm: kworker/2:2 Tainted: G OE<br /> Hardware name: LENOVO 2356AD1/2356AD1, BIOS G7ETB6WW (2.76 ) 09/10/2019<br /> Workqueue: events cfg80211_conn_work [cfg80211]<br /> RIP: 0010:rtw89_fw_h2c_scan_offload_be+0xc33/0x13c3 [rtw89_core]<br /> Code: 00 45 89 6c 24 1c 0f 85 23 01 00 00 48 8b 85 20 ff ff ff 48 8d<br /> RSP: 0018:ffff88811fd9f068 EFLAGS: 00010206<br /> RAX: dffffc0000000000 RBX: ffff88811fd9f258 RCX: 0000000000000001<br /> RDX: 0000000000000011 RSI: 0000000000000001 RDI: 0000000000000089<br /> RBP: ffff88811fd9f170 R08: 0000000000000000 R09: 0000000000000000<br /> R10: ffff88811fd9f108 R11: 0000000000000000 R12: ffff88810e47f960<br /> R13: 0000000000000000 R14: 000000000000ffff R15: 0000000000000000<br /> FS: 0000000000000000(0000) GS:ffff8881d6f00000(0000) knlGS:0000000000000000<br /> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> CR2: 00007531dfca55b0 CR3: 00000001be296004 CR4: 00000000001706e0<br /> Call Trace:<br /> <br /> ? show_regs+0x61/0x73<br /> ? __die_body+0x20/0x73<br /> ? die_addr+0x4f/0x7b<br /> ? exc_general_protection+0x191/0x1db<br /> ? asm_exc_general_protection+0x27/0x30<br /> ? rtw89_fw_h2c_scan_offload_be+0xc33/0x13c3 [rtw89_core]<br /> ? rtw89_fw_h2c_scan_offload_be+0x458/0x13c3 [rtw89_core]<br /> ? __pfx_rtw89_fw_h2c_scan_offload_be+0x10/0x10 [rtw89_core]<br /> ? do_raw_spin_lock+0x75/0xdb<br /> ? __pfx_do_raw_spin_lock+0x10/0x10<br /> rtw89_hw_scan_offload+0xb5e/0xbf7 [rtw89_core]<br /> ? _raw_spin_unlock+0xe/0x24<br /> ? __mutex_lock.constprop.0+0x40c/0x471<br /> ? __pfx_rtw89_hw_scan_offload+0x10/0x10 [rtw89_core]<br /> ? __mutex_lock_slowpath+0x13/0x1f<br /> ? mutex_lock+0xa2/0xdc<br /> ? __pfx_mutex_lock+0x10/0x10<br /> rtw89_hw_scan_abort+0x58/0xb7 [rtw89_core]<br /> rtw89_ops_cancel_hw_scan+0x120/0x13b [rtw89_core]<br /> ieee80211_scan_cancel+0x468/0x4d0 [mac80211]<br /> ieee80211_prep_connection+0x858/0x899 [mac80211]<br /> ieee80211_mgd_auth+0xbea/0xdde [mac80211]<br /> ? __pfx_ieee80211_mgd_auth+0x10/0x10 [mac80211]<br /> ? cfg80211_find_elem+0x15/0x29 [cfg80211]<br /> ? is_bss+0x1b7/0x1d7 [cfg80211]<br /> ieee80211_auth+0x18/0x27 [mac80211]<br /> cfg80211_mlme_auth+0x3bb/0x3e7 [cfg80211]<br /> cfg80211_conn_do_work+0x410/0xb81 [cfg80211]<br /> ? __pfx_cfg80211_conn_do_work+0x10/0x10 [cfg80211]<br /> ? __kasan_check_read+0x11/0x1f<br /> ? psi_group_change+0x8bc/0x944<br /> ? __kasan_check_write+0x14/0x22<br /> ? mutex_lock+0x8e/0xdc<br /> ? __pfx_mutex_lock+0x10/0x10<br /> ? __pfx___radix_tree_lookup+0x10/0x10<br /> cfg80211_conn_work+0x245/0x34d [cfg80211]<br /> ? __pfx_cfg80211_conn_work+0x10/0x10 [cfg80211]<br /> ? update_cfs_rq_load_avg+0x3bc/0x3d7<br /> ? sched_clock_noinstr+0x9/0x1a<br /> ? sched_clock+0x10/0x24<br /> ? sched_clock_cpu+0x7e/0x42e<br /> ? newidle_balance+0x796/0x937<br /> ? __pfx_sched_clock_cpu+0x10/0x10<br /> ? __pfx_newidle_balance+0x10/0x10<br /> ? __kasan_check_read+0x11/0x1f<br /> ? psi_group_change+0x8bc/0x944<br /> ? _raw_spin_unlock+0xe/0x24<br /> ? raw_spin_rq_unlock+0x47/0x54<br /> ? raw_spin_rq_unlock_irq+0x9/0x1f<br /> ? finish_task_switch.isra.0+0x347/0x586<br /> ? __schedule+0x27bf/0x2892<br /> ? mutex_unlock+0x80/0xd0<br /> ? do_raw_spin_lock+0x75/0xdb<br /> ? __pfx___schedule+0x10/0x10<br /> process_scheduled_works+0x58c/0x821<br /> worker_thread+0x4c7/0x586<br /> ? __kasan_check_read+0x11/0x1f<br /> kthread+0x285/0x294<br /> ? __pfx_worker_thread+0x10/0x10<br /> ? __pfx_kthread+0x10/0x10<br /> ret_from_fork+0x29/0x6f<br /> ? __pfx_kthread+0x10/0x10<br /> ret_from_fork_asm+0x1b/0x30<br />

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: rtw89: avoid to init mgnt_entry list twice when WoWLAN failed<br /> <br /> If WoWLAN failed in resume flow, the rtw89_ops_add_interface() triggered<br /> without removing the interface first. Then the mgnt_entry list init again,<br /> causing the list_empty() check in rtw89_chanctx_ops_assign_vif()<br /> useless, and list_add_tail() again. Therefore, we have added a check to<br /> prevent double adding of the list.<br /> <br /> rtw89_8852ce 0000:01:00.0: failed to check wow status disabled<br /> rtw89_8852ce 0000:01:00.0: wow: failed to check disable fw ready<br /> rtw89_8852ce 0000:01:00.0: wow: failed to swap to normal fw<br /> rtw89_8852ce 0000:01:00.0: failed to disable wow<br /> rtw89_8852ce 0000:01:00.0: failed to resume for wow -110<br /> rtw89_8852ce 0000:01:00.0: MAC has already powered on<br /> i2c_hid_acpi i2c-ILTK0001:00: PM: acpi_subsys_resume+0x0/0x60 returned 0 after 284705 usecs<br /> list_add corruption. prev-&gt;next should be next (ffff9d9719d82228), but was ffff9d9719f96030. (prev=ffff9d9719f96030).<br /> ------------[ cut here ]------------<br /> kernel BUG at lib/list_debug.c:34!<br /> invalid opcode: 0000 [#1] PREEMPT SMP NOPTI<br /> CPU: 2 PID: 6918 Comm: kworker/u8:19 Tainted: G U O<br /> Hardware name: Google Anraggar/Anraggar, BIOS Google_Anraggar.15217.514.0 03/25/2024<br /> Workqueue: events_unbound async_run_entry_fn<br /> RIP: 0010:__list_add_valid_or_report+0x9f/0xb0<br /> Code: e8 56 89 ff ff 0f 0b 48 c7 c7 3e fc e0 96 48 89 c6 e8 45 89 ff ...<br /> RSP: 0018:ffffa51b42bbbaf0 EFLAGS: 00010246<br /> RAX: 0000000000000075 RBX: ffff9d9719d82ab0 RCX: 13acb86e047a4400<br /> RDX: 3fffffffffffffff RSI: 0000000000000000 RDI: 00000000ffffdfff<br /> RBP: ffffa51b42bbbb28 R08: ffffffff9768e250 R09: 0000000000001fff<br /> R10: ffffffff9765e250 R11: 0000000000005ffd R12: ffff9d9719f95c40<br /> R13: ffff9d9719f95be8 R14: ffff9d97081bfd78 R15: ffff9d9719d82060<br /> FS: 0000000000000000(0000) GS:ffff9d9a6fb00000(0000) knlGS:0000000000000000<br /> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> CR2: 00007e7d029a4060 CR3: 0000000345e38000 CR4: 0000000000750ee0<br /> PKRU: 55555554<br /> Call Trace:<br /> <br /> ? __die_body+0x68/0xb0<br /> ? die+0xaa/0xd0<br /> ? do_trap+0x9f/0x170<br /> ? __list_add_valid_or_report+0x9f/0xb0<br /> ? __list_add_valid_or_report+0x9f/0xb0<br /> ? handle_invalid_op+0x69/0x90<br /> ? __list_add_valid_or_report+0x9f/0xb0<br /> ? exc_invalid_op+0x3c/0x50<br /> ? asm_exc_invalid_op+0x16/0x20<br /> ? __list_add_valid_or_report+0x9f/0xb0<br /> rtw89_chanctx_ops_assign_vif+0x1f9/0x210 [rtw89_core cbb375c44bf28564ce479002bff66617a25d9ac1]<br /> ? __mutex_unlock_slowpath+0xa0/0xf0<br /> rtw89_ops_assign_vif_chanctx+0x4b/0x90 [rtw89_core cbb375c44bf28564ce479002bff66617a25d9ac1]<br /> drv_assign_vif_chanctx+0xa7/0x1f0 [mac80211 6efaad16237edaaea0868b132d4f93ecf918a8b6]<br /> ieee80211_reconfig+0x9cb/0x17b0 [mac80211 6efaad16237edaaea0868b132d4f93ecf918a8b6]<br /> ? __pfx_wiphy_resume+0x10/0x10 [cfg80211 572d03acaaa933fe38251be7fce3b3675284b8ed]<br /> ? dev_printk_emit+0x51/0x70<br /> ? _dev_info+0x6e/0x90<br /> wiphy_resume+0x89/0x180 [cfg80211 572d03acaaa933fe38251be7fce3b3675284b8ed]<br /> ? __pfx_wiphy_resume+0x10/0x10 [cfg80211 572d03acaaa933fe38251be7fce3b3675284b8ed]<br /> dpm_run_callback+0x37/0x1e0<br /> device_resume+0x26d/0x4b0<br /> ? __pfx_dpm_watchdog_handler+0x10/0x10<br /> async_resume+0x1d/0x30<br /> async_run_entry_fn+0x29/0xd0<br /> worker_thread+0x397/0x970<br /> kthread+0xed/0x110<br /> ? __pfx_worker_thread+0x10/0x10<br /> ? __pfx_kthread+0x10/0x10<br /> ret_from_fork+0x38/0x50<br /> ? __pfx_kthread+0x10/0x10<br /> ret_from_fork_asm+0x1b/0x30<br />