Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ASoC: SOF: Intel: Fix NULL ptr dereference when ENOMEM<br /> <br /> Do not call snd_dma_free_pages() when snd_dma_alloc_pages() returns<br /> -ENOMEM because it leads to a NULL pointer dereference bug.<br /> <br /> The dmesg says:<br /> <br /> [ T1387] sof-audio-pci-intel-tgl 0000:00:1f.3: error: memory alloc failed: -12<br /> [ T1387] BUG: kernel NULL pointer dereference, address: 0000000000000000<br /> [ T1387] #PF: supervisor read access in kernel mode<br /> [ T1387] #PF: error_code(0x0000) - not-present page<br /> [ T1387] PGD 0 P4D 0<br /> [ T1387] Oops: 0000 [#1] PREEMPT SMP NOPTI<br /> [ T1387] CPU: 6 PID: 1387 Comm: alsa-sink-HDA A Tainted: G W 5.17.0-rc4-superb-owl-00055-g80d47f5de5e3<br /> [ T1387] Hardware name: HP HP Laptop 14s-dq2xxx/87FD, BIOS F.15 09/15/2021<br /> [ T1387] RIP: 0010:dma_free_noncontiguous+0x37/0x80<br /> [ T1387] Code: [... snip ...]<br /> [ T1387] RSP: 0000:ffffc90002b87770 EFLAGS: 00010246<br /> [ T1387] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000<br /> [ T1387] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff888101db30d0<br /> [ T1387] RBP: 00000000fffffff4 R08: 0000000000000000 R09: 0000000000000000<br /> [ T1387] R10: 0000000000000000 R11: ffffc90002b874d0 R12: 0000000000000001<br /> [ T1387] R13: 0000000000058000 R14: ffff888105260c68 R15: ffff888105260828<br /> [ T1387] FS: 00007f42e2ffd640(0000) GS:ffff888466b80000(0000) knlGS:0000000000000000<br /> [ T1387] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> [ T1387] CR2: 0000000000000000 CR3: 000000014acf0003 CR4: 0000000000770ee0<br /> [ T1387] PKRU: 55555554<br /> [ T1387] Call Trace:<br /> [ T1387] <br /> [ T1387] cl_stream_prepare+0x10a/0x120 [snd_sof_intel_hda_common 146addf995b9279ae7f509621078cccbe4f875e1]<br /> [... snip ...]<br /> [ T1387]

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> can: isotp: sanitize CAN ID checks in isotp_bind()<br /> <br /> Syzbot created an environment that lead to a state machine status that<br /> can not be reached with a compliant CAN ID address configuration.<br /> The provided address information consisted of CAN ID 0x6000001 and 0xC28001<br /> which both boil down to 11 bit CAN IDs 0x001 in sending and receiving.<br /> <br /> Sanitize the SFF/EFF CAN ID values before performing the address checks.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> dm: fix use-after-free in dm_cleanup_zoned_dev()<br /> <br /> dm_cleanup_zoned_dev() uses queue, so it must be called<br /> before blk_cleanup_disk() starts its killing:<br /> <br /> blk_cleanup_disk-&gt;blk_cleanup_queue()-&gt;kobject_put()-&gt;blk_release_queue()-&gt;<br /> -&gt;...RCU...-&gt;blk_free_queue_rcu()-&gt;kmem_cache_free()<br /> <br /> Otherwise, RCU callback may be executed first and<br /> dm_cleanup_zoned_dev() will touch free&amp;#39;d memory:<br /> <br /> BUG: KASAN: use-after-free in dm_cleanup_zoned_dev+0x33/0xd0<br /> Read of size 8 at addr ffff88805ac6e430 by task dmsetup/681<br /> <br /> CPU: 4 PID: 681 Comm: dmsetup Not tainted 5.17.0-rc2+ #6<br /> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014<br /> Call Trace:<br /> <br /> dump_stack_lvl+0x57/0x7d<br /> print_address_description.constprop.0+0x1f/0x150<br /> ? dm_cleanup_zoned_dev+0x33/0xd0<br /> kasan_report.cold+0x7f/0x11b<br /> ? dm_cleanup_zoned_dev+0x33/0xd0<br /> dm_cleanup_zoned_dev+0x33/0xd0<br /> __dm_destroy+0x26a/0x400<br /> ? dm_blk_ioctl+0x230/0x230<br /> ? up_write+0xd8/0x270<br /> dev_remove+0x156/0x1d0<br /> ctl_ioctl+0x269/0x530<br /> ? table_clear+0x140/0x140<br /> ? lock_release+0xb2/0x750<br /> ? remove_all+0x40/0x40<br /> ? rcu_read_lock_sched_held+0x12/0x70<br /> ? lock_downgrade+0x3c0/0x3c0<br /> ? rcu_read_lock_sched_held+0x12/0x70<br /> dm_ctl_ioctl+0xa/0x10<br /> __x64_sys_ioctl+0xb9/0xf0<br /> do_syscall_64+0x3b/0x90<br /> entry_SYSCALL_64_after_hwframe+0x44/0xae<br /> RIP: 0033:0x7fb6dfa95c27

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/i915/gem: add missing boundary check in vm_access<br /> <br /> A missing bounds check in vm_access() can lead to an out-of-bounds read<br /> or write in the adjacent memory area, since the len attribute is not<br /> validated before the memcpy later in the function, potentially hitting:<br /> <br /> [ 183.637831] BUG: unable to handle page fault for address: ffffc90000c86000<br /> [ 183.637934] #PF: supervisor read access in kernel mode<br /> [ 183.637997] #PF: error_code(0x0000) - not-present page<br /> [ 183.638059] PGD 100000067 P4D 100000067 PUD 100258067 PMD 106341067 PTE 0<br /> [ 183.638144] Oops: 0000 [#2] PREEMPT SMP NOPTI<br /> [ 183.638201] CPU: 3 PID: 1790 Comm: poc Tainted: G D 5.17.0-rc6-ci-drm-11296+ #1<br /> [ 183.638298] Hardware name: Intel Corporation CoffeeLake Client Platform/CoffeeLake H DDR4 RVP, BIOS CNLSFWR1.R00.X208.B00.1905301319 05/30/2019<br /> [ 183.638430] RIP: 0010:memcpy_erms+0x6/0x10<br /> [ 183.640213] RSP: 0018:ffffc90001763d48 EFLAGS: 00010246<br /> [ 183.641117] RAX: ffff888109c14000 RBX: ffff888111bece40 RCX: 0000000000000ffc<br /> [ 183.642029] RDX: 0000000000001000 RSI: ffffc90000c86000 RDI: ffff888109c14004<br /> [ 183.642946] RBP: 0000000000000ffc R08: 800000000000016b R09: 0000000000000000<br /> [ 183.643848] R10: ffffc90000c85000 R11: 0000000000000048 R12: 0000000000001000<br /> [ 183.644742] R13: ffff888111bed190 R14: ffff888109c14000 R15: 0000000000001000<br /> [ 183.645653] FS: 00007fe5ef807540(0000) GS:ffff88845b380000(0000) knlGS:0000000000000000<br /> [ 183.646570] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> [ 183.647481] CR2: ffffc90000c86000 CR3: 000000010ff02006 CR4: 00000000003706e0<br /> [ 183.648384] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000<br /> [ 183.649271] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400<br /> [ 183.650142] Call Trace:<br /> [ 183.650988] <br /> [ 183.651793] vm_access+0x1f0/0x2a0 [i915]<br /> [ 183.652726] __access_remote_vm+0x224/0x380<br /> [ 183.653561] mem_rw.isra.0+0xf9/0x190<br /> [ 183.654402] vfs_read+0x9d/0x1b0<br /> [ 183.655238] ksys_read+0x63/0xe0<br /> [ 183.656065] do_syscall_64+0x38/0xc0<br /> [ 183.656882] entry_SYSCALL_64_after_hwframe+0x44/0xae<br /> [ 183.657663] RIP: 0033:0x7fe5ef725142<br /> [ 183.659351] RSP: 002b:00007ffe1e81c7e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000000<br /> [ 183.660227] RAX: ffffffffffffffda RBX: 0000557055dfb780 RCX: 00007fe5ef725142<br /> [ 183.661104] RDX: 0000000000001000 RSI: 00007ffe1e81d880 RDI: 0000000000000005<br /> [ 183.661972] RBP: 00007ffe1e81e890 R08: 0000000000000030 R09: 0000000000000046<br /> [ 183.662832] R10: 0000557055dfc2e0 R11: 0000000000000246 R12: 0000557055dfb1c0<br /> [ 183.663691] R13: 00007ffe1e81e980 R14: 0000000000000000 R15: 0000000000000000<br /> <br /> Changes since v1:<br /> - Updated if condition with range_overflows_t [Chris Wilson]<br /> <br /> [mauld: tidy up the commit message and add Cc: stable]<br /> (cherry picked from commit 661412e301e2ca86799aa4f400d1cf0bd38c57c6)

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> exec: Force single empty string when argv is empty<br /> <br /> Quoting[1] Ariadne Conill:<br /> <br /> "In several other operating systems, it is a hard requirement that the<br /> second argument to execve(2) be the name of a program, thus prohibiting<br /> a scenario where argc

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ASoC: codecs: va-macro: fix accessing array out of bounds for enum type<br /> <br /> Accessing enums using integer would result in array out of bounds access<br /> on platforms like aarch64 where sizeof(long) is 8 compared to enum size<br /> which is 4 bytes.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ASoC: codecs: rx-macro: fix accessing array out of bounds for enum type<br /> <br /> Accessing enums using integer would result in array out of bounds access<br /> on platforms like aarch64 where sizeof(long) is 8 compared to enum size<br /> which is 4 bytes.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> media: usb: go7007: s2250-board: fix leak in probe()<br /> <br /> Call i2c_unregister_device(audio) on this error path.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> media: ti-vpe: cal: Fix a NULL pointer dereference in cal_ctx_v4l2_init_formats()<br /> <br /> In cal_ctx_v4l2_init_formats(), devm_kzalloc() is assigned to<br /> ctx-&gt;active_fmt and there is a dereference of it after that, which could<br /> lead to NULL pointer dereference on failure of devm_kzalloc().<br /> <br /> Fix this bug by adding a NULL check of ctx-&gt;active_fmt.<br /> <br /> This bug was found by a static analyzer.<br /> <br /> Builds with &amp;#39;make allyesconfig&amp;#39; show no new warnings, and our static<br /> analyzer no longer warns about this code.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> f2fs: fix missing free nid in f2fs_handle_failed_inode<br /> <br /> This patch fixes xfstests/generic/475 failure.<br /> <br /> [ 293.680694] F2FS-fs (dm-1): May loss orphan inode, run fsck to fix.<br /> [ 293.685358] Buffer I/O error on dev dm-1, logical block 8388592, async page read<br /> [ 293.691527] Buffer I/O error on dev dm-1, logical block 8388592, async page read<br /> [ 293.691764] sh (7615): drop_caches: 3<br /> [ 293.691819] sh (7616): drop_caches: 3<br /> [ 293.694017] Buffer I/O error on dev dm-1, logical block 1, async page read<br /> [ 293.695659] sh (7618): drop_caches: 3<br /> [ 293.696979] sh (7617): drop_caches: 3<br /> [ 293.700290] sh (7623): drop_caches: 3<br /> [ 293.708621] sh (7626): drop_caches: 3<br /> [ 293.711386] sh (7628): drop_caches: 3<br /> [ 293.711825] sh (7627): drop_caches: 3<br /> [ 293.716738] sh (7630): drop_caches: 3<br /> [ 293.719613] sh (7632): drop_caches: 3<br /> [ 293.720971] sh (7633): drop_caches: 3<br /> [ 293.727741] sh (7634): drop_caches: 3<br /> [ 293.730783] sh (7636): drop_caches: 3<br /> [ 293.732681] sh (7635): drop_caches: 3<br /> [ 293.732988] sh (7637): drop_caches: 3<br /> [ 293.738836] sh (7639): drop_caches: 3<br /> [ 293.740568] sh (7641): drop_caches: 3<br /> [ 293.743053] sh (7640): drop_caches: 3<br /> [ 293.821889] ------------[ cut here ]------------<br /> [ 293.824654] kernel BUG at fs/f2fs/node.c:3334!<br /> [ 293.826226] invalid opcode: 0000 [#1] PREEMPT SMP PTI<br /> [ 293.828713] CPU: 0 PID: 7653 Comm: umount Tainted: G OE 5.17.0-rc1-custom #1<br /> [ 293.830946] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014<br /> [ 293.832526] RIP: 0010:f2fs_destroy_node_manager+0x33f/0x350 [f2fs]<br /> [ 293.833905] Code: e8 d6 3d f9 f9 48 8b 45 d0 65 48 2b 04 25 28 00 00 00 75 1a 48 81 c4 28 03 00 00 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 0b<br /> [ 293.837783] RSP: 0018:ffffb04ec31e7a20 EFLAGS: 00010202<br /> [ 293.839062] RAX: 0000000000000001 RBX: ffff9df947db2eb8 RCX: 0000000080aa0072<br /> [ 293.840666] RDX: 0000000000000000 RSI: ffffe86c0432a140 RDI: ffffffffc0b72a21<br /> [ 293.842261] RBP: ffffb04ec31e7d70 R08: ffff9df94ca85780 R09: 0000000080aa0072<br /> [ 293.843909] R10: ffff9df94ca85700 R11: ffff9df94e1ccf58 R12: ffff9df947db2e00<br /> [ 293.845594] R13: ffff9df947db2ed0 R14: ffff9df947db2eb8 R15: ffff9df947db2eb8<br /> [ 293.847855] FS: 00007f5a97379800(0000) GS:ffff9dfa77c00000(0000) knlGS:0000000000000000<br /> [ 293.850647] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033<br /> [ 293.852940] CR2: 00007f5a97528730 CR3: 000000010bc76005 CR4: 0000000000370ef0<br /> [ 293.854680] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000<br /> [ 293.856423] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400<br /> [ 293.858380] Call Trace:<br /> [ 293.859302] <br /> [ 293.860311] ? ttwu_do_wakeup+0x1c/0x170<br /> [ 293.861800] ? ttwu_do_activate+0x6d/0xb0<br /> [ 293.863057] ? _raw_spin_unlock_irqrestore+0x29/0x40<br /> [ 293.864411] ? try_to_wake_up+0x9d/0x5e0<br /> [ 293.865618] ? debug_smp_processor_id+0x17/0x20<br /> [ 293.866934] ? debug_smp_processor_id+0x17/0x20<br /> [ 293.868223] ? free_unref_page+0xbf/0x120<br /> [ 293.869470] ? __free_slab+0xcb/0x1c0<br /> [ 293.870614] ? preempt_count_add+0x7a/0xc0<br /> [ 293.871811] ? __slab_free+0xa0/0x2d0<br /> [ 293.872918] ? __wake_up_common_lock+0x8a/0xc0<br /> [ 293.874186] ? __slab_free+0xa0/0x2d0<br /> [ 293.875305] ? free_inode_nonrcu+0x20/0x20<br /> [ 293.876466] ? free_inode_nonrcu+0x20/0x20<br /> [ 293.877650] ? debug_smp_processor_id+0x17/0x20<br /> [ 293.878949] ? call_rcu+0x11a/0x240<br /> [ 293.880060] ? f2fs_destroy_stats+0x59/0x60 [f2fs]<br /> [ 293.881437] ? kfree+0x1fe/0x230<br /> [ 293.882674] f2fs_put_super+0x160/0x390 [f2fs]<br /> [ 293.883978] generic_shutdown_super+0x7a/0x120<br /> [ 293.885274] kill_block_super+0x27/0x50<br /> [ 293.886496] kill_f2fs_super+0x7f/0x100 [f2fs]<br /> [ 293.887806] deactivate_locked_super+0x35/0xa0<br /> [ 293.889271] deactivate_super+0x40/0x50<br /> [ 293.890513] cleanup_mnt+0x139/0x190<br /> [ 293.891689] __cleanup_mnt+0x12/0x20<br /> [ 293.892850] task_work_run+0x64/0xa0<br /> [ 293.894035] exit_to_user_mode_prepare+0x1b7/<br /> ---truncated---

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> watch_queue: Actually free the watch<br /> <br /> free_watch() does everything barring actually freeing the watch object. Fix<br /> this by adding the missing kfree.<br /> <br /> kmemleak produces a report something like the following. Note that as an<br /> address can be seen in the first word, the watch would appear to have gone<br /> through call_rcu().<br /> <br /> BUG: memory leak<br /> unreferenced object 0xffff88810ce4a200 (size 96):<br /> comm "syz-executor352", pid 3605, jiffies 4294947473 (age 13.720s)<br /> hex dump (first 32 bytes):<br /> e0 82 48 0d 81 88 ff ff 00 00 00 00 00 00 00 00 ..H.............<br /> 80 a2 e4 0c 81 88 ff ff 00 00 00 00 00 00 00 00 ................<br /> backtrace:<br /> [] kmalloc include/linux/slab.h:581 [inline]<br /> [] kzalloc include/linux/slab.h:714 [inline]<br /> [] keyctl_watch_key+0xec/0x2e0 security/keys/keyctl.c:1800<br /> [] __do_sys_keyctl+0x3c4/0x490 security/keys/keyctl.c:2016<br /> [] do_syscall_x64 arch/x86/entry/common.c:50 [inline]<br /> [] do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80<br /> [] entry_SYSCALL_64_after_hwframe+0x44/0xae

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> watch_queue: Fix NULL dereference in error cleanup<br /> <br /> In watch_queue_set_size(), the error cleanup code doesn&amp;#39;t take account of<br /> the fact that __free_page() can&amp;#39;t handle a NULL pointer when trying to free<br /> up buffer pages that did get allocated.<br /> <br /> Fix this by only calling __free_page() on the pages actually allocated.<br /> <br /> Without the fix, this can lead to something like the following:<br /> <br /> BUG: KASAN: null-ptr-deref in __free_pages+0x1f/0x1b0 mm/page_alloc.c:5473<br /> Read of size 4 at addr 0000000000000034 by task syz-executor168/3599<br /> ...<br /> Call Trace:<br /> <br /> __dump_stack lib/dump_stack.c:88 [inline]<br /> dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106<br /> __kasan_report mm/kasan/report.c:446 [inline]<br /> kasan_report.cold+0x66/0xdf mm/kasan/report.c:459<br /> check_region_inline mm/kasan/generic.c:183 [inline]<br /> kasan_check_range+0x13d/0x180 mm/kasan/generic.c:189<br /> instrument_atomic_read include/linux/instrumented.h:71 [inline]<br /> atomic_read include/linux/atomic/atomic-instrumented.h:27 [inline]<br /> page_ref_count include/linux/page_ref.h:67 [inline]<br /> put_page_testzero include/linux/mm.h:717 [inline]<br /> __free_pages+0x1f/0x1b0 mm/page_alloc.c:5473<br /> watch_queue_set_size+0x499/0x630 kernel/watch_queue.c:275<br /> pipe_ioctl+0xac/0x2b0 fs/pipe.c:632<br /> vfs_ioctl fs/ioctl.c:51 [inline]<br /> __do_sys_ioctl fs/ioctl.c:874 [inline]<br /> __se_sys_ioctl fs/ioctl.c:860 [inline]<br /> __x64_sys_ioctl+0x193/0x200 fs/ioctl.c:860<br /> do_syscall_x64 arch/x86/entry/common.c:50 [inline]<br /> do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80<br /> entry_SYSCALL_64_after_hwframe+0x44/0xae