CVE Catalog

CVE-2025-21738

HighCVSS 7.8
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.22%

13th percentile - higher than 13% of all known CVEs

Summary

In the Linux kernel, the libata-sff subsystem has a bug that allows writing outside the allocated buffer during ATA PIO command handling. The ata_pio_sector() function lacked a bounds check, unlike the similar __atapi_pio_bytes() function. This can lead to overwriting random memory.

Risk Assessment

An attacker can send a specially crafted SCSI command (e.g., ATA_16 PASS-THROUGH with ATA_NOP and PIO protocol), causing an out-of-bounds write and potentially corrupting kernel memory, leading to system crash or privilege escalation.

Recommendation

Apply the Linux kernel patch that adds a buffer bounds check in ata_pio_sector(), similar to the one in __atapi_pio_bytes().

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS