Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
  • Fixed version: Linux Linux 1417927df8049a0194933861e9b098669a95c762, 3dd6d01384823e1bd8602873153d6fc4337ac4fe, 4.15; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1.

Low priority for now. Upgrade to Linux Linux 1417927df8049a0194933861e9b098669a95c762, 3dd6d01384823e1bd8602873153d6fc4337ac4fe, 4.15; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Jan 13, 2026
Updated
Oct 15, 2026
EPSS
0.2% · 14th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-68773

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 42c04316d9275ec267d36e5e9064cd56c9884148, dc120f2d35b030390a2bc0f94dd5f37e900cae91, b558275c1b040f0e5aa56c862241f9212b6118c3, b9d9e8856f1c83e4277403f9b4c369b322ebcb12, 36a6d0f66c874666caf4e8be155b1be30f6231be, 6.4affected
    • 60afe299bb541a928ba39bcb4ae8d3e428d1c5a5 and later · before c8f1d35076b78df61ace737e41cc1f4b7b63236caffected · git
    • 4badd33929c05ed314794b95f1af1308f7222be8 and later · before 9c34a4a2ead00979d203a8c16bea87f0ef5291d8affected · git
    • 7f6738e003b364783f3019fdf6e7645bc8dd1643 and later · before 837a23a11e0f734f096c7c7b0778d0e625e3dc87affected · git
    • fc96ec826bced75cc6b9c07a4ac44bbf651337ab and later · before 3dd6d01384823e1bd8602873153d6fc4337ac4feaffected · git
    • fc96ec826bced75cc6b9c07a4ac44bbf651337ab and later · before 743cebcbd1b2609ec5057ab474979cef73d1b681affected · git
    • fc96ec826bced75cc6b9c07a4ac44bbf651337ab and later · before be0b613198e6bfa104ad520397cab82ad3ec1771affected · git
    • fc96ec826bced75cc6b9c07a4ac44bbf651337ab and later · before 1417927df8049a0194933861e9b098669a95c762affected · git
    • 5.10.181 and later · before 5.10.248affected · semver
    • 5.15.114 and later · before 5.15.198affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.162-16.1.162-1
Debian:13linuxbefore 6.12.69-16.12.69-1
Debian:14linuxbefore 6.18.3-16.18.3-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-71070Jan 13, 2026 · ublk: clean up user copy references on ublk server exit
    31Monitor
  • ← EarlierCVE-2025-68770Jan 13, 2026 · bnxt_en: Fix XDP_TX path
    30Monitor
  • Later →CVE-2025-68775Jan 13, 2026 · net/handshake: duplicate handshake cancellations leak socket
    39Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1417927df8049a0194933861e9b098669a95c762Vendor (CNA)
Linux Linux3dd6d01384823e1bd8602873153d6fc4337ac4feVendor (CNA)
Linux Linux4.15Vendor (CNA)
Linux Linux4.20Vendor (CNA)
Linux Linux5.10.248Vendor (CNA)
Linux Linux5.15.198Vendor (CNA)
Linux Linux5.5Vendor (CNA)
Linux Linux6.1.160Vendor (CNA)
Linux Linux6.3Vendor (CNA)
Linux Linux6.4Vendor (CNA)
Linux Linux743cebcbd1b2609ec5057ab474979cef73d1b681Vendor (CNA)
Linux Linux837a23a11e0f734f096c7c7b0778d0e625e3dc87Vendor (CNA)
Linux Linux9c34a4a2ead00979d203a8c16bea87f0ef5291d8Vendor (CNA)
Linux Linuxbe0b613198e6bfa104ad520397cab82ad3ec1771Vendor (CNA)
Linux Linuxc8f1d35076b78df61ace737e41cc1f4b7b63236cVendor (CNA)
azl3 kernel 6.6.119.3-3 on Azure Linux 3.06.6.121.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records