CVE-2026-89586
ata: libata-scsi: fix DSM TRIM for sector sizes larger than 2048 bytes
Reported by linux · Published September 11, 2026
In the Linux kernel, the following vulnerability has been resolved: ata: libata-scsi: fix DSM TRIM for sector sizes larger than 2048 bytes ata_scsi_write_same_xlat() translates a SCSI WRITE SAME command with the UNMAP bit set into an ATA DATA SET MANAGEMENT TRIM command. The TRIM descriptor is built by ata_format_dsm_trim_descr() into the 2048-byte ata_scsi_rbuf staging buffer, and the number of bytes copied is compared against the logical sector size by the caller: size = ata_format_dsm_trim_descr(scmd, trmax, block, n_block); if (size != len) /* len == sdp->sector_size */ goto invalid_param_len; ata_format_dsm_trim_descr() clamps the copy length to ATA_SCSI_RBUF_SIZE (2048). On a device whose logical sector size exceeds that (e.g. a 4Kn device, where sector_size == 4096) the function can never return more than 2048, while the caller expects it to return sector_size. The comparison therefore always fails, so every TRIM is rejected with "Parameter list length error" and WARN_ON() splats on each attempt. TRIM / discard is thus completely broken on such devices. The descriptor was incorrectly sized from the logical sector size. A DSM TRIM payload is a list of 512-byte pages, each holding up to ATA_MAX_TRIM_RNUM (64) LBA Range Entries, and is independent of the logical sector size. The Block Limits VPD page already advertises a single such page as the maximum WRITE SAME length (65535 * ATA_MAX_TRIM_RNUM logical blocks), so the block layer never sends a request that needs more than one page. Emit exactly one 512-byte page, independent of the logical sector size, and transfer only that page (COUNT == 1). For a 512-byte-sector device this is unchanged; devices with larger logical sectors now work instead of failing every TRIM.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| python3-perf6.18 | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| kernel-modules-extra-common | Amazon Linux | 1:6.1.188-233.385.amzn2023 |
| bpftool6.18 | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| perf6.18 | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| perf | Amazon Linux | 1:6.1.188-233.385.amzn2023 |
| perf6.12 | Amazon Linux | 1:6.12.110-135.201.amzn2023 |
| kernel-tools-devel | Amazon Linux | 1:6.1.188-233.385.amzn2023 |
| kernel6.18-headers | Amazon Linux | 1:6.18.51-120.162.amzn2023 |
| kernel | Amazon Linux | 1:6.1.188-233.385.amzn2023 |
| Linux | Linux | c2e3dccd6870659851eaa4c12ab16418b8e3040a, 4.9 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | ef2d7392c4ece5c3cd12a6c7ca9366cd8f189aff, ef2d7392c4ece5c3cd12a6c7ca9366cd8f189aff, ef2d7392c4ece5c3cd12a6c7ca9366cd8f189aff |
| Linux | Linux | 4.9, 0, 5.10.270 |
| amazon:2023 | python3-perf6.18 | 0 |
| amazon:2023 | kernel-modules-extra-common | 0 |
| amazon:2023 | bpftool6.18 | 0 |
| amazon:2023 | perf6.18 | 0 |
| amazon:2023 | perf | 0 |
| amazon:2023 | perf6.12 | 0 |
| amazon:2023 | kernel-tools-devel | 0 |
| amazon:2023 | kernel6.18-headers | 0 |
| amazon:2023 | kernel | 0 |
| Linux | Linux | 0, *, 7.3 |
| amazon:2023 | kernel-headers | 0 |
| amazon:2023 | kernel-modules-extra | 0 |
| amazon:2023 | kernel6.12-tools-devel | 0 |
| amazon:2023 | kernel-livepatch-6.1.188-233.385 | 0 |
| amazon:2023 | microvm-kernel6.18 | 0 |
| amazon:2023 | kernel6.12-modules-extra | 0 |
| amazon:2023 | bpftool6.12 | 0 |
| amazon:2023 | bpftool | 0 |
…and 18 more
Timeline
- Sep 11, 2026 CVE Published
- Sep 12, 2026 EPSS Score (29 in total, the first dated here)
- Oct 19, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-89586
vulnetix vdb fixes CVE-2026-89586
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-89586/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart