LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

A Linux kernel SPI driver can overrun a buffer during certain odd-length transfers. The issue appears specific to systems using the Freescale CPM SPI driver path, common in embedded environments. Public sources do not provide CVSS, CWE, or confirmed exploitation.

Executive priority

Treat as a targeted embedded and industrial Linux kernel issue. Prioritize asset identification and vendor patch tracking over emergency enterprise-wide response unless affected hardware is confirmed.

Technical view

The fsl-cpm SPI driver switched to 16-bit transfer mode without verifying even transfer length. After the at25 EEPROM driver moved to the spi-mem API, exact-size dynamic bounce buffers could be overrun on odd-length transfers. Stable kernel commits add the missing parity check and keep odd lengths in 8-bit mode.

Likely exposure

Likely exposure is embedded Linux systems using the fsl-cpm SPI driver, especially at25 EEPROM access through spi-mem. General-purpose Linux servers are unlikely to be affected unless this hardware and driver path are present. Siemens has a related advisory, so industrial deployments should check vendor product status.

Exploitation context

The provided sources do not report active exploitation, public exploit code, or KEV listing. The issue is a kernel buffer overrun, but reachable conditions appear hardware-driver specific and tied to odd-length SPI transfers.

Researcher notes

Evidence supports a length-parity bug leading to driver-side buffer overrun. Exploitability details, privilege requirements, and impact severity are not established in the supplied sources. Avoid assuming remote reachability or broad Linux exposure.

Mitigation direction

  • Apply the relevant Linux stable kernel fix for your maintained branch.
  • Check Siemens SSA-019113 for affected industrial products and vendor-specific guidance.
  • Prioritize embedded systems using Freescale CPM SPI or at25 EEPROM components.
  • If patching is delayed, consult vendor guidance for supported compensating controls.

Validation and detection

  • Inventory kernels and identify systems loading or building the fsl-cpm SPI driver.
  • Check whether at25 EEPROM devices use the spi-mem API on affected systems.
  • Verify the relevant stable fix commit is present in deployed kernel sources.
  • Review Siemens product advisories for matching product names and versions.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-68773 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux60afe299bb541a928ba39bcb4ae8d3e428d1c5a5, 4badd33929c05ed314794b95f1af1308f7222be8, 7f6738e003b364783f3019fdf6e7645bc8dd1643, fc96ec826bced75cc6b9c07a4ac44bbf651337ab, fc96ec826bced75cc6b9c07a4ac44bbf651337ab, fc96ec826bced75cc6b9c07a4ac44bbf651337ab, fc96ec826bced75cc6b9c07a4ac44bbf651337ab, 42c04316d9275ec267d36e5e9064cd56c9884148, dc120f2d35b030390a2bc0f94dd5f37e900cae91, b558275c1b040f0e5aa56c862241f9212b6118c3, b9d9e8856f1c83e4277403f9b4c369b322ebcb12, 36a6d0f66c874666caf4e8be155b1be30f6231be, 5.10.181, 5.15.114, 6.1.29, 4.14.316, 4.19.284, 5.4.244, 6.2.16, 6.3.3unaffected
LinuxLinux6.4, 0, 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.3, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.