From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2025-21690: scsi: storvsc: Ratelimit warning logs to prevent VM denial of service
Date: Mon, 10 Feb 2025 16:58:58 +0100 [thread overview]
Message-ID: <2025021055-CVE-2025-21690-e8ec@gregkh> (raw)
Description
===========
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.
The Linux kernel CVE team has assigned CVE-2025-21690 to this issue.
Affected and fixed versions
===========================
Fixed in 5.15.178 with commit 81d4dd05c412ba04f9f6b85b718e6da833be290c
Fixed in 6.1.128 with commit 182a4b7c731e95c08cb47f14b87a272b6ab2b2da
Fixed in 6.6.75 with commit 088bde862f8d3d0fc52e40e66a0484a246837087
Fixed in 6.12.12 with commit 01d1ebdab9ccb73c952e1666a8a80abd194dbc55
Fixed in 6.13.1 with commit d0f0af1bafef33b3e2aa8c3a4ef44db48df9b0ea
Fixed in 6.14-rc1 with commit d2138eab8cde61e0e6f62d0713e45202e8457d6d
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2025-21690
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/scsi/storvsc_drv.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/81d4dd05c412ba04f9f6b85b718e6da833be290c
https://git.kernel.org/stable/c/182a4b7c731e95c08cb47f14b87a272b6ab2b2da
https://git.kernel.org/stable/c/088bde862f8d3d0fc52e40e66a0484a246837087
https://git.kernel.org/stable/c/01d1ebdab9ccb73c952e1666a8a80abd194dbc55
https://git.kernel.org/stable/c/d0f0af1bafef33b3e2aa8c3a4ef44db48df9b0ea
https://git.kernel.org/stable/c/d2138eab8cde61e0e6f62d0713e45202e8457d6d
reply other threads:[~2025-02-10 15:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025021055-CVE-2025-21690-e8ec@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.