CVE-2025-21690: scsi: storvsc: Ratelimit warning logs to prevent VM denial of service
In the Linux kernel, the following vulnerability has been resolved:
scsi: storvsc: Ratelimit warning logs to prevent VM denial of service
If there's a persistent error in the hypervisor, the SCSI warning for
failed I/O can flood the kernel log and max out CPU utilization,
preventing troubleshooting from the VM side. Ratelimit the warning so
it doesn't DoS the VM.
Security readout for executives and security teams
Plain-English summary
A Linux VM can become hard to troubleshoot or effectively unavailable if persistent storage errors cause the kernel to flood logs and consume CPU. The fix rate-limits the warning message. This is mainly an availability issue, not a data theft or integrity issue.
Executive priority
Treat this as a moderate availability risk. Patch through normal kernel maintenance, but prioritize critical Linux VMs where storage faults could block operations or incident response.
Technical view
CVE-2025-21690 affects the Linux kernel SCSI storvsc path. Repeated failed I/O warnings can exhaust CPU through kernel log flooding when a persistent hypervisor-side error exists. The resolved change rate-limits the warning. CVSS is 5.5 with local access, low complexity, low privileges, and high availability impact.
Likely exposure
Exposure is most likely in Linux virtual machines using the storvsc storage driver in hypervisor-backed storage environments. The source lists affected Linux kernel versions and stable branch fixes, but distribution exposure depends on vendor kernel backports.
Exploitation context
The source bundle does not show public exploitation, and KEV status is false. Practical impact appears tied to persistent hypervisor or storage error conditions that trigger repeated failed I/O warnings inside the VM.
Researcher notes
The core issue is uncontrolled warning emission under repeated I/O failure, mapped to CWE-770. Evidence supports availability impact only. Sources do not establish remote exploitation, data exposure, or a standalone attacker-triggerable path beyond the stated local CVSS vector.
Mitigation direction
Apply vendor Linux kernel updates that include the stable storvsc rate-limit fix.
Review distribution advisories, including Debian LTS if applicable.
Prioritize VMs where storage availability or troubleshooting access is business-critical.
Monitor for excessive kernel logging and CPU saturation from failed I/O warnings.
Check vendor guidance before using nonstandard kernel builds or manual backports.
Validation and detection
Inventory Linux VMs using the storvsc storage driver.
Compare running kernel versions against vendor advisories and fixed stable commits.
Confirm installed kernel packages include the storvsc warning rate-limit change.
Review kernel logs for repeated failed I/O warning floods.
Validate CPU monitoring alerts cover log-flood-driven saturation.
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.
cwe · low confidence lookup
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-770 · source CWE mapping
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.