Vulnerabilities

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 /> PM: domains: Fix sleep-in-atomic bug caused by genpd_debug_remove()<br /> <br /> When a genpd with GENPD_FLAG_IRQ_SAFE gets removed, the following<br /> sleep-in-atomic bug will be seen, as genpd_debug_remove() will be called<br /> with a spinlock being held.<br /> <br /> [ 0.029183] BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:1460<br /> [ 0.029204] in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid: 1, name: swapper/0<br /> [ 0.029219] preempt_count: 1, expected: 0<br /> [ 0.029230] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.17.0-rc4+ #489<br /> [ 0.029245] Hardware name: Thundercomm TurboX CM2290 (DT)<br /> [ 0.029256] Call trace:<br /> [ 0.029265] dump_backtrace.part.0+0xbc/0xd0<br /> [ 0.029285] show_stack+0x3c/0xa0<br /> [ 0.029298] dump_stack_lvl+0x7c/0xa0<br /> [ 0.029311] dump_stack+0x18/0x34<br /> [ 0.029323] __might_resched+0x10c/0x13c<br /> [ 0.029338] __might_sleep+0x4c/0x80<br /> [ 0.029351] down_read+0x24/0xd0<br /> [ 0.029363] lookup_one_len_unlocked+0x9c/0xcc<br /> [ 0.029379] lookup_positive_unlocked+0x10/0x50<br /> [ 0.029392] debugfs_lookup+0x68/0xac<br /> [ 0.029406] genpd_remove.part.0+0x12c/0x1b4<br /> [ 0.029419] of_genpd_remove_last+0xa8/0xd4<br /> [ 0.029434] psci_cpuidle_domain_probe+0x174/0x53c<br /> [ 0.029449] platform_probe+0x68/0xe0<br /> [ 0.029462] really_probe+0x190/0x430<br /> [ 0.029473] __driver_probe_device+0x90/0x18c<br /> [ 0.029485] driver_probe_device+0x40/0xe0<br /> [ 0.029497] __driver_attach+0xf4/0x1d0<br /> [ 0.029508] bus_for_each_dev+0x70/0xd0<br /> [ 0.029523] driver_attach+0x24/0x30<br /> [ 0.029534] bus_add_driver+0x164/0x22c<br /> [ 0.029545] driver_register+0x78/0x130<br /> [ 0.029556] __platform_driver_register+0x28/0x34<br /> [ 0.029569] psci_idle_init_domains+0x1c/0x28<br /> [ 0.029583] do_one_initcall+0x50/0x1b0<br /> [ 0.029595] kernel_init_freeable+0x214/0x280<br /> [ 0.029609] kernel_init+0x2c/0x13c<br /> [ 0.029622] ret_from_fork+0x10/0x20<br /> <br /> It doesn&amp;#39;t seem necessary to call genpd_debug_remove() with the lock, so<br /> move it out from locking to fix the problem.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> block: fix rq-qos breakage from skipping rq_qos_done_bio()<br /> <br /> a647a524a467 ("block: don&amp;#39;t call rq_qos_ops-&gt;done_bio if the bio isn&amp;#39;t<br /> tracked") made bio_endio() skip rq_qos_done_bio() if BIO_TRACKED is not set.<br /> While this fixed a potential oops, it also broke blk-iocost by skipping the<br /> done_bio callback for merged bios.<br /> <br /> Before, whether a bio goes through rq_qos_throttle() or rq_qos_merge(),<br /> rq_qos_done_bio() would be called on the bio on completion with BIO_TRACKED<br /> distinguishing the former from the latter. rq_qos_done_bio() is not called<br /> for bios which wenth through rq_qos_merge(). This royally confuses<br /> blk-iocost as the merged bios never finish and are considered perpetually<br /> in-flight.<br /> <br /> One reliably reproducible failure mode is an intermediate cgroup geting<br /> stuck active preventing its children from being activated due to the<br /> leaf-only rule, leading to loss of control. The following is from<br /> resctl-bench protection scenario which emulates isolating a web server like<br /> workload from a memory bomb run on an iocost configuration which should<br /> yield a reasonable level of protection.<br /> <br /> # cat /sys/block/nvme2n1/device/model<br /> Samsung SSD 970 PRO 512GB<br /> # cat /sys/fs/cgroup/io.cost.model<br /> 259:0 ctrl=user model=linear rbps=834913556 rseqiops=93622 rrandiops=102913 wbps=618985353 wseqiops=72325 wrandiops=71025<br /> # cat /sys/fs/cgroup/io.cost.qos<br /> 259:0 enable=1 ctrl=user rpct=95.00 rlat=18776 wpct=95.00 wlat=8897 min=60.00 max=100.00<br /> # resctl-bench -m 29.6G -r out.json run protection::scenario=mem-hog,loops=1<br /> ...<br /> Memory Hog Summary<br /> ==================<br /> <br /> IO Latency: R p50=242u:336u/2.5m p90=794u:1.4m/7.5m p99=2.7m:8.0m/62.5m max=8.0m:36.4m/350m<br /> W p50=221u:323u/1.5m p90=709u:1.2m/5.5m p99=1.5m:2.5m/9.5m max=6.9m:35.9m/350m<br /> <br /> Isolation and Request Latency Impact Distributions:<br /> <br /> min p01 p05 p10 p25 p50 p75 p90 p95 p99 max mean stdev<br /> isol% 15.90 15.90 15.90 40.05 57.24 59.07 60.01 74.63 74.63 90.35 90.35 58.12 15.82<br /> lat-imp% 0 0 0 0 0 4.55 14.68 15.54 233.5 548.1 548.1 53.88 143.6<br /> <br /> Result: isol=58.12:15.82% lat_imp=53.88%:143.6 work_csv=100.0% missing=3.96%<br /> <br /> The isolation result of 58.12% is close to what this device would show<br /> without any IO control.<br /> <br /> Fix it by introducing a new flag BIO_QOS_MERGED to mark merged bios and<br /> calling rq_qos_done_bio() on them too. For consistency and clarity, rename<br /> BIO_TRACKED to BIO_QOS_THROTTLED. The flag checks are moved into<br /> rq_qos_done_bio() so that it&amp;#39;s next to the code paths that set the flags.<br /> <br /> With the patch applied, the above same benchmark shows:<br /> <br /> # resctl-bench -m 29.6G -r out.json run protection::scenario=mem-hog,loops=1<br /> ...<br /> Memory Hog Summary<br /> ==================<br /> <br /> IO Latency: R p50=123u:84.4u/985u p90=322u:256u/2.5m p99=1.6m:1.4m/9.5m max=11.1m:36.0m/350m<br /> W p50=429u:274u/995u p90=1.7m:1.3m/4.5m p99=3.4m:2.7m/11.5m max=7.9m:5.9m/26.5m<br /> <br /> Isolation and Request Latency Impact Distributions:<br /> <br /> min p01 p05 p10 p25 p50 p75 p90 p95 p99 max mean stdev<br /> isol% 84.91 84.91 89.51 90.73 92.31 94.49 96.36 98.04 98.71 100.0 100.0 94.42 2.81<br /> lat-imp% 0 0 0 0 0 2.81 5.73 11.11 13.92 17.53 22.61 4.10 4.68<br /> <br /> Result: isol=94.42:2.81% lat_imp=4.10%:4.68 work_csv=58.34% missing=0%

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 /> mmc: core: use sysfs_emit() instead of sprintf()<br /> <br /> sprintf() (still used in the MMC core for the sysfs output) is vulnerable<br /> to the buffer overflow. Use the new-fangled sysfs_emit() instead.<br /> <br /> Found by Linux Verification Center (linuxtesting.org) with the SVACE static<br /> analysis tool.

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---