mtd: spi-nor: debugfs: fix out-of-bounds read in spi_nor_params_show()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0257be79fc4a16a3252ce80aa13b3640f728c425 · < e47029b977e747cb3a9174308fd55762cce70147| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
mtd: spi-nor: debugfs: fix out-of-bounds read in spi_nor_params_show()
Sashiko noticed an out-of-bounds read [1].
In spi_nor_params_show(), the snor_f_names array is passed to spi_nor_print_flags() using sizeof(snor_f_names).
Since snor_f_names is an array of pointers, sizeof() returns the total number of bytes occupied by the pointers (element_count * sizeof(void *)) rather than the element count itself. On 64-bit systems, this makes the passed length 8x larger than intended.
Inside spi_nor_print_flags(), the 'names_len' argument is used to bounds-check the 'names' array access. An out-of-bounds read occurs if a flag bit is set that exceeds the array's actual element count but is within the inflated byte-size count.
Correct this by using ARRAY_SIZE() to pass the actual number of string pointers in the array.
From the CVE record · Linux
The Linux kernel's SPI-NOR debugfs code can read beyond a flag-name array. On 64-bit systems, this can occur when a flag bit exceeds the array's element count because the code uses the array's byte size as its length. The input does not specify attacker access requirements or user interaction.
Engineers running the Linux kernel should check their versions; affected versions are not specified.