Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-68773spi: fsl-cpm: Check length parity before switching to 16 bit mode

Description

In the Linux kernel, the following vulnerability has been resolved: spi: fsl-cpm: Check length parity before switching to 16 bit mode Commit fc96ec826bce ("spi: fsl-cpm: Use 16 bit mode for large transfers with even size") failed to make sure that the size is really even before switching to 16 bit mode. Until recently the problem went unnoticed because kernfs uses a pre-allocated bounce buffer of size PAGE_SIZE for reading EEPROM. But commit 8ad6249c51d0 ("eeprom: at25: convert to spi-mem API") introduced an additional dynamically allocated bounce buffer whose size is exactly the size of the transfer, leading to a buffer overrun in the fsl-cpm driver when that size is odd. Add the missing length parity verification and remain in 8 bit mode when the length is not even.

Timeline

  1. ID reserved

    By Linux

  2. · 20 days later

    Published

  3. · 10 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 60afe299bb541a928ba39bcb4ae8d3e428d1c5a5 – < c8f1d35076b78df61ace737e41cc1f4b7b63236c
    • affected 4badd33929c05ed314794b95f1af1308f7222be8 – < 9c34a4a2ead00979d203a8c16bea87f0ef5291d8
    • affected 7f6738e003b364783f3019fdf6e7645bc8dd1643 – < 837a23a11e0f734f096c7c7b0778d0e625e3dc87
    • affected fc96ec826bced75cc6b9c07a4ac44bbf651337ab – < 3dd6d01384823e1bd8602873153d6fc4337ac4fe
    • affected fc96ec826bced75cc6b9c07a4ac44bbf651337ab – < 743cebcbd1b2609ec5057ab474979cef73d1b681
    • affected fc96ec826bced75cc6b9c07a4ac44bbf651337ab – < be0b613198e6bfa104ad520397cab82ad3ec1771
    • affected fc96ec826bced75cc6b9c07a4ac44bbf651337ab – < 1417927df8049a0194933861e9b098669a95c762
    • affected 42c04316d9275ec267d36e5e9064cd56c9884148
    • affected dc120f2d35b030390a2bc0f94dd5f37e900cae91
    • affected b558275c1b040f0e5aa56c862241f9212b6118c3
    • affected b9d9e8856f1c83e4277403f9b4c369b322ebcb12
    • affected 36a6d0f66c874666caf4e8be155b1be30f6231be
    • affected 5.10.181 – < 5.10.248
    • affected 5.15.114 – < 5.15.198
    • affected 6.1.29 – < 6.1.160
    • affected 4.14.316 – < 4.15
    • affected 4.19.284 – < 4.20
    • affected 5.4.244 – < 5.5
    • affected 6.2.16 – < 6.3
    • affected 6.3.3 – < 6.4
  • Linux · Linux

    • affected 6.4
    • unaffected < 6.4
    • unaffected 5.10.248 – ≤ 5.10.*
    • unaffected 5.15.198 – ≤ 5.15.*
    • unaffected 6.1.160 – ≤ 6.1.*
    • unaffected 6.6.120 – ≤ 6.6.*
    • unaffected 6.12.64 – ≤ 6.12.*
    • unaffected 6.18.3 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-68773 badge
[![CVE-2025-68773](https://cveledger.app/badge/CVE-2025-68773.svg)](https://cveledger.app/cve/CVE-2025-68773)

Record last updated .