Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> fs/ntfs3: Add null pointer check to attr_load_runs_vcn<br /> <br /> Some metadata files are handled before MFT. This adds a null pointer<br /> check for some corner cases that could lead to NPD while reading these<br /> metadata files for a malformed NTFS image.<br /> <br /> [ 240.190827] BUG: kernel NULL pointer dereference, address: 0000000000000158<br /> [ 240.191583] #PF: supervisor read access in kernel mode<br /> [ 240.191956] #PF: error_code(0x0000) - not-present page<br /> [ 240.192391] PGD 0 P4D 0<br /> [ 240.192897] Oops: 0000 [#1] PREEMPT SMP KASAN NOPTI<br /> [ 240.193805] CPU: 0 PID: 242 Comm: mount Tainted: G B 5.19.0+ #17<br /> [ 240.194477] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014<br /> [ 240.195152] RIP: 0010:ni_find_attr+0xae/0x300<br /> [ 240.195679] Code: c8 48 c7 45 88 c0 4e 5e 86 c7 00 f1 f1 f1 f1 c7 40 04 00 f3 f3 f3 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 e8 e2 d9f<br /> [ 240.196642] RSP: 0018:ffff88800812f690 EFLAGS: 00000286<br /> [ 240.197019] RAX: 0000000000000001 RBX: 0000000000000000 RCX: ffffffff85ef037a<br /> [ 240.197523] RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffffffff88e95f60<br /> [ 240.197877] RBP: ffff88800812f738 R08: 0000000000000001 R09: fffffbfff11d2bed<br /> [ 240.198292] R10: ffffffff88e95f67 R11: fffffbfff11d2bec R12: 0000000000000000<br /> [ 240.198647] R13: 0000000000000080 R14: 0000000000000000 R15: 0000000000000000<br /> [ 240.199410] FS: 00007f233c33be40(0000) GS:ffff888058200000(0000) knlGS:0000000000000000<br /> [ 240.199895] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> [ 240.200314] CR2: 0000000000000158 CR3: 0000000004d32000 CR4: 00000000000006f0<br /> [ 240.200839] Call Trace:<br /> [ 240.201104] <br /> [ 240.201502] ? ni_load_mi+0x80/0x80<br /> [ 240.202297] ? ___slab_alloc+0x465/0x830<br /> [ 240.202614] attr_load_runs_vcn+0x8c/0x1a0<br /> [ 240.202886] ? __kasan_slab_alloc+0x32/0x90<br /> [ 240.203157] ? attr_data_write_resident+0x250/0x250<br /> [ 240.203543] mi_read+0x133/0x2c0<br /> [ 240.203785] mi_get+0x70/0x140<br /> [ 240.204012] ni_load_mi_ex+0xfa/0x190<br /> [ 240.204346] ? ni_std5+0x90/0x90<br /> [ 240.204588] ? __kasan_kmalloc+0x88/0xb0<br /> [ 240.204859] ni_enum_attr_ex+0xf1/0x1c0<br /> [ 240.205107] ? ni_fname_type.part.0+0xd0/0xd0<br /> [ 240.205600] ? ntfs_load_attr_list+0xbe/0x300<br /> [ 240.205864] ? ntfs_cmp_names_cpu+0x125/0x180<br /> [ 240.206157] ntfs_iget5+0x56c/0x1870<br /> [ 240.206510] ? ntfs_get_block_bmap+0x70/0x70<br /> [ 240.206776] ? __kasan_kmalloc+0x88/0xb0<br /> [ 240.207030] ? set_blocksize+0x95/0x150<br /> [ 240.207545] ntfs_fill_super+0xb8f/0x1e20<br /> [ 240.207839] ? put_ntfs+0x1d0/0x1d0<br /> [ 240.208069] ? vsprintf+0x20/0x20<br /> [ 240.208467] ? mutex_unlock+0x81/0xd0<br /> [ 240.208846] ? set_blocksize+0x95/0x150<br /> [ 240.209221] get_tree_bdev+0x232/0x370<br /> [ 240.209804] ? put_ntfs+0x1d0/0x1d0<br /> [ 240.210519] ntfs_fs_get_tree+0x15/0x20<br /> [ 240.210991] vfs_get_tree+0x4c/0x130<br /> [ 240.211455] path_mount+0x645/0xfd0<br /> [ 240.211806] ? putname+0x80/0xa0<br /> [ 240.212112] ? finish_automount+0x2e0/0x2e0<br /> [ 240.212559] ? kmem_cache_free+0x110/0x390<br /> [ 240.212906] ? putname+0x80/0xa0<br /> [ 240.213329] do_mount+0xd6/0xf0<br /> [ 240.213829] ? path_mount+0xfd0/0xfd0<br /> [ 240.214246] ? __kasan_check_write+0x14/0x20<br /> [ 240.214774] __x64_sys_mount+0xca/0x110<br /> [ 240.215080] do_syscall_64+0x3b/0x90<br /> [ 240.215442] entry_SYSCALL_64_after_hwframe+0x63/0xcd<br /> [ 240.215811] RIP: 0033:0x7f233b4e948a<br /> [ 240.216104] Code: 48 8b 0d 11 fa 2a 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 a5 00 00 008<br /> [ 240.217615] RSP: 002b:00007fff02211ec8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5<br /> [ 240.218718] RAX: ffffffffffffffda RBX: 0000561cdc35b060 RCX: 00007f233b4e948a<br /> [ 240.219556] RDX: 0000561cdc35b260 RSI: 0000561cdc35b2e0 RDI: 0000561cdc363af0<br /> [ 240.219975] RBP: 0000000000000000 R08: 0000561cdc35b280 R09: 0000000000000020<br /> [ 240.220403] R10: 00000000c0ed0000 R11: 0000000000000202 R12: 0000561cdc363af0<br /> [ 240.220803] R13: 000<br /> ---truncated---

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wwan_hwsim: fix possible memory leak in wwan_hwsim_dev_new()<br /> <br /> Inject fault while probing module, if device_register() fails,<br /> but the refcount of kobject is not decreased to 0, the name<br /> allocated in dev_set_name() is leaked. Fix this by calling<br /> put_device(), so that name can be freed in callback function<br /> kobject_cleanup().<br /> <br /> unreferenced object 0xffff88810152ad20 (size 8):<br /> comm "modprobe", pid 252, jiffies 4294849206 (age 22.713s)<br /> hex dump (first 8 bytes):<br /> 68 77 73 69 6d 30 00 ff hwsim0..<br /> backtrace:<br /> [] __kmalloc_node_track_caller+0x44/0x1b0<br /> [] kvasprintf+0xb5/0x140<br /> [] kvasprintf_const+0x55/0x180<br /> [] kobject_set_name_vargs+0x56/0x150<br /> [] dev_set_name+0xab/0xe0

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ACPI: processor: idle: Check acpi_fetch_acpi_dev() return value<br /> <br /> The return value of acpi_fetch_acpi_dev() could be NULL, which would<br /> cause a NULL pointer dereference to occur in acpi_device_hid().<br /> <br /> [ rjw: Subject and changelog edits, added empty line after if () ]

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ASoC: Intel: avs: Fix potential RX buffer overflow<br /> <br /> If an event caused firmware to return invalid RX size for<br /> LARGE_CONFIG_GET, memcpy_fromio() could end up copying too many bytes.<br /> Fix by utilizing min_t().

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> jbd2: fix potential use-after-free in jbd2_fc_wait_bufs<br /> <br /> In &amp;#39;jbd2_fc_wait_bufs&amp;#39; use &amp;#39;bh&amp;#39; after put buffer head reference count<br /> which may lead to use-after-free.<br /> So judge buffer if uptodate before put buffer head reference count.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> net: do not sense pfmemalloc status in skb_append_pagefrags()<br /> <br /> skb_append_pagefrags() is used by af_unix and udp sendpage()<br /> implementation so far.<br /> <br /> In commit 326140063946 ("tcp: TX zerocopy should not sense<br /> pfmemalloc status") we explained why we should not sense<br /> pfmemalloc status for pages owned by user space.<br /> <br /> We should also use skb_fill_page_desc_noacc()<br /> in skb_append_pagefrags() to avoid following KCSAN report:<br /> <br /> BUG: KCSAN: data-race in lru_add_fn / skb_append_pagefrags<br /> <br /> write to 0xffffea00058fc1c8 of 8 bytes by task 17319 on cpu 0:<br /> __list_add include/linux/list.h:73 [inline]<br /> list_add include/linux/list.h:88 [inline]<br /> lruvec_add_folio include/linux/mm_inline.h:323 [inline]<br /> lru_add_fn+0x327/0x410 mm/swap.c:228<br /> folio_batch_move_lru+0x1e1/0x2a0 mm/swap.c:246<br /> lru_add_drain_cpu+0x73/0x250 mm/swap.c:669<br /> lru_add_drain+0x21/0x60 mm/swap.c:773<br /> free_pages_and_swap_cache+0x16/0x70 mm/swap_state.c:311<br /> tlb_batch_pages_flush mm/mmu_gather.c:59 [inline]<br /> tlb_flush_mmu_free mm/mmu_gather.c:256 [inline]<br /> tlb_flush_mmu+0x5b2/0x640 mm/mmu_gather.c:263<br /> tlb_finish_mmu+0x86/0x100 mm/mmu_gather.c:363<br /> exit_mmap+0x190/0x4d0 mm/mmap.c:3098<br /> __mmput+0x27/0x1b0 kernel/fork.c:1185<br /> mmput+0x3d/0x50 kernel/fork.c:1207<br /> copy_process+0x19fc/0x2100 kernel/fork.c:2518<br /> kernel_clone+0x166/0x550 kernel/fork.c:2671<br /> __do_sys_clone kernel/fork.c:2812 [inline]<br /> __se_sys_clone kernel/fork.c:2796 [inline]<br /> __x64_sys_clone+0xc3/0xf0 kernel/fork.c:2796<br /> do_syscall_x64 arch/x86/entry/common.c:50 [inline]<br /> do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80<br /> entry_SYSCALL_64_after_hwframe+0x63/0xcd<br /> <br /> read to 0xffffea00058fc1c8 of 8 bytes by task 17325 on cpu 1:<br /> page_is_pfmemalloc include/linux/mm.h:1817 [inline]<br /> __skb_fill_page_desc include/linux/skbuff.h:2432 [inline]<br /> skb_fill_page_desc include/linux/skbuff.h:2453 [inline]<br /> skb_append_pagefrags+0x210/0x600 net/core/skbuff.c:3974<br /> unix_stream_sendpage+0x45e/0x990 net/unix/af_unix.c:2338<br /> kernel_sendpage+0x184/0x300 net/socket.c:3561<br /> sock_sendpage+0x5a/0x70 net/socket.c:1054<br /> pipe_to_sendpage+0x128/0x160 fs/splice.c:361<br /> splice_from_pipe_feed fs/splice.c:415 [inline]<br /> __splice_from_pipe+0x222/0x4d0 fs/splice.c:559<br /> splice_from_pipe fs/splice.c:594 [inline]<br /> generic_splice_sendpage+0x89/0xc0 fs/splice.c:743<br /> do_splice_from fs/splice.c:764 [inline]<br /> direct_splice_actor+0x80/0xa0 fs/splice.c:931<br /> splice_direct_to_actor+0x305/0x620 fs/splice.c:886<br /> do_splice_direct+0xfb/0x180 fs/splice.c:974<br /> do_sendfile+0x3bf/0x910 fs/read_write.c:1255<br /> __do_sys_sendfile64 fs/read_write.c:1323 [inline]<br /> __se_sys_sendfile64 fs/read_write.c:1309 [inline]<br /> __x64_sys_sendfile64+0x10c/0x150 fs/read_write.c:1309<br /> do_syscall_x64 arch/x86/entry/common.c:50 [inline]<br /> do_syscall_64+0x2b/0x70 arch/x86/entry/common.c:80<br /> entry_SYSCALL_64_after_hwframe+0x63/0xcd<br /> <br /> value changed: 0x0000000000000000 -&gt; 0xffffea00058fc188<br /> <br /> Reported by Kernel Concurrency Sanitizer on:<br /> CPU: 1 PID: 17325 Comm: syz-executor.0 Not tainted 6.1.0-rc1-syzkaller-00158-g440b7895c990-dirty #0<br /> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> rtc: msc313: Fix function prototype mismatch in msc313_rtc_probe()<br /> <br /> With clang&amp;#39;s kernel control flow integrity (kCFI, CONFIG_CFI_CLANG),<br /> indirect call targets are validated against the expected function<br /> pointer prototype to make sure the call target is valid to help mitigate<br /> ROP attacks. If they are not identical, there is a failure at run time,<br /> which manifests as either a kernel panic or thread getting killed.<br /> <br /> msc313_rtc_probe() was passing clk_disable_unprepare() directly, which<br /> did not have matching prototypes for devm_add_action_or_reset()&amp;#39;s<br /> callback argument. Refactor to use devm_clk_get_enabled() instead.<br /> <br /> This was found as a result of Clang&amp;#39;s new -Wcast-function-type-strict<br /> flag, which is more sensitive than the simpler -Wcast-function-type,<br /> which only checks for type width mismatches.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: brcmfmac: fix potential memory leak in brcmf_netdev_start_xmit()<br /> <br /> The brcmf_netdev_start_xmit() returns NETDEV_TX_OK without freeing skb<br /> in case of pskb_expand_head() fails, add dev_kfree_skb() to fix it.<br /> Compile tested only.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> mtd: maps: pxa2xx-flash: fix memory leak in probe<br /> <br /> Free &amp;#39;info&amp;#39; upon remapping error to avoid a memory leak.<br /> <br /> [: Reword the commit log]

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> media: airspy: fix memory leak in airspy probe<br /> <br /> The commit ca9dc8d06ab6 ("media: airspy: respect the DMA coherency<br /> rules") moves variable buf from stack to heap, however, it only frees<br /> buf in the error handling code, missing deallocation in the success<br /> path.<br /> <br /> Fix this by freeing buf in the success path since this variable does not<br /> have any references in other code.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ACPI: tables: FPDT: Don&amp;#39;t call acpi_os_map_memory() on invalid phys address<br /> <br /> On a Packard Bell Dot SC (Intel Atom N2600 model) there is a FPDT table<br /> which contains invalid physical addresses, with high bits set which fall<br /> outside the range of the CPU-s supported physical address range.<br /> <br /> Calling acpi_os_map_memory() on such an invalid phys address leads to<br /> the below WARN_ON in ioremap triggering resulting in an oops/stacktrace.<br /> <br /> Add code to verify the physical address before calling acpi_os_map_memory()<br /> to fix / avoid the oops.<br /> <br /> [ 1.226900] ioremap: invalid physical address 3001000000000000<br /> [ 1.226949] ------------[ cut here ]------------<br /> [ 1.226962] WARNING: CPU: 1 PID: 1 at arch/x86/mm/ioremap.c:200 __ioremap_caller.cold+0x43/0x5f<br /> [ 1.226996] Modules linked in:<br /> [ 1.227016] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 6.0.0-rc3+ #490<br /> [ 1.227029] Hardware name: Packard Bell dot s/SJE01_CT, BIOS V1.10 07/23/2013<br /> [ 1.227038] RIP: 0010:__ioremap_caller.cold+0x43/0x5f<br /> [ 1.227054] Code: 96 00 00 e9 f8 af 24 ff 89 c6 48 c7 c7 d8 0c 84 99 e8 6a 96 00 00 e9 76 af 24 ff 48 89 fe 48 c7 c7 a8 0c 84 99 e8 56 96 00 00 0b e9 60 af 24 ff 48 8b 34 24 48 c7 c7 40 0d 84 99 e8 3f 96 00<br /> [ 1.227067] RSP: 0000:ffffb18c40033d60 EFLAGS: 00010286<br /> [ 1.227084] RAX: 0000000000000032 RBX: 3001000000000000 RCX: 0000000000000000<br /> [ 1.227095] RDX: 0000000000000001 RSI: 00000000ffffdfff RDI: 00000000ffffffff<br /> [ 1.227105] RBP: 3001000000000000 R08: 0000000000000000 R09: ffffb18c40033c18<br /> [ 1.227115] R10: 0000000000000003 R11: ffffffff99d62fe8 R12: 0000000000000008<br /> [ 1.227124] R13: 0003001000000000 R14: 0000000000001000 R15: 3001000000000000<br /> [ 1.227135] FS: 0000000000000000(0000) GS:ffff913a3c080000(0000) knlGS:0000000000000000<br /> [ 1.227146] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> [ 1.227156] CR2: 0000000000000000 CR3: 0000000018c26000 CR4: 00000000000006e0<br /> [ 1.227167] Call Trace:<br /> [ 1.227176] <br /> [ 1.227185] ? acpi_os_map_iomem+0x1c9/0x1e0<br /> [ 1.227215] ? kmem_cache_alloc_trace+0x187/0x370<br /> [ 1.227254] acpi_os_map_iomem+0x1c9/0x1e0<br /> [ 1.227288] acpi_init_fpdt+0xa8/0x253<br /> [ 1.227308] ? acpi_debugfs_init+0x1f/0x1f<br /> [ 1.227339] do_one_initcall+0x5a/0x300<br /> [ 1.227406] ? rcu_read_lock_sched_held+0x3f/0x80<br /> [ 1.227442] kernel_init_freeable+0x28b/0x2cc<br /> [ 1.227512] ? rest_init+0x170/0x170<br /> [ 1.227538] kernel_init+0x16/0x140<br /> [ 1.227552] ret_from_fork+0x1f/0x30<br /> [ 1.227639] <br /> [ 1.227647] irq event stamp: 186819<br /> [ 1.227656] hardirqs last enabled at (186825): [] __up_console_sem+0x5e/0x70<br /> [ 1.227672] hardirqs last disabled at (186830): [] __up_console_sem+0x43/0x70<br /> [ 1.227686] softirqs last enabled at (186576): [] __irq_exit_rcu+0xed/0x160<br /> [ 1.227701] softirqs last disabled at (186569): [] __irq_exit_rcu+0xed/0x160<br /> [ 1.227715] ---[ end trace 0000000000000000 ]---

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> coresight: trbe: remove cpuhp instance node before remove cpuhp state<br /> <br /> cpuhp_state_add_instance() and cpuhp_state_remove_instance() should<br /> be used in pairs. Or there will lead to the warn on<br /> cpuhp_remove_multi_state() since the cpuhp_step list is not empty.<br /> <br /> The following is the error log with &amp;#39;rmmod coresight-trbe&amp;#39;:<br /> Error: Removing state 215 which has instances left.<br /> Call trace:<br /> __cpuhp_remove_state_cpuslocked+0x144/0x160<br /> __cpuhp_remove_state+0xac/0x100<br /> arm_trbe_device_remove+0x2c/0x60 [coresight_trbe]<br /> platform_remove+0x34/0x70<br /> device_remove+0x54/0x90<br /> device_release_driver_internal+0x1e4/0x250<br /> driver_detach+0x5c/0xb0<br /> bus_remove_driver+0x64/0xc0<br /> driver_unregister+0x3c/0x70<br /> platform_driver_unregister+0x20/0x30<br /> arm_trbe_exit+0x1c/0x658 [coresight_trbe]<br /> __arm64_sys_delete_module+0x1ac/0x24c<br /> invoke_syscall+0x50/0x120<br /> el0_svc_common.constprop.0+0x58/0x1a0<br /> do_el0_svc+0x38/0xd0<br /> el0_svc+0x2c/0xc0<br /> el0t_64_sync_handler+0x1ac/0x1b0<br /> el0t_64_sync+0x19c/0x1a0<br /> ---[ end trace 0000000000000000 ]---