CVSS: -EPSS: 0%CPEs: 4EXPL: 0CVE-2024-27036 – cifs: Fix writeback data corruption
https://notcve.org/view.php?id=CVE-2024-27036
In the Linux kernel, the following vulnerability has been resolved: cifs: Fix writeback data corruption cifs writeback doesn't correctly handle the case where cifs_extend_writeback() hits a point where it is considering an additional folio, but this would overrun the wsize - at which point it drops out of the xarray scanning loop and calls xas_pause(). The problem is that xas_pause() advances the loop counter - thereby skipping that page. What needs to happen is for xas_reset() to be called any time we decide we don't want to process the page we're looking at, but rather send the request we are building and start a new one. Fix this by copying and adapting the netfslib writepages code as a temporary measure, with cifs writeback intending to be offloaded to netfslib in the near future. This also fixes the issue with the use of filemap_get_folios_tag() causing retry of a bunch of pages which the extender already dealt with. This can be tested by creating, say, a 64K file somewhere not on cifs (otherwise copy-offload may get underfoot), mounting a cifs share with a wsize of 64000, copying the file to it and then comparing the original file and the copy: dd if=/dev/urandom of=/tmp/64K bs=64k count=1 mount //192.168.6.1/test /mnt -o user=...,pass=...,wsize=64000 cp /tmp/64K /mnt/64K cmp /tmp/64K /mnt/64K Without the fix, the cmp fails at position 64000 (or shortly thereafter). En el kernel de Linux, se resolvió la siguiente vulnerabilidad: cifs: corrige la corrupción de datos de reescritura cifs writeback no maneja correctamente el caso en el que cifs_extend_writeback() llega a un punto en el que está considerando una publicación adicional, pero esto sobrepasaría el tamaño de wsize - en momento en el que sale del ciclo de escaneo de xarray y llama a xas_pause(). • https://git.kernel.org/stable/c/d08089f649a0cfb2099c8551ac47eef0cc23fdf2 https://git.kernel.org/stable/c/e45deec35bf7f1f4f992a707b2d04a8c162f2240 https://git.kernel.org/stable/c/65f2ced695982ccd516196d0a9447d85dbe2eed5 https://git.kernel.org/stable/c/844b4e132f57f1333dc79feaa035075a096762e4 https://git.kernel.org/stable/c/f3dc1bdb6b0b0693562c7c54a6c28bafa608ba3c •
CVSS: -EPSS: 0%CPEs: 5EXPL: 0CVE-2024-27035 – f2fs: compress: fix to guarantee persisting compressed blocks by CP
https://notcve.org/view.php?id=CVE-2024-27035
In the Linux kernel, the following vulnerability has been resolved: f2fs: compress: fix to guarantee persisting compressed blocks by CP If data block in compressed cluster is not persisted with metadata during checkpoint, after SPOR, the data may be corrupted, let's guarantee to write compressed page by checkpoint. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: f2fs: compress: corrección para garantizar la persistencia de los bloques comprimidos por CP. Si el bloque de datos en el clúster comprimido no persiste con los metadatos durante el punto de control, después de SPOR, los datos pueden estar dañados, garanticemos que escribir página comprimida por punto de control. • https://git.kernel.org/stable/c/4c8ff7095bef64fc47e996a938f7d57f9e077da3 https://git.kernel.org/stable/c/e54cce8137258a550b49cae45d09e024821fb28d https://git.kernel.org/stable/c/82704e598d7b33c7e45526e34d3c585426319bed https://git.kernel.org/stable/c/c3311694b9bcced233548574d414c91d39214684 https://git.kernel.org/stable/c/57e8b17d0522c8f4daf0c4d9969b4d7358033532 https://git.kernel.org/stable/c/8a430dd49e9cb021372b0ad91e60aeef9c6ced00 •
CVSS: -EPSS: 0%CPEs: 6EXPL: 0CVE-2024-27034 – f2fs: compress: fix to cover normal cluster write with cp_rwsem
https://notcve.org/view.php?id=CVE-2024-27034
In the Linux kernel, the following vulnerability has been resolved: f2fs: compress: fix to cover normal cluster write with cp_rwsem When we overwrite compressed cluster w/ normal cluster, we should not unlock cp_rwsem during f2fs_write_raw_pages(), otherwise data will be corrupted if partial blocks were persisted before CP & SPOR, due to cluster metadata wasn't updated atomically. En el kernel de Linux, se resolvió la siguiente vulnerabilidad: f2fs: compress: corrección para cubrir la escritura normal del clúster con cp_rwsem Cuando sobrescribimos el clúster comprimido con el clúster normal, no debemos desbloquear cp_rwsem durante f2fs_write_raw_pages(); de lo contrario, los datos se dañarán si Los bloques parciales persistieron antes de CP y SPOR, debido a que los metadatos del clúster no se actualizaron atómicamente. • https://git.kernel.org/stable/c/4c8ff7095bef64fc47e996a938f7d57f9e077da3 https://git.kernel.org/stable/c/7d420eaaa18ec8e2bb4eeab8c65c00492ef6f416 https://git.kernel.org/stable/c/542c8b3c774a480bfd0804291a12f6f2391b0cd1 https://git.kernel.org/stable/c/75abfd61392b1db391bde6d738a30d685b843286 https://git.kernel.org/stable/c/2b1b14d9fc94b8feae20808684c8af28ec80f45b https://git.kernel.org/stable/c/52982edfcefd475cc34af663d5c47c0cddaa5739 https://git.kernel.org/stable/c/fd244524c2cf07b5f4c3fe8abd6a99225c76544b •
CVSS: -EPSS: 0%CPEs: 4EXPL: 0CVE-2024-27033 – f2fs: fix to remove unnecessary f2fs_bug_on() to avoid panic
https://notcve.org/view.php?id=CVE-2024-27033
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to remove unnecessary f2fs_bug_on() to avoid panic verify_blkaddr() will trigger panic once we inject fault into f2fs_is_valid_blkaddr(), fix to remove this unnecessary f2fs_bug_on(). En el kernel de Linux, se resolvió la siguiente vulnerabilidad: f2fs: solución para eliminar f2fs_bug_on() innecesario para evitar el pánico. verificar_blkaddr() provocará pánico una vez que inyectemos el error en f2fs_is_valid_blkaddr(), solución para eliminar este f2fs_bug_on() innecesario. • https://git.kernel.org/stable/c/18792e64c86dd7e34ba28e4f61faba472b7bf5fc https://git.kernel.org/stable/c/0386408036bfc8b50296d9e544ff91c4d52af2db https://git.kernel.org/stable/c/6633cdc8b2ebefcddcfcdacfd063105e60f39a49 https://git.kernel.org/stable/c/abe98a05e7162f64759bf9111108ebcb11322dec https://git.kernel.org/stable/c/b896e302f79678451a94769ddd9e52e954c64fbb •
CVSS: 6.3EPSS: 0%CPEs: 9EXPL: 0CVE-2024-27032 – f2fs: fix to avoid potential panic during recovery
https://notcve.org/view.php?id=CVE-2024-27032
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid potential panic during recovery During recovery, if FAULT_BLOCK is on, it is possible that f2fs_reserve_new_block() will return -ENOSPC during recovery, then it may trigger panic. Also, if fault injection rate is 1 and only FAULT_BLOCK fault type is on, it may encounter deadloop in loop of block reservation. Let's change as below to fix these issues: - remove bug_on() to avoid panic. - limit the loop count of block reservation to avoid potential deadloop. En el kernel de Linux, se resolvió la siguiente vulnerabilidad: f2fs: corrección para evitar un posible pánico durante la recuperación. Durante la recuperación, si FAULT_BLOCK está activado, es posible que f2fs_reserve_new_block() devuelva -ENOSPC durante la recuperación, lo que puede provocar pánico. Además, si la tasa de inyección de fallas es 1 y solo el tipo de falla FAULT_BLOCK está activado, es posible que se produzca un bucle muerto en el bucle de reserva de bloque. Cambiemos como se muestra a continuación para solucionar estos problemas: - elimine bug_on() para evitar el pánico. - limitar el número de bucles de reserva de bloques para evitar posibles bucles muertos. • https://git.kernel.org/stable/c/b1020a546779139eec5d930e15ce534c1101b89c https://git.kernel.org/stable/c/2a7b12d4705bc308cf18eae2b69ec8db34881cc3 https://git.kernel.org/stable/c/b29cc6e29b5e6037e1bcd2b2ac67b7d89acd194c https://git.kernel.org/stable/c/956fa1ddc132e028f3b7d4cf17e6bfc8cb36c7fd https://git.kernel.org/stable/c/bc1fb291f36dd1d9d667241d9fe30b835dbb8ee8 https://git.kernel.org/stable/c/9fceaf8182d453639cddb7f4a6877a1e1564de39 https://git.kernel.org/stable/c/80c69f576ff39d6ae8a6e2107da3dc03b533759c https://git.kernel.org/stable/c/b4fb0807a1d60f8642a5fd62bd659cd60 •