CVSS: -EPSS: 0%CPEs: 4EXPL: 0CVE-2023-52682 – f2fs: fix to wait on block writeback for post_read case
https://notcve.org/view.php?id=CVE-2023-52682
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to wait on block writeback for post_read case If inode is compressed, but not encrypted, it missed to call f2fs_wait_on_block_writeback() to wait for GCed page writeback in IPU write path. Thread A GC-Thread - f2fs_gc - do_garbage_collect - gc_data_segment - move_data_block - f2fs_submit_page_write migrate normal cluster's block via meta_inode's page cache - f2fs_write_single_data_page - f2fs_do_write_data_page - f2fs_inplace_write_data - f2fs_submit_page_bio IRQ - f2fs_read_end_io IRQ old data overrides new data due to out-of-order GC and common IO. - f2fs_read_end_io En el kernel de Linux, se resolvió la siguiente vulnerabilidad: f2fs: corrección para esperar en la reescritura del bloque para el caso post_read. Si el inodo está comprimido, pero no encriptado, no llamó a f2fs_wait_on_block_writeback() para esperar la reescritura de la página GCed en la ruta de escritura de la IPU. Subproceso A GC-Thread - f2fs_gc - do_garbage_collect - gc_data_segment - move_data_block - f2fs_submit_page_write migra el bloque del clúster normal a través del caché de página de meta_inode - f2fs_write_single_data_page - f2fs_do_write_data_page - f2fs_inplace_write_data - f2fs_submit_page_bio IRQ - fs_read_end_io Los datos antiguos de IRQ anulan los datos nuevos debido a GC desordenado y común OÍ. - f2fs_read_end_io • https://git.kernel.org/stable/c/4c8ff7095bef64fc47e996a938f7d57f9e077da3 https://git.kernel.org/stable/c/9bfd5ea71521d0e522ba581c6ccc5db93759c0c3 https://git.kernel.org/stable/c/4535be48780431753505e74e1b1ad4836a189bc2 https://git.kernel.org/stable/c/f904c156d8011d8291ffd5b6b398f3747e294986 https://git.kernel.org/stable/c/55fdc1c24a1d6229fe0ecf31335fb9a2eceaaa00 •
CVSS: 5.5EPSS: 0%CPEs: 5EXPL: 0CVE-2023-52680 – ALSA: scarlett2: Add missing error checks to *_ctl_get()
https://notcve.org/view.php?id=CVE-2023-52680
In the Linux kernel, the following vulnerability has been resolved: ALSA: scarlett2: Add missing error checks to *_ctl_get() The *_ctl_get() functions which call scarlett2_update_*() were not checking the return value. Fix to check the return value and pass to the caller. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ALSA: scarlett2: Agregar comprobaciones de errores faltantes a *_ctl_get() Las funciones *_ctl_get() que llaman a scarlett2_update_*() no estaban comprobando el valor de retorno. Corrija para verificar el valor de retorno y pasarlo a la persona que llama. • https://git.kernel.org/stable/c/9e4d5c1be21f0c00e747e92186784f3298309b3e https://git.kernel.org/stable/c/3a09488f4f67f7ade59b8ac62a6c7fb29439cf51 https://git.kernel.org/stable/c/cda7762bea857e6951315a2f7d0632ea1850ed43 https://git.kernel.org/stable/c/821fbaeaaae23d483d3df799fe91ec8045973ec3 https://git.kernel.org/stable/c/773e38f73461ef2134a0d33a08f1668edde9b7c3 https://git.kernel.org/stable/c/50603a67daef161c78c814580d57f7f0be57167e https://access.redhat.com/security/cve/CVE-2023-52680 https://bugzilla.redhat.com/show_bug.cgi?id=2281324 •
CVSS: 5.5EPSS: 0%CPEs: 8EXPL: 0CVE-2023-52679 – of: Fix double free in of_parse_phandle_with_args_map
https://notcve.org/view.php?id=CVE-2023-52679
In the Linux kernel, the following vulnerability has been resolved: of: Fix double free in of_parse_phandle_with_args_map In of_parse_phandle_with_args_map() the inner loop that iterates through the map entries calls of_node_put(new) to free the reference acquired by the previous iteration of the inner loop. This assumes that the value of "new" is NULL on the first iteration of the inner loop. Make sure that this is true in all iterations of the outer loop by setting "new" to NULL after its value is assigned to "cur". Extend the unittest to detect the double free and add an additional test case that actually triggers this path. En el kernel de Linux se ha resuelto la siguiente vulnerabilidad: of: Solucionado double free en of_parse_phandle_with_args_map En of_parse_phandle_with_args_map() el bucle interno que itera por las entradas del mapa llama a of_node_put(new) para liberar la referencia adquirida por la iteración anterior del bucle interno . Esto supone que el valor de "nuevo" es NULL en la primera iteración del bucle interno. Asegúrese de que esto sea cierto en todas las iteraciones del bucle externo estableciendo "nuevo" en NULL después de que su valor se asigne a "cur". • https://git.kernel.org/stable/c/bd6f2fd5a1d52198468c5cdc3c2472362dff5aaa https://git.kernel.org/stable/c/26b4d702c44f9e5cf3c5c001ae619a4a001889db https://git.kernel.org/stable/c/a0a061151a6200c13149dbcdb6c065203c8425d2 https://git.kernel.org/stable/c/d5f490343c77e6708b6c4aa7dbbfbcbb9546adea https://git.kernel.org/stable/c/4541004084527ce9e95a818ebbc4e6b293ffca21 https://git.kernel.org/stable/c/b9d760dae5b10e73369b769073525acd7b3be2bd https://git.kernel.org/stable/c/b64d09a4e8596f76d27f4b4a90a1cf6baf6a82f8 https://git.kernel.org/stable/c/cafa992134124e785609a406da4ff2b54 •
CVSS: -EPSS: 0%CPEs: 5EXPL: 0CVE-2023-52677 – riscv: Check if the code to patch lies in the exit section
https://notcve.org/view.php?id=CVE-2023-52677
In the Linux kernel, the following vulnerability has been resolved: riscv: Check if the code to patch lies in the exit section Otherwise we fall through to vmalloc_to_page() which panics since the address does not lie in the vmalloc region. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: riscv: compruebe si el código a parchear se encuentra en la sección de salida. De lo contrario, caeremos en vmalloc_to_page(), lo que entra en pánico ya que la dirección no se encuentra en la región vmalloc. • https://git.kernel.org/stable/c/043cb41a85de1c0e944da61ad7a264960e22c865 https://git.kernel.org/stable/c/938f70d14618ec72e10d6fcf8a546134136d7c13 https://git.kernel.org/stable/c/890cfe5337e0aaf03ece1429db04d23c88da72e7 https://git.kernel.org/stable/c/8db56df4a954b774bdc68917046a685a9fa2e4bc https://git.kernel.org/stable/c/1d7a03052846f34d624d0ab41a879adf5e85c85f https://git.kernel.org/stable/c/420370f3ae3d3b883813fd3051a38805160b2b9f •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2023-52676 – bpf: Guard stack limits against 32bit overflow
https://notcve.org/view.php?id=CVE-2023-52676
In the Linux kernel, the following vulnerability has been resolved: bpf: Guard stack limits against 32bit overflow This patch promotes the arithmetic around checking stack bounds to be done in the 64-bit domain, instead of the current 32bit. The arithmetic implies adding together a 64-bit register with a int offset. The register was checked to be below 1<<29 when it was variable, but not when it was fixed. The offset either comes from an instruction (in which case it is 16 bit), from another register (in which case the caller checked it to be below 1<<29 [1]), or from the size of an argument to a kfunc (in which case it can be a u32 [2]). Between the register being inconsistently checked to be below 1<<29, and the offset being up to an u32, it appears that we were open to overflowing the `int`s which were currently used for arithmetic. [1] https://github.com/torvalds/linux/blob/815fb87b753055df2d9e50f6cd80eb10235fe3e9/kernel/bpf/verifier.c#L7494-L7498 [2] https://github.com/torvalds/linux/blob/815fb87b753055df2d9e50f6cd80eb10235fe3e9/kernel/bpf/verifier.c#L11904 En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: bpf: Proteger los límites de la pila contra el desbordamiento de 32 bits. • https://git.kernel.org/stable/c/ad140fc856f0b1d5e2215bcb6d0cc247a86805a2 https://git.kernel.org/stable/c/e5ad9ecb84405637df82732ee02ad741a5f782a6 https://git.kernel.org/stable/c/1d38a9ee81570c4bd61f557832dead4d6f816760 https://access.redhat.com/security/cve/CVE-2023-52676 https://bugzilla.redhat.com/show_bug.cgi?id=2281332 •