CVE-2026-89586: ata: libata-scsi: fix DSM TRIM for sector sizes larger than 2048 bytes

Published Sep 11, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

ata: libata-scsi: fix DSM TRIM for sector sizes larger than 2048 bytes

atascsiwritesamexlat() 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 ataformatdsmtrimdescr() into the 2048-byte atascsirbuf staging buffer, and the number of bytes copied is compared against the logical sector size by the caller:

size = ataformatdsmtrimdescr(scmd, trmax, block, nblock); if (size != len) / len == sdp->sectorsize / goto invalidparamlen;

ataformatdsmtrimdescr() clamps the copy length to ATASCSIRBUFSIZE (2048). On a device whose logical sector size exceeds that (e.g. a 4Kn device, where sectorsize == 4096) the function can never return more than 2048, while the caller expects it to return sectorsize. The comparison therefore always fails, so every TRIM is rejected with "Parameter list length error" and WARNON() 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 ATAMAXTRIMRNUM (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 ATAMAXTRIMRNUM 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.

Affected Software

1 affected component
Linux Kernel

Event History

Sep 11, 2026
CVE Published
via MITRE·07:44 PM
Data Sourced
via MITRE·07:44 PM
Description

Frequently Asked Questions

1

Are upstream fixes available?

Yes. The provided references identify stable Linux kernel fixes in commits 04e2befe25792f2e90097f284d7e86fc6bcfe928, c2e3dccd6870659851eaa4c12ab16418b8e3040a, and 4a4268a0b0a595bd9534cf9c7fda93775a7d8a0d.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203