Answer in brief
CVE-2026-68467 records a Unknown severity vulnerability in mtd: mchp23k256: use SPI match data for chip caps. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-68467 records a Unknown severity vulnerability in mtd: mchp23k256: use SPI match data for chip caps. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4379075a870b8de43a9ecd5b46884953234fc669 <2e179b028da9fd628a09286a2c9df4fa076b2cc9 || >=4379075a870b8de43a9ecd5b46884953234fc669 <a0c38083623c8b210a5b87fd34bebd05aa935ae8 || >=4379075a870b8de43a9ecd5b46884953234fc669 <7c0a3a73dccc9a3fc701f6be762449f18d0ca0fc || >=4379075a870b8de43a9ecd5b46884953234fc669 <dbe2254d1da99c986f9a3392471fc5eaa3229647 || >=4379075a870b8de43a9ecd5b46884953234fc669 <04ebd3766861f219325852c9598e0f0281cb3636 || >=4379075a870b8de43a9ecd5b46884953234fc669 <09e044192a42f716215fbd1a100ee87fa57426aa || >=4379075a870b8de43a9ecd5b46884953234fc669 <d322e40f4edf92bf0ca329e5aa4ae1c0316feb38 | 2e179b028da9fd628a09286a2c9df4fa076b2cc9, a0c38083623c8b210a5b87fd34bebd05aa935ae8, 7c0a3a73dccc9a3fc701f6be762449f18d0ca0fc, dbe2254d1da99c986f9a3392471fc5eaa3229647, 04ebd3766861f219325852c9598e0f0281cb3636, 09e044192a42f716215fbd1a100ee87fa57426aa, d322e40f4edf92bf0ca329e5aa4ae1c0316feb38 |
| Linux/Linuxgeneric | 4.13 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4379075a870b8de43a9ecd5b46884953234fc669 <2e179b028da9fd628a09286a2c9df4fa076b2cc9 || >=4379075a870b8de43a9ecd5b46884953234fc669 <a0c38083623c8b210a5b87fd34bebd05aa935ae8 || >=4379075a870b8de43a9ecd5b46884953234fc669 <7c0a3a73dccc9a3fc701f6be762449f18d0ca0fc || >=4379075a870b8de43a9ecd5b46884953234fc669 <dbe2254d1da99c986f9a3392471fc5eaa3229647 || >=4379075a870b8de43a9ecd5b46884953234fc669 <04ebd3766861f219325852c9598e0f0281cb3636 || >=4379075a870b8de43a9ecd5b46884953234fc669 <09e044192a42f716215fbd1a100ee87fa57426aa || >=4379075a870b8de43a9ecd5b46884953234fc669 <d322e40f4edf92bf0ca329e5aa4ae1c0316feb38 | 2e179b028da9fd628a09286a2c9df4fa076b2cc9, a0c38083623c8b210a5b87fd34bebd05aa935ae8, 7c0a3a73dccc9a3fc701f6be762449f18d0ca0fc, dbe2254d1da99c986f9a3392471fc5eaa3229647, 04ebd3766861f219325852c9598e0f0281cb3636, 09e044192a42f716215fbd1a100ee87fa57426aa, d322e40f4edf92bf0ca329e5aa4ae1c0316feb38 |
| Linux/Linuxgeneric | 4.13 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.