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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version b9d9e8856f1c83e4277403f9b4c369b322ebcb12version 6.4≥ 6.3.3 and < 6.4≥ 6.2.16 and < 6.3≥ 5.4.244 and < 5.5≥ 4.19.284 and < 4.20≥ 4.14.316 and < 4.15≥ 6.1.29 and < 6.1.160 and 13 more≥ 5.15.114 and < 5.15.198≥ 5.10.181 and < 5.10.248version 36a6d0f66c874666caf4e8be155b1be30f6231be≥ 60afe299bb541a928ba39bcb4ae8d3e428d1c5a5 and < c8f1d35076b78df61ace737e41cc1f4b7b63236cversion b558275c1b040f0e5aa56c862241f9212b6118c3version dc120f2d35b030390a2bc0f94dd5f37e900cae91version 42c04316d9275ec267d36e5e9064cd56c9884148≥ fc96ec826bced75cc6b9c07a4ac44bbf651337ab and < 1417927df8049a0194933861e9b098669a95c762≥ fc96ec826bced75cc6b9c07a4ac44bbf651337ab and < be0b613198e6bfa104ad520397cab82ad3ec1771≥ fc96ec826bced75cc6b9c07a4ac44bbf651337ab and < 743cebcbd1b2609ec5057ab474979cef73d1b681≥ fc96ec826bced75cc6b9c07a4ac44bbf651337ab and < 3dd6d01384823e1bd8602873153d6fc4337ac4fe≥ 7f6738e003b364783f3019fdf6e7645bc8dd1643 and < 837a23a11e0f734f096c7c7b0778d0e625e3dc87≥ 4badd33929c05ed314794b95f1af1308f7222be8 and < 9c34a4a2ead00979d203a8c16bea87f0ef5291d8 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Deferred
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
11 on the record
- git.kernel.org/stable/c/1417927df8049a0194933861e9b098669a95c762
- git.kernel.org/stable/c/837a23a11e0f734f096c7c7b0778d0e625e3dc87
- git.kernel.org/stable/c/9c34a4a2ead00979d203a8c16bea87f0ef5291d8
- cert-portal.siemens.com/productcert/html/ssa-457936.html
- github.com/advisories/GHSA-wrfv-x882-24r3
- git.kernel.org/stable/c/c8f1d35076b78df61ace737e41cc1f4b7b63236c
- nvd.nist.gov/vuln/detail/CVE-2025-68773
- cert-portal.siemens.com/productcert/html/ssa-019113.html
- git.kernel.org/stable/c/be0b613198e6bfa104ad520397cab82ad3ec1771
- git.kernel.org/stable/c/3dd6d01384823e1bd8602873153d6fc4337ac4fe
- git.kernel.org/stable/c/743cebcbd1b2609ec5057ab474979cef73d1b681
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 13h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 13h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-68773 is "spi: fsl-cpm: Check length parity before switching to 16 bit mode", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.