LiveActive security incident?Get immediate response
CVE Record

CVE-2024-27059: USB: usb-storage: Prevent divide-by-0 error in isd200_ata_command

In the Linux kernel, the following vulnerability has been resolved: USB: usb-storage: Prevent divide-by-0 error in isd200_ata_command The isd200 sub-driver in usb-storage uses the HEADS and SECTORS values in the ATA ID information to calculate cylinder and head values when creating a CDB for READ or WRITE commands. The calculation involves division and modulus operations, which will cause a crash if either of these values is 0. While this never happens with a genuine device, it could happen with a flawed or subversive emulation, as reported by the syzbot fuzzer. Protect against this possibility by refusing to bind to the device if either the ATA_ID_HEADS or ATA_ID_SECTORS value in the device's ID information is 0. This requires isd200_Initialization() to return a negative error code when initialization fails; currently it always returns 0 (even when there is an error).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-27059 is a Linux kernel flaw in a USB storage sub-driver. A malformed or hostile USB storage emulation can report impossible disk geometry values and trigger a divide-by-zero crash. The main business risk is local denial of service on systems that accept USB mass-storage devices.

Executive priority

Treat this as a practical hardening and patch-management item, not an emergency internet-scale issue. Prioritize systems where untrusted users can attach USB devices or where USB devices are passed into production Linux hosts or appliances.

Technical view

The Linux usb-storage isd200 sub-driver used ATA ID HEADS and SECTORS values in division and modulus operations while building READ or WRITE CDBs. If either value is zero, the kernel can crash. The fix refuses to bind when those ATA ID fields are zero.

Likely exposure

Exposure is most likely on Linux systems using affected kernel versions with USB mass-storage support and access to physical, virtual, or emulated USB devices. Internet-facing exposure is not indicated by the sources.

Exploitation context

The CVE record says syzbot found the crash condition through fuzzing and that genuine devices should not normally produce these values. KEV is false, and the supplied sources do not show active exploitation.

Researcher notes

The evidence supports a kernel denial-of-service condition caused by invalid ATA ID geometry values in isd200 initialization. No CVSS, CWE, or exploit-in-the-wild evidence is provided. The patch behavior is defensive binding refusal, not input correction later in command handling.

Mitigation direction

  • Update affected Linux kernels to a fixed stable release or vendor-packaged kernel.
  • Apply Debian LTS or other distribution kernel updates where applicable.
  • Restrict untrusted USB mass-storage attachment on sensitive systems.
  • Check vendor advisories for embedded or appliance products using affected Linux kernels.

Validation and detection

  • Inventory Linux kernel versions against the affected and fixed ranges in the CVE record.
  • Confirm deployed kernel packages include the referenced stable kernel fixes.
  • Review USB exposure on servers, kiosks, appliances, and virtualized environments.
  • Verify distribution or vendor advisories cover the product build in use.
Prepared
Confidence
high
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-27059 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
3ADP providers
12Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2unaffected
LinuxLinux2.6.12, 0, 4.19.312, 5.4.274, 5.10.215, 5.15.154, 6.1.84, 6.6.24, 6.7.12, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.