From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2025-21793: spi: sn-f-ospi: Fix division by zero
Date: Wed, 26 Feb 2025 18:17:49 -0800 [thread overview]
Message-ID: <2025022609-CVE-2025-21793-2c1e@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
spi: sn-f-ospi: Fix division by zero
When there is no dummy cycle in the spi-nor commands, both dummy bus cycle
bytes and width are zero. Because of the cpu's warning when divided by
zero, the warning should be avoided. Return just zero to avoid such
calculations.
The Linux kernel CVE team has assigned CVE-2025-21793 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.2 with commit 1b74dd64c8612619e399e5a31da79a3636914495 and fixed in 6.6.79 with commit 966328191b4c389c0f2159fa242915f51cbc1679
Issue introduced in 6.2 with commit 1b74dd64c8612619e399e5a31da79a3636914495 and fixed in 6.12.16 with commit 4df6f005bef04a3dd16c028124a1b5684db3922b
Issue introduced in 6.2 with commit 1b74dd64c8612619e399e5a31da79a3636914495 and fixed in 6.13.4 with commit 7434135553bc03809a55803ee6a8dcaae6240d55
Issue introduced in 6.2 with commit 1b74dd64c8612619e399e5a31da79a3636914495 and fixed in 6.14-rc3 with commit 3588b1c0fde2f58d166e3f94a5a58d64b893526c
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-21793
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/spi/spi-sn-f-ospi.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/966328191b4c389c0f2159fa242915f51cbc1679
https://git.kernel.org/stable/c/4df6f005bef04a3dd16c028124a1b5684db3922b
https://git.kernel.org/stable/c/7434135553bc03809a55803ee6a8dcaae6240d55
https://git.kernel.org/stable/c/3588b1c0fde2f58d166e3f94a5a58d64b893526c
reply other threads:[~2025-02-27 2:19 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=2025022609-CVE-2025-21793-2c1e@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.