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 spi_read()
Add a DMA-safe buffer and use it for spi_read() 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.
Security readout for executives and security teams
Plain-English summary
A Linux driver for the TI ADC161S626 analog-to-digital converter used stack memory for an SPI transfer, although SPI buffers must support DMA safely. On affected systems, this could compromise confidentiality, integrity, and availability. Exposure is hardware- and driver-dependent, so ordinary Linux installations may not be affected.
Executive priority
Prioritize targeted identification and patching of embedded, industrial, or specialized Linux systems using this driver. Treat confirmed exposure as high priority because the supplied CVSS indicates possible complete confidentiality, integrity, and availability impact. Broad emergency action across every Linux host is not supported by the evidence.
Technical view
The ti-adc161s626 IIO driver passed a stack-backed buffer to spi_read(). The resolved implementation adds a DMA-safe byte buffer and adjusts value conversion. CVSS 3.1 rates the issue 7.8: local access, low complexity, low privileges, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impacts.
Likely exposure
Likely exposure is limited to affected Linux kernels where the ti-adc161s626 driver is present and used with relevant SPI-connected hardware. The supplied version data is not sufficiently clear to state exact vulnerable ranges confidently. Two Siemens advisories are referenced, so organizations using Siemens products should review those notices for product-specific applicability.
Exploitation context
The supplied record does not identify public exploitation, and the CVE is not listed as KEV. The CVSS vector describes a local, low-privilege attack path rather than remote exploitation. No exploit prerequisites beyond that scoring information are established by the provided sources.
Researcher notes
The core defect is an SPI DMA-safety contract violation involving stack memory. Multiple Linux stable commits are supplied, indicating backports across maintained branches, but their exact release mapping is not explained in the bundle. The record provides neither a CWE nor evidence of exploitation, trigger conditions, demonstrated impact, or exploitability across particular SPI controllers.
Mitigation direction
Update to a vendor-supported kernel containing the referenced DMA-safe buffer correction.
Review Linux distribution and appliance vendor advisories for exact fixed package versions.
Assess both referenced Siemens advisories if Siemens products are deployed.
Restrict local access to potentially affected systems until updates are validated.
Validation and detection
Inventory kernel versions and systems using the ti-adc161s626 driver.
Confirm whether relevant TI ADC161S626 SPI hardware is configured or operational.
Verify the installed kernel includes the applicable referenced stable fix.
Check vendor advisories because the supplied affected-version list is ambiguous.
After updating, confirm normal ADC operation and review kernel logs for SPI or DMA errors.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-31768 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
9Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.