Storage-service interruption via resource-shutdown race
Published Oct 7, 2024 · Updated Dec 11, 2024
A race condition in Solidigm DC SSD firmware allows local users to cause a storage-service interruption during resource shutdown. The firmware resource-shutdown path permits a race between concurrent operations; Solidigm has not identified the resource or operations. Exploitation requires local access and high privileges, and the reported consequence is availability loss only.
Summary
What happened
A race condition in Solidigm DC SSD firmware allows local users to cause a storage-service interruption during resource shutdown. The firmware resource-shutdown path permits a race between concurrent operations; Solidigm has not identified the resource or operations. Exploitation requires local access and high privileges, and the reported consequence is availability loss only.
The record
- CVE
- CVE-2024-47974
- Published
- Oct 7, 2024
- Updated
- Dec 11, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-362, T1499
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Oct 7, 2024CVE publishedPublication date reported by the CVE source.
- Dec 11, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo