LiveActive security incident?Get immediate response
CVE Record

CVE-2013-2140: The dispatch_discard_io function in drivers/block/xen-blkback/blkback.c in the Xen blkback implementation i...

The dispatch_discard_io function in drivers/block/xen-blkback/blkback.c in the Xen blkback implementation in the Linux kernel before 3.10.5 allows guest OS users to cause a denial of service (data loss) via filesystem write operations on a read-only disk that supports the (1) BLKIF_OP_DISCARD (aka discard or TRIM) or (2) SCSI UNMAP feature.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This issue affects Linux Xen block backend handling for virtual machines. A guest user could trigger discard/TRIM or SCSI UNMAP behavior against a read-only virtual disk that supports those features, causing denial of service through data loss. The main business concern is integrity loss in Xen environments, especially where untrusted guests share infrastructure. Exposure appears limited to Xen hosts using affected Linux kernel blkback code with guest-accessible read-only disks that support discard/TRIM or SCSI UNMAP. Non-Xen systems, non-blkback storage paths, or disks without these features are not indicated by the provided sources. Prioritize remediation for shared or multi-tenant Xen platforms and systems using read-only shared virtual disks. The issue is older and not KEV-listed in the bundle, but potential data loss makes it operationally important where the affected configuration exists. Mitigation focus: Identify Xen hosts running Linux kernel versions before 3.10.5 or vendor backports lacking the fix.; Apply vendor kernel updates from Canonical, distribution advisories, or kernels containing the referenced upstream commit.; Review Xen guest disk configurations for read-only disks exposing discard/TRIM or SCSI UNMAP..

Prepared

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-2013-2140 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
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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