Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> block, bfq: fix uaf for bfqq in bfq_exit_icq_bfqq<br /> <br /> Commit 64dc8c732f5c ("block, bfq: fix possible uaf for &amp;#39;bfqq-&gt;bic&amp;#39;")<br /> will access &amp;#39;bic-&gt;bfqq&amp;#39; in bic_set_bfqq(), however, bfq_exit_icq_bfqq()<br /> can free bfqq first, and then call bic_set_bfqq(), which will cause uaf.<br /> <br /> Fix the problem by moving bfq_exit_bfqq() behind bic_set_bfqq().

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> crypto: cavium - prevent integer overflow loading firmware<br /> <br /> The "code_length" value comes from the firmware file. If your firmware<br /> is untrusted realistically there is probably very little you can do to<br /> protect yourself. Still we try to limit the damage as much as possible.<br /> Also Smatch marks any data read from the filesystem as untrusted and<br /> prints warnings if it not capped correctly.<br /> <br /> The "ntohl(ucode-&gt;code_length) * 2" multiplication can have an<br /> integer overflow.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> video/aperture: Call sysfb_disable() before removing PCI devices<br /> <br /> Call sysfb_disable() from aperture_remove_conflicting_pci_devices()<br /> before removing PCI devices. Without, simpledrm can still bind to<br /> simple-framebuffer devices after the hardware driver has taken over<br /> the hardware. Both drivers interfere with each other and results are<br /> undefined.<br /> <br /> Reported modesetting errors [1] are shown below.<br /> <br /> ---- snap ----<br /> rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 13-.... } 7 jiffies s: 165 root: 0x2000/.<br /> rcu: blocking rcu_node structures (internal RCU debug):<br /> Task dump for CPU 13:<br /> task:X state:R running task stack: 0 pid: 4242 ppid: 4228 flags:0x00000008<br /> Call Trace:<br /> <br /> ? commit_tail+0xd7/0x130<br /> ? drm_atomic_helper_commit+0x126/0x150<br /> ? drm_atomic_commit+0xa4/0xe0<br /> ? drm_plane_get_damage_clips.cold+0x1c/0x1c<br /> ? drm_atomic_helper_dirtyfb+0x19e/0x280<br /> ? drm_mode_dirtyfb_ioctl+0x10f/0x1e0<br /> ? drm_mode_getfb2_ioctl+0x2d0/0x2d0<br /> ? drm_ioctl_kernel+0xc4/0x150<br /> ? drm_ioctl+0x246/0x3f0<br /> ? drm_mode_getfb2_ioctl+0x2d0/0x2d0<br /> ? __x64_sys_ioctl+0x91/0xd0<br /> ? do_syscall_64+0x60/0xd0<br /> ? entry_SYSCALL_64_after_hwframe+0x4b/0xb5<br /> <br /> ...<br /> rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 13-.... } 30 jiffies s: 169 root: 0x2000/.<br /> rcu: blocking rcu_node structures (internal RCU debug):<br /> Task dump for CPU 13:<br /> task:X state:R running task stack: 0 pid: 4242 ppid: 4228 flags:0x0000400e<br /> Call Trace:<br /> <br /> ? memcpy_toio+0x76/0xc0<br /> ? memcpy_toio+0x1b/0xc0<br /> ? drm_fb_memcpy_toio+0x76/0xb0<br /> ? drm_fb_blit_toio+0x75/0x2b0<br /> ? simpledrm_simple_display_pipe_update+0x132/0x150<br /> ? drm_atomic_helper_commit_planes+0xb6/0x230<br /> ? drm_atomic_helper_commit_tail+0x44/0x80<br /> ? commit_tail+0xd7/0x130<br /> ? drm_atomic_helper_commit+0x126/0x150<br /> ? drm_atomic_commit+0xa4/0xe0<br /> ? drm_plane_get_damage_clips.cold+0x1c/0x1c<br /> ? drm_atomic_helper_dirtyfb+0x19e/0x280<br /> ? drm_mode_dirtyfb_ioctl+0x10f/0x1e0<br /> ? drm_mode_getfb2_ioctl+0x2d0/0x2d0<br /> ? drm_ioctl_kernel+0xc4/0x150<br /> ? drm_ioctl+0x246/0x3f0<br /> ? drm_mode_getfb2_ioctl+0x2d0/0x2d0<br /> ? __x64_sys_ioctl+0x91/0xd0<br /> ? do_syscall_64+0x60/0xd0<br /> ? entry_SYSCALL_64_after_hwframe+0x4b/0xb5<br /> <br /> <br /> The problem was added by commit 5e0137612430 ("video/aperture: Disable<br /> and unregister sysfb devices via aperture helpers") to v6.0.3 and does<br /> not exist in the mainline branch.<br /> <br /> The mainline commit 5e0137612430 ("video/aperture: Disable and<br /> unregister sysfb devices via aperture helpers") has been backported<br /> from v6.0-rc1 to stable v6.0.3 from a larger patch series [2] that<br /> reworks fbdev framebuffer ownership. The backport misses a change to<br /> aperture_remove_conflicting_pci_devices(). Mainline itself is fine,<br /> because the function does not exist there as a result of the patch<br /> series.<br /> <br /> Instead of backporting the whole series, fix the additional function.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> fs: jfs: fix shift-out-of-bounds in dbDiscardAG<br /> <br /> This should be applied to most URSAN bugs found recently by syzbot,<br /> by guarding the dbMount. As syzbot feeding rubbish into the bmap<br /> descriptor.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> hugetlbfs: fix null-ptr-deref in hugetlbfs_parse_param()<br /> <br /> Syzkaller reports a null-ptr-deref bug as follows:<br /> ======================================================<br /> KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]<br /> RIP: 0010:hugetlbfs_parse_param+0x1dd/0x8e0 fs/hugetlbfs/inode.c:1380<br /> [...]<br /> Call Trace:<br /> <br /> vfs_parse_fs_param fs/fs_context.c:148 [inline]<br /> vfs_parse_fs_param+0x1f9/0x3c0 fs/fs_context.c:129<br /> vfs_parse_fs_string+0xdb/0x170 fs/fs_context.c:191<br /> generic_parse_monolithic+0x16f/0x1f0 fs/fs_context.c:231<br /> do_new_mount fs/namespace.c:3036 [inline]<br /> path_mount+0x12de/0x1e20 fs/namespace.c:3370<br /> do_mount fs/namespace.c:3383 [inline]<br /> __do_sys_mount fs/namespace.c:3591 [inline]<br /> __se_sys_mount fs/namespace.c:3568 [inline]<br /> __x64_sys_mount+0x27f/0x300 fs/namespace.c:3568<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+0x63/0xcd<br /> [...]<br /> <br /> ======================================================<br /> <br /> According to commit "vfs: parse: deal with zero length string value",<br /> kernel will set the param-&gt;string to null pointer in vfs_parse_fs_string()<br /> if fs string has zero length.<br /> <br /> Yet the problem is that, hugetlbfs_parse_param() will dereference the<br /> param-&gt;string, without checking whether it is a null pointer. To be more<br /> specific, if hugetlbfs_parse_param() parses an illegal mount parameter,<br /> such as "size=,", kernel will constructs struct fs_parameter with null<br /> pointer in vfs_parse_fs_string(), then passes this struct fs_parameter to<br /> hugetlbfs_parse_param(), which triggers the above null-ptr-deref bug.<br /> <br /> This patch solves it by adding sanity check on param-&gt;string<br /> in hugetlbfs_parse_param().

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> 9p: set req refcount to zero to avoid uninitialized usage<br /> <br /> When a new request is allocated, the refcount will be zero if it is<br /> reused, but if the request is newly allocated from slab, it is not fully<br /> initialized before being added to idr.<br /> <br /> If the p9_read_work got a response before the refcount initiated. It will<br /> use a uninitialized req, which will result in a bad request data struct.<br /> <br /> Here is the logs from syzbot.<br /> <br /> Corrupted memory at 0xffff88807eade00b [ 0xff 0x07 0x00 0x00 0x00 0x00<br /> 0x00 0x00 . . . . . . . . ] (in kfence-#110):<br /> p9_fcall_fini net/9p/client.c:248 [inline]<br /> p9_req_put net/9p/client.c:396 [inline]<br /> p9_req_put+0x208/0x250 net/9p/client.c:390<br /> p9_client_walk+0x247/0x540 net/9p/client.c:1165<br /> clone_fid fs/9p/fid.h:21 [inline]<br /> v9fs_fid_xattr_set+0xe4/0x2b0 fs/9p/xattr.c:118<br /> v9fs_xattr_set fs/9p/xattr.c:100 [inline]<br /> v9fs_xattr_handler_set+0x6f/0x120 fs/9p/xattr.c:159<br /> __vfs_setxattr+0x119/0x180 fs/xattr.c:182<br /> __vfs_setxattr_noperm+0x129/0x5f0 fs/xattr.c:216<br /> __vfs_setxattr_locked+0x1d3/0x260 fs/xattr.c:277<br /> vfs_setxattr+0x143/0x340 fs/xattr.c:309<br /> setxattr+0x146/0x160 fs/xattr.c:617<br /> path_setxattr+0x197/0x1c0 fs/xattr.c:636<br /> __do_sys_setxattr fs/xattr.c:652 [inline]<br /> __se_sys_setxattr fs/xattr.c:648 [inline]<br /> __ia32_sys_setxattr+0xc0/0x160 fs/xattr.c:648<br /> do_syscall_32_irqs_on arch/x86/entry/common.c:112 [inline]<br /> __do_fast_syscall_32+0x65/0xf0 arch/x86/entry/common.c:178<br /> do_fast_syscall_32+0x33/0x70 arch/x86/entry/common.c:203<br /> entry_SYSENTER_compat_after_hwframe+0x70/0x82<br /> <br /> Below is a similar scenario, the scenario in the syzbot log looks more<br /> complicated than this one, but this patch can fix it.<br /> <br /> T21124 p9_read_work<br /> ======================== second trans =================================<br /> p9_client_walk<br /> p9_client_rpc<br /> p9_client_prepare_req<br /> p9_tag_alloc<br /> req = kmem_cache_alloc(p9_req_cache, GFP_NOFS);<br /> tag = idr_alloc<br /> <br /> req-&gt;tc.tag = tag;<br /> /* req-&gt;[refcount/tag] == uninitialized */<br /> m-&gt;rreq = p9_tag_lookup(m-&gt;client, m-&gt;rc.tag);<br /> /* increments uninitalized refcount */<br /> <br /> refcount_set(&amp;req-&gt;refcount, 2);<br /> /* cb drops one ref */<br /> p9_client_cb(req)<br /> /* reader thread drops its ref:<br /> request is incorrectly freed */<br /> p9_req_put(req)<br /> /* use after free and ref underflow */<br /> p9_req_put(req)<br /> <br /> To fix it, we can initialize the refcount to zero before add to idr.

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