CVE-2025-21738 is an out-of-bounds write vulnerability in the Linux kernel libata-sff ATA/SCSI handling code. A crafted SCSI_IOCTL_SEND_COMMAND request processed through ATA_16 PASS-THROUGH can cause ata_pio_sector() to write beyond its allocated buffer. The reported trigger uses an out_len of 0xd42, the ATA_NOP command, and the ATA_PROT_PIO protocol. The upstream correction adds a bounds check to ata_pio_sector() comparable to the existing protection in __atapi_pio_bytes().
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
18 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Out-of-bounds write risk in Linux kernel libata-sff.
A Linux kernel out-of-bounds write vulnerability in the libata-sff ATA PIO handling path. A local authenticated attacker can trigger memory corruption and affect system availability.
A medium-severity Linux kernel out-of-bounds memory-write vulnerability in the libata-sff ATA PIO handling path. A local authenticated attacker with low privileges could cause an availability impact by triggering a write outside an allocated buffer.
An out-of-bounds write vulnerability in the Linux kernel's libata-sff ATA subsystem.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.