CVE-2026-31768: iio: adc: ti-adc161s626: use DMA-safe memory for spi_read()
In the Linux kernel, the following vulnerability has been resolved:
iio: adc: ti-adc161s626: use DMA-safe memory for spiread()
Add a DMA-safe buffer and use it for spiread() instead of a stack memory. All SPI buffers must be DMA-safe.
Since we only need up to 3 bytes, we just use a u8[] instead of be16 and be32 and change the conversion functions appropriately.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
In ti-adc161s626, ensure all SPI buffers are DMA-safe by using a u8[] buffer for spi_read() (since only up to 3 bytes are needed) instead of __be16/__be32, and adjust the conversion functions as described.
Linux kernel iio: adc: ti-adc161s626 spi_read() SPI buffer type = use u8[] instead of __be16 and __be32 (update conversion functions accordingly)
Event History
Frequently Asked Questions
What is the severity of CVE-2026-31768?
CVE-2026-31768 is classified as a medium severity vulnerability in the Linux kernel.
How do I fix CVE-2026-31768?
To fix CVE-2026-31768, ensure that the DMA-safe buffer is used for spi_read() instead of stack memory.
Which Linux kernel versions are affected by CVE-2026-31768?
CVE-2026-31768 affects specific versions of the Linux kernel related to the iio ADC driver, particularly the ti-adc161s626.
What impact does CVE-2026-31768 have on my system?
CVE-2026-31768 could lead to potential data corruption or system instability if DMA-safe memory is not utilized properly.
Who resolved CVE-2026-31768?
CVE-2026-31768 was resolved by the Linux kernel development team with a patch that introduces a DMA-safe buffer.