mtd: mchp23k256: use SPI match data for chip caps
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4379075a870b8de43a9ecd5b46884953234fc669 · < 09e044192a42f716215fbd1a100ee87fa57426aa| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s mchp23k256 driver can use the wrong chip capacity for a non-OF SPI modalias match, resulting in incorrect MTD geometry for some ID-table-only matches. The input does not describe an attacker action or specify network access, authentication, or user interaction requirements.
Engineers running Linux kernels with the mchp23k256 driver should check their vendor advisory for affected versions; none are listed here.