CVE-2025-21845

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-03-12. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

mtd: spi-nor: sst: Fix SST write failure

'commit 18bcb4aa54ea ("mtd: spi-nor: sst: Factor out common write operation to sst_nor_write_data()")' introduced a bug where only one byte of data is written, regardless of the number of bytes passed to sst_nor_write_data(), causing a kernel crash during the write operation. Ensure the correct number of bytes are written as passed to sst_nor_write_data().

Call trace: [ 57.400180] ------------[ cut here ]------------ [ 57.404842] While writing 2 byte written 1 bytes [ 57.409493] WARNING: CPU: 0 PID: 737 at drivers/mtd/spi-nor/sst.c:187 sst_nor_write_data+0x6c/0x74 [ 57.418464] Modules linked in: [ 57.421517] CPU: 0 UID: 0 PID: 737 Comm: mtd_debug Not tainted 6.12.0-g5ad04afd91f9 #30 [ 57.429517] Hardware name: Xilinx Versal A2197 Processor board revA - x-prc-02 revA (DT) [ 57.437600] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 57.444557] pc : sst_nor_write_data+0x6c/0x74 [ 57.448911] lr : sst_nor_write_data+0x6c/0x74 [ 57.453264] sp : ffff80008232bb40 [ 57.456570] x29: ffff80008232bb40 x28: 0000000000010000 x27: 0000000000000001 [ 57.463708] x26: 000000000000ffff x25: 0000000000000000 x24: 0000000000000000 [ 57.470843] x23: 0000000000010000 x22: ffff80008232bbf0 x21: ffff000816230000 [ 57.477978] x20: ffff0008056c0080 x19: 0000000000000002 x18: 0000000000000006 [ 57.485112] x17: 0000000000000000 x16: 0000000000000000 x15: ffff80008232b580 [ 57.492246] x14: 0000000000000000 x13: ffff8000816d1530 x12: 00000000000004a4 [ 57.499380] x11: 000000000000018c x10: ffff8000816fd530 x9 : ffff8000816d1530 [ 57.506515] x8 : 00000000fffff7ff x7 : ffff8000816fd530 x6 : 0000000000000001 [ 57.513649] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000000000 [ 57.520782] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0008049b0000 [ 57.527916] Call trace: [ 57.530354] sst_nor_write_data+0x6c/0x74 [ 57.534361] sst_nor_write+0xb4/0x18c [ 57.538019] mtd_write_oob_std+0x7c/0x88 [ 57.541941] mtd_write_oob+0x70/0xbc [ 57.545511] mtd_write+0x68/0xa8 [ 57.548733] mtdchar_write+0x10c/0x290 [ 57.552477] vfs_write+0xb4/0x3a8 [ 57.555791] ksys_write+0x74/0x10c [ 57.559189] __arm64_sys_write+0x1c/0x28 [ 57.563109] invoke_syscall+0x54/0x11c [ 57.566856] el0_svc_common.constprop.0+0xc0/0xe0 [ 57.571557] do_el0_svc+0x1c/0x28 [ 57.574868] el0_svc+0x30/0xcc [ 57.577921] el0t_64_sync_handler+0x120/0x12c [ 57.582276] el0t_64_sync+0x190/0x194 [ 57.585933] ---[ end trace 0000000000000000 ]---

[[email protected]: add Cc stable tag]

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

March 12, 2025

Last Modified

June 1, 2026

Advisory Details (4)

Auto-updated May 17, 2026
No patch confirmed yet.
generic

mtd: spi-nor: sst: Fix SST write failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f7c14993dc2f1eca661975c0ff90a6e2098ecd41
generic

mtd: spi-nor: sst: Fix SST write failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bb1accc7e0f688886f0c634f2e878b8ac4ee6a58
generic

mtd: spi-nor: sst: Fix SST write failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9553391f32f8c43e12fc7c04e1035160b5ea20bf
generic

mtd: spi-nor: sst: Fix SST write failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/539bd20352832b9244238a055eb169ccf1c41ff6

