PoC Monitor
← All CVEs
CVE-2026-89586published 11 Sep 2026 19:44 UTCData: JSON · API

Linux

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

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.2high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= ef2d7392c4ece5c3cd12a6c7ca9366cd8f189aff, < 07975b8daa3b0ab3cbc02cc48ea7bc48fadcec53
  • >= ef2d7392c4ece5c3cd12a6c7ca9366cd8f189aff, < b7b5ab2df325ffbbad7ca2debaa071e024d68cb5
  • >= ef2d7392c4ece5c3cd12a6c7ca9366cd8f189aff, < 07baa310ea3224a7044b1ca84796bb37a235af1f
  • >= ef2d7392c4ece5c3cd12a6c7ca9366cd8f189aff, < 977554ed91b54075fbc0bac536316b4841ef6258
  • >= ef2d7392c4ece5c3cd12a6c7ca9366cd8f189aff, < 04e2befe25792f2e90097f284d7e86fc6bcfe928
  • >= ef2d7392c4ece5c3cd12a6c7ca9366cd8f189aff, < c2e3dccd6870659851eaa4c12ab16418b8e3040a
  • >= ef2d7392c4ece5c3cd12a6c7ca9366cd8f189aff, < 4a4268a0b0a595bd9534cf9c7fda93775a7d8a0d
  • >= ef2d7392c4ece5c3cd12a6c7ca9366cd8f189aff, < 79cce911e623c0baa0fde307ce3a434e084b881a

Fixed in 07975b8daa3b0ab3cbc02cc48ea7bc48fadcec53, b7b5ab2df325ffbbad7ca2debaa071e024d68cb5, 07baa310ea3224a7044b1ca84796bb37a235af1f, 977554ed91b54075fbc0bac536316b4841ef6258, 04e2befe25792f2e90097f284d7e86fc6bcfe928, c2e3dccd6870659851eaa4c12ab16418b8e3040a, 4a4268a0b0a595bd9534cf9c7fda93775a7d8a0d, 79cce911e623c0baa0fde307ce3a434e084b881a

Linux Linux
  • 4.9

Fixed in 0, 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.109, 6.18.50, 7.2.4, 7.3

Mitigation

Upgrade Linux to 07975b8daa3b0ab3cbc02cc48ea7bc48fadcec53 or b7b5ab2df325ffbbad7ca2debaa071e024d68cb5 or 07baa310ea3224a7044b1ca84796bb37a235af1f or 977554ed91b54075fbc0bac536316b4841ef6258 or 04e2befe25792f2e90097f284d7e86fc6bcfe928 or c2e3dccd6870659851eaa4c12ab16418b8e3040a or 4a4268a0b0a595bd9534cf9c7fda93775a7d8a0d or 79cce911e623c0baa0fde307ce3a434e084b881a or later.

Upgrade Linux to 0 or 5.10.270 or 5.15.221 or 6.1.188 or 6.6.157 or 6.12.109 or 6.18.50 or 7.2.4 or 7.3 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published11 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.