Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-21738ata: libata-sff: Ensure that we cannot write outside the allocated buffer

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 20 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-21738, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 5a5dbd18a7496ed403f6f54bb20c955c65482fa5 – < a8f8cf87059ed1905c2a5c72f8b39a4f57b11b4c
    • affected 5a5dbd18a7496ed403f6f54bb20c955c65482fa5 – < d5e6e3000309359eae2a17117aa6e3c44897bf6c
    • affected 5a5dbd18a7496ed403f6f54bb20c955c65482fa5 – < 0dd5aade301a10f4b329fa7454fdcc2518741902
    • affected 5a5dbd18a7496ed403f6f54bb20c955c65482fa5 – < 0a17a9944b8d89ef03946121241870ac53ddaf45
    • affected 5a5dbd18a7496ed403f6f54bb20c955c65482fa5 – < 6e74e53b34b6dec5a50e1404e2680852ec6768d2
  • Linux · Linux

    • affected 2.6.22
    • unaffected < 2.6.22
    • unaffected 6.1.129 – ≤ 6.1.*
    • unaffected 6.6.78 – ≤ 6.6.*
    • unaffected 6.12.14 – ≤ 6.12.*
    • unaffected 6.13.3 – ≤ 6.13.*
    • unaffected 6.14 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-21738 badge
[![CVE-2025-21738](https://cveledger.app/badge/CVE-2025-21738.svg)](https://cveledger.app/cve/CVE-2025-21738)

Record last updated .