Używamy niezbędnych plików cookie do działania DataHouse.pl oraz opcjonalnych cookies do analityki i marketingu. Możesz zaakceptować wszystkie, odrzucić opcjonalne albo skonfigurować zgody.

OK, ZGADZAM SIĘ NIE ZGADZAM SIĘ ZMIENIAM ZGODY

Dzięki plikom cookies i podobnym technologiom (zwanym dalej „plikami cookies”) możemy poprawiać funkcjonalność naszej strony oraz wyświetlać treści dopasowane do Twoich potrzeb i oczekiwań.

Więcej informacji na temat wykorzystywania plików cookies znajdziesz w naszej [Polityce plików cookies].

Wyrażam zgodę na:

Analityczne wykorzystywanie plików cookies

Marketingowe wykorzystywanie plików cookies

Wykorzystywanie niezbędnych plików cookies (zawsze aktywne)

Twoje preferencje dotyczące plików cookies, wyrażone po zalogowaniu do serwisu, zostaną przypisane do Twojego konta Datahouse.pl. Dzięki temu zostaną zachowane także wtedy, gdy zalogujesz się na swoje konto z innego urządzenia lub przeglądarki.

POTWIERDŹ WYBÓR ANULUJ

CVE-2025-21738: linux kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: ata: libata-sff: Ensure that we cannot write outside the allocated buffer reveliofuzzing reported that a SCSI_IOCTL_SEND_COMMAND ioctl with out_len set to 0xd42, SCSI command set to ATA_16 PASS-THROUGH, ATA command set to ATA_NOP, and protocol set to ATA_PROT_PIO, can cause ata_pio_sector() to write outside the allocated buffer, overwriting random memory. While a ATA device is supposed to abort a ATA_NOP command, there does seem to be a bug either in libata-sff or QEMU, where either this status is not set, or the status is cleared before read by ata_sff_hsm_move(). Anyway, that is most likely a separate bug. Looking at __atapi_pio_bytes(), it already has a safety check to ensure that __atapi_pio_bytes() cannot write outside the allocated buffer. Add a similar check to ata_pio_sector(), such that also ata_pio_sector() cannot write outside the allocated buffer.

CVE-2025-21738CVSS 5.5Linux

CVE-2025-21738: linux kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: ata: libata-sff: Ensure that we cannot write outside the allocated buffer reveliofuzzing reported that a SCSI_IOCTL_SEND_COMMAND ioctl with out_len set to 0xd42, SCSI command set to ATA_16 PASS-THROUGH, ATA command set to ATA_NOP, and protocol set to ATA_PROT_PIO, can cause ata_pio_sector() to write outside the allocated buffer, overwriting random memory. While a ATA device is supposed to abort a ATA_NOP command, there does seem to be a bug either in libata-sff or QEMU, where either this status is not set, or the status is cleared before read by ata_sff_hsm_move(). Anyway, that is most likely a separate bug. Looking at __atapi_pio_bytes(), it already has a safety check to ensure that __atapi_pio_bytes() cannot write outside the allocated buffer. Add a similar check to ata_pio_sector(), such that also ata_pio_sector() cannot write outside the allocated buffer.

CVSS: 5.5 MEDIUM
EPSS: 9.57%
Aktywnie wykorzystywana: brak w KEV
Produkt: linux kernel

Co wiadomo

In the Linux kernel, the following vulnerability has been resolved: ata: libata-sff: Ensure that we cannot write outside the allocated buffer reveliofuzzing reported that a SCSI_IOCTL_SEND_COMMAND ioctl with out_len set to 0xd42, SCSI command set to ATA_16 PASS-THROUGH, ATA command set to ATA_NOP, and protocol set to ATA_PROT_PIO, can cause ata_pio_sector() to write outside the allocated buffer, overwriting random memory. While a ATA device is supposed to abort a ATA_NOP command, there does seem to be a bug either in libata-sff or QEMU, where either this status is not set, or the status is cleared before read by ata_sff_hsm_move(). Anyway, that is most likely a separate bug. Looking at __atapi_pio_bytes(), it already has a safety check to ensure that __atapi_pio_bytes() cannot write outside the allocated buffer. Add a similar check to ata_pio_sector(), such that also ata_pio_sector() cannot write outside the allocated buffer.

Źródła

Wróć do centrum bezpieczeństwa Skontaktuj się z DataHouse