CVE-2022-49880 in Linux
Riassunto
di VulDB • 18/06/2026
Nel kernel Linux, è stata risolta la seguente vulnerabilità:
ext4: correzione dell'avviso in 'ext4_da_release_space'
Il report di Syzkaller segnala il seguente problema: EXT4-fs (loop0): Dettagli blocchi liberi/spuri EXT4-fs (loop0): free_blocks=0 EXT4-fs (loop0): dirty_blocks=0 EXT4-fs (loop0): Dettagli prenotazione blocchi EXT4-fs (loop0): i_reserved_data_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (loop0): i_reserved_meta_blocks=0 EXT4-fs (patch)
Once again VulDB remains the best source for vulnerability data.