Vendor Advisories for CVE-2025-21845(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.12.17—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Data Freshness Timeline

(refreshed 7× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 142 total refreshes for this CVE.

  1. 2026-08-07 16:26 UTCEPSS rescore
  2. 2026-08-06 13:46 UTCEPSS rescore
  3. 2026-08-05 19:16 UTCEPSS rescore
  4. 2026-08-04 15:09 UTCEPSS rescore
  5. 2026-08-04 10:37 UTCEPSS rescore
  6. 2026-08-03 10:35 UTCEPSS rescore
  7. 2026-08-02 02:25 UTCEPSS rescore
  8. 2026-08-01 04:15 UTCEPSS rescore
  9. 2026-07-30 16:27 UTCEPSS rescore
  10. 2026-07-30 01:29 UTCEPSS rescore
  11. 2026-07-28 15:35 UTCEPSS rescore
  12. 2026-07-28 00:25 UTCOSV refresh
  13. 2026-07-27 14:12 UTCEPSS rescore
  14. 2026-07-26 14:53 UTCEPSS rescore
  15. 2026-07-25 14:17 UTCEPSS rescore
  16. 2026-07-24 14:17 UTCEPSS rescore
  17. 2026-07-23 14:17 UTCEPSS rescore
  18. 2026-07-23 02:50 UTCEG score recompute
  19. 2026-07-22 14:07 UTCEPSS rescore
  20. 2026-07-22 14:07 UTCEPSS rescore
  21. 2026-07-21 15:24 UTCEPSS rescore
  22. 2026-07-20 17:07 UTCEPSS rescore
  23. 2026-07-19 14:30 UTCEPSS rescore
  24. 2026-07-19 14:30 UTCEPSS rescore
  25. 2026-07-19 02:28 UTCEPSS rescore
Show 75 more
  1. 2026-07-19 02:28 UTCEPSS rescore
  2. 2026-07-18 10:03 UTCEPSS rescore
  3. 2026-07-16 17:02 UTCEPSS rescore
  4. 2026-07-15 16:57 UTCEPSS rescore
  5. 2026-07-15 16:57 UTCEPSS rescore
  6. 2026-07-15 01:59 UTCEPSS rescore
  7. 2026-07-13 22:29 UTCEPSS rescore
  8. 2026-07-13 22:29 UTCEPSS rescore
  9. 2026-07-13 06:12 UTCEPSS rescore
  10. 2026-07-13 06:12 UTCEPSS rescore
  11. 2026-07-12 05:46 UTCEPSS rescore
  12. 2026-07-12 05:46 UTCEPSS rescore
  13. 2026-07-11 08:27 UTCEPSS rescore
  14. 2026-07-11 08:26 UTCEPSS rescore
  15. 2026-07-10 16:52 UTCOSV refresh
  16. 2026-07-09 19:09 UTCEPSS rescore
  17. 2026-07-08 15:14 UTCEPSS rescore
  18. 2026-07-07 13:45 UTCEPSS rescore
  19. 2026-07-06 16:26 UTCEPSS rescore
  20. 2026-07-06 02:22 UTCEPSS rescore
  21. 2026-07-06 02:22 UTCEPSS rescore
  22. 2026-07-05 02:30 UTCEPSS rescore
  23. 2026-07-04 06:30 UTCEPSS rescore
  24. 2026-07-01 15:06 UTCEPSS rescore
  25. 2026-06-30 23:21 UTCEPSS rescore
  26. 2026-06-30 23:21 UTCEPSS rescore
  27. 2026-06-29 14:06 UTCEPSS rescore
  28. 2026-06-28 14:07 UTCEPSS rescore
  29. 2026-06-28 14:07 UTCEPSS rescore
  30. 2026-06-28 04:55 UTCEPSS rescore
  31. 2026-06-28 04:55 UTCEPSS rescore
  32. 2026-06-27 03:08 UTCEPSS rescore
  33. 2026-06-27 03:08 UTCEPSS rescore
  34. 2026-06-25 13:49 UTCEPSS rescore
  35. 2026-06-25 13:49 UTCEPSS rescore
  36. 2026-06-24 14:04 UTCEPSS rescore
  37. 2026-06-24 14:04 UTCEPSS rescore
  38. 2026-06-23 21:32 UTCEPSS rescore
  39. 2026-06-23 21:32 UTCEPSS rescore
  40. 2026-06-22 14:25 UTCEPSS rescore
  41. 2026-06-22 14:25 UTCEPSS rescore
  42. 2026-06-22 00:25 UTCOSV refresh
  43. 2026-06-21 14:56 UTCEPSS rescore
  44. 2026-06-21 14:56 UTCEPSS rescore
  45. 2026-06-21 01:59 UTCEPSS rescore
  46. 2026-06-21 01:59 UTCEPSS rescore
  47. 2026-06-19 19:25 UTCEPSS rescore
  48. 2026-06-19 19:25 UTCEPSS rescore
  49. 2026-06-18 17:52 UTCEPSS rescore
  50. 2026-06-18 17:52 UTCEPSS rescore
  51. 2026-06-17 17:52 UTCEPSS rescore
  52. 2026-06-16 17:52 UTCEPSS rescore
  53. 2026-06-16 17:52 UTCEPSS rescore
  54. 2026-06-15 17:48 UTCEPSS rescore
  55. 2026-06-14 23:17 UTCEPSS rescore
  56. 2026-06-13 22:59 UTCEPSS rescore
  57. 2026-06-12 23:11 UTCEPSS rescore
  58. 2026-06-11 13:59 UTCEPSS rescore
  59. 2026-06-10 22:18 UTCEPSS rescore
  60. 2026-06-10 13:22 UTCEPSS rescore
  61. 2026-06-08 14:16 UTCEPSS rescore
  62. 2026-06-08 14:16 UTCEPSS rescore
  63. 2026-06-07 15:24 UTCEPSS rescore
  64. 2026-06-07 15:24 UTCEPSS rescore
  65. 2026-06-06 13:47 UTCEPSS rescore
  66. 2026-06-06 13:47 UTCEPSS rescore
  67. 2026-06-05 22:46 UTCEPSS rescore
  68. 2026-06-05 22:46 UTCEPSS rescore
  69. 2026-06-05 06:10 UTCEPSS rescore
  70. 2026-06-05 06:10 UTCEPSS rescore
  71. 2026-06-04 13:11 UTCEPSS rescore
  72. 2026-06-04 13:11 UTCEPSS rescore
  73. 2026-06-03 16:09 UTCOSV refresh
  74. 2026-06-02 20:12 UTCEPSS rescore
  75. 2026-06-02 20:12 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-21845?
CVE-2025-21845 is a medium vulnerability published on March 12, 2025. In the Linux kernel, the following vulnerability has been resolved: mtd: spi-nor: sst: Fix SST write failure 'commit 18bcb4aa54ea ("mtd: spi-nor: sst: Factor out common write operation to sstnorwrite_data()")' introduced a bug where only one byte of data is written, regardless of the number of…
When was CVE-2025-21845 disclosed?
CVE-2025-21845 was first published in the National Vulnerability Database on March 12, 2025, with the most recent update on June 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-21845 actively exploited?
CVE-2025-21845 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.3% of all scored CVEs.
What is the CVSS score of CVE-2025-21845?
CVE-2025-21845 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-21845?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-21845, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-21845

Explore →

Is Your Infrastructure Affected by CVE-2025-21845?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs