Skip to content
Fencer Vulns
medium 5.5

CVE-2025-21793 json

spi: sn-f-ospi: Fix division by zero

published 2025-02-27 20 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-5131

cvss
5.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 12%
public exploits
0
none known

Summary

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.

Patch / fix

  • Linux Linux 6.6.79, 6.12.16, 6.13.4, 6.14
  • linux Debian 14, Debian 13 6.12.16-1

debian advisories DEBIAN-CVE-2025-21793

  • linux Ubuntu 24.04 LTS 6.8.0-78.78
  • linux-aws Ubuntu 24.04 LTS 6.8.0-1035.37
  • linux-gcp Ubuntu 24.04 LTS 6.8.0-1036.38
  • linux-gke Ubuntu 24.04 LTS 6.8.0-1032.36
  • linux-ibm Ubuntu 24.04 LTS 6.8.0-1033.33
  • linux-azure Ubuntu 24.04 LTS 6.8.0-1034.39
  • linux-gkeop Ubuntu 24.04 LTS 6.8.0-1019.21
  • linux-raspi Ubuntu 24.04 LTS 6.8.0-1035.39

ubuntu advisories UBUNTU-CVE-2025-21793

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-coco SLE Module for Confidential Computing Technical Preview 15 SP6 6.4.0-15061.21.coco15sp6.1
  • kernel-syms-coco SLE Module for Confidential Computing Technical Preview 15 SP6 6.4.0-15061.21.coco15sp6.1
  • kernel-coco_debug SLE Module for Confidential Computing Technical Preview 15 SP6 6.4.0-15061.21.coco15sp6.1
  • kernel-source-coco SLE Module for Confidential Computing Technical Preview 15 SP6 6.4.0-15061.21.coco15sp6.1
  • kernel-source Linux Micro 6.1, Linux Micro 6.0 6.4.0-28.1
  • kernel-default Linux Micro 6.1, Linux Micro 6.0 6.4.0-28.1
  • kernel-kvmsmall Linux Micro 6.1, Linux Micro 6.0 6.4.0-28.1
  • kernel-default-base Linux Micro 6.1, Linux Micro 6.0 6.4.0-28.1.21.6

suse advisories SUSE-SU-2025:01919-1SUSE-SU-2025:20192-1SUSE-SU-2025:20270-1SUSE-SU-2025:20190-1SUSE-SU-2025:20260-1SUSE-SU-2025:1180-1

  • kernel Azure Linux 3.0 6.6.79.1-1

azure linux advisories AZL-57761

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-21793 updated cvss 5.5

kernel: spi: sn-f-ospi: Fix division by zero

  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
13 mo ago

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Linux Linux

Classification

Weakness
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.