Skip to main content

Linux Kernel CVE-2026-68467

| EUVDEUVD-2026-59089 HIGH
2026-08-15 416baaa9-dc9f-4396-8d5f-8c081fb06d67 GHSA-p34j-xw9f-x58x
7.8
CVSS 3.1 · Vendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Share

Severity by source

Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67) PRIMARY
7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
5.8 MEDIUM

AC:H reflects mandatory specialized hardware and non-DT SPI match path; integrity impact dominates due to possible out-of-bounds SRAM writes; confidentiality and availability impacts are limited.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:L
4.0 AV:L/AC:H/AT:P/PR:L/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N
SUSE
4.4 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Red Hat
5.5 MEDIUM
qualitative

Primary rating from Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67).

CVSS VectorVendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Generated
Aug 17, 2026 - 12:56 vuln.today
CVSS changed
Aug 17, 2026 - 06:22 NVD
7.8 (HIGH)
Patch available
Aug 15, 2026 - 07:20 EUVD
CVE Published
Aug 15, 2026 - 06:19 cve.org
UNKNOWN (no severity yet)
CVE Published
Aug 15, 2026 - 06:19 cve.org
HIGH 7.8

DescriptionCVE.org

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

mtd: mchp23k256: use SPI match data for chip caps

The driver stores chip capacity information in both the OF match table and the SPI id table. Probe currently uses of_device_get_match_data(), so a non-OF SPI modalias match falls back to mchp23k256_caps even when the SPI id table selected a different part.

Use spi_get_device_match_data() so SPI id-table driver_data is consumed when OF match data is absent. This keeps the existing default fallback while avoiding the wrong MTD geometry for id-table-only matches.

AnalysisAI

Wrong MTD geometry is applied in the Linux kernel's mchp23k256 SPI SRAM driver when the chip is matched via the SPI id-table rather than via Device Tree, potentially exposing or corrupting unintended SRAM address regions. The driver's probe function calls of_device_get_match_data() exclusively, causing any non-OF SPI modalias match to silently fall back to the default mchp23k256_caps structure regardless of which part was actually selected by the SPI id-table, leading to incorrect chip capacity and address geometry. No public exploit exists and EPSS places this at the 7th percentile (0.17%), but the C:H/I:H/A:H CVSS impact flags reflect that incorrect geometry can expose the entire SRAM contents or allow out-of-bounds writes on affected embedded systems.

Technical ContextAI

The mchp23k256 driver manages the Microchip 23K256/23LC1024 family of SPI-attached SRAM chips under the Linux kernel's Memory Technology Device (MTD) subsystem. Linux supports two parallel device-matching paths at probe time: Open Firmware/Device Tree (OF) and the SPI id-table. The driver previously used of_device_get_match_data(), which returns NULL when the match path was SPI id-table only (no DT node), causing the code to silently fall back to the compile-time default mchp23k256_caps even when the SPI id-table driver_data pointed to a different chip variant with a different capacity. The fix replaces this call with spi_get_device_match_data(), which checks both paths and returns the correct driver_data regardless of how the device was matched. The root cause is a missing multi-path match abstraction rather than a traditional CWE-classified memory safety error - no CWE is assigned. Affected kernel versions trace back to commit 4379075a870b (Linux 4.13, when the driver was introduced).

RemediationAI

The primary fix is to upgrade the Linux kernel to a patched stable release: 5.15.212 or later for the 5.15.x LTS branch, 6.1.178 or later for 6.1.x LTS, 6.6.145 or later for 6.6.x LTS, 6.12.97 or later for 6.12.x LTS, 6.18.40 or later for 6.18.x, 7.1.5 or later for 7.1.x, or any build from 7.2-rc4 onward. Patch commits are available at https://git.kernel.org/stable/c/04ebd3766861f219325852c9598e0f0281cb3636 and the related stable-tree commits listed in the references. For systems where a kernel upgrade is not immediately feasible, a targeted workaround is to ensure the mchp23k256 chip is always enumerated via a Device Tree node (specifying the correct compatible string), which causes of_device_get_match_data() to return correct capacity data and avoids the fallback bug. Unloading the mchp23k256 kernel module entirely is an alternative where the SRAM is not operationally required, with the trade-off that any functionality depending on the SPI SRAM will be unavailable.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise Desktop 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Affected
SUSE Linux Enterprise High Availability Extension 16.0 Affected

Share

CVE-2026-68467 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy