SCSI device disruption via unchecked group number
Published May 24, 2025 · Updated May 24, 2025
Type confusion in maboroshinokiseki scsir 0.2.0 allows local users to disrupt SCSI device operation via an oversized group number. WriteSameCommand::group_number accepts any u8 and copies it into the command without enforcing the device's smaller 5- or 6-bit field limit. Exploitation requires code execution on a host attached to a susceptible SCSI device, and the published impact is limited to device availability.
Summary
What happened
Type confusion in maboroshinokiseki scsir 0.2.0 allows local users to disrupt SCSI device operation via an oversized group number. WriteSameCommand::group_number accepts any u8 and copies it into the command without enforcing the device's smaller 5- or 6-bit field limit. Exploitation requires code execution on a host attached to a susceptible SCSI device, and the published impact is limited to device availability.
The record
- CVE
- CVE-2025-48756
- Published
- May 24, 2025
- Updated
- May 24, 2025
- Vendor
- maboroshinokiseki
- Product
- scsir
- Classifications
- CWE-843, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 24, 2025CVE publishedPublication date reported by the CVE source.
- May 24, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.2.0
What conditions does exploitation require?
What is affected?
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
- WriteSameCommand oversized group-number proof of conceptproof of concept · unverified
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