Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-68467mtd: mchp23k256: use SPI match data for chip caps

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 2 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-68467, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 4379075a870b8de43a9ecd5b46884953234fc669 – < 2e179b028da9fd628a09286a2c9df4fa076b2cc9
    • affected 4379075a870b8de43a9ecd5b46884953234fc669 – < a0c38083623c8b210a5b87fd34bebd05aa935ae8
    • affected 4379075a870b8de43a9ecd5b46884953234fc669 – < 7c0a3a73dccc9a3fc701f6be762449f18d0ca0fc
    • affected 4379075a870b8de43a9ecd5b46884953234fc669 – < dbe2254d1da99c986f9a3392471fc5eaa3229647
    • affected 4379075a870b8de43a9ecd5b46884953234fc669 – < 04ebd3766861f219325852c9598e0f0281cb3636
    • affected 4379075a870b8de43a9ecd5b46884953234fc669 – < 09e044192a42f716215fbd1a100ee87fa57426aa
    • affected 4379075a870b8de43a9ecd5b46884953234fc669 – < d322e40f4edf92bf0ca329e5aa4ae1c0316feb38
  • Linux · Linux

    • affected 4.13
    • unaffected < 4.13
    • unaffected 5.15.212 – ≤ 5.15.*
    • unaffected 6.1.178 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-68467 badge
[![CVE-2026-68467](https://cveledger.app/badge/CVE-2026-68467.svg)](https://cveledger.app/cve/CVE-2026-68467)

Record last updated .