Answer in brief
CVE-2025-21738 records a Unknown severity vulnerability in ata: libata-sff: Ensure that we cannot write outside the allocated buffer. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5a5dbd18a7496ed403f6f54bb20c955c65482fa5 <a8f8cf87059ed1905c2a5c72f8b39a4f57b11b4c || >=5a5dbd18a7496ed403f6f54bb20c955c65482fa5 <d5e6e3000309359eae2a17117aa6e3c44897bf6c || >=5a5dbd18a7496ed403f6f54bb20c955c65482fa5 <0dd5aade301a10f4b329fa7454fdcc2518741902 || >=5a5dbd18a7496ed403f6f54bb20c955c65482fa5 <0a17a9944b8d89ef03946121241870ac53ddaf45 || >=5a5dbd18a7496ed403f6f54bb20c955c65482fa5 <6e74e53b34b6dec5a50e1404e2680852ec6768d2 | a8f8cf87059ed1905c2a5c72f8b39a4f57b11b4c, d5e6e3000309359eae2a17117aa6e3c44897bf6c, 0dd5aade301a10f4b329fa7454fdcc2518741902, 0a17a9944b8d89ef03946121241870ac53ddaf45, 6e74e53b34b6dec5a50e1404e2680852ec6768d2 |
| Linux/Linuxgeneric | 2.6.22 | Not reported |
Published upstream
Feb 27, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2025-21738 records a Unknown severity vulnerability in ata: libata-sff: Ensure that we cannot write outside the allocated buffer. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=5a5dbd18a7496ed403f6f54bb20c955c65482fa5 <a8f8cf87059ed1905c2a5c72f8b39a4f57b11b4c || >=5a5dbd18a7496ed403f6f54bb20c955c65482fa5 <d5e6e3000309359eae2a17117aa6e3c44897bf6c || >=5a5dbd18a7496ed403f6f54bb20c955c65482fa5 <0dd5aade301a10f4b329fa7454fdcc2518741902 || >=5a5dbd18a7496ed403f6f54bb20c955c65482fa5 <0a17a9944b8d89ef03946121241870ac53ddaf45 || >=5a5dbd18a7496ed403f6f54bb20c955c65482fa5 <6e74e53b34b6dec5a50e1404e2680852ec6768d2 | a8f8cf87059ed1905c2a5c72f8b39a4f57b11b4c, d5e6e3000309359eae2a17117aa6e3c44897bf6c, 0dd5aade301a10f4b329fa7454fdcc2518741902, 0a17a9944b8d89ef03946121241870ac53ddaf45, 6e74e53b34b6dec5a50e1404e2680852ec6768d2 |
| Linux/Linuxgeneric | 2.6.22 | Not reported |
Published upstream
Feb 27, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.