CVE-2025-37801: spi: spi-imx: Add check for spi_imx_setupxfer()
In the Linux kernel, the following vulnerability has been resolved:
spi: spi-imx: Add check for spi_imx_setupxfer()
Add check for the return value of spi_imx_setupxfer().
spi_imx->rx and spi_imx->tx function pointer can be NULL when
spi_imx_setupxfer() return error, and make NULL pointer dereference.
Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
Call trace:
0x0
spi_imx_pio_transfer+0x50/0xd8
spi_imx_transfer_one+0x18c/0x858
spi_transfer_one_message+0x43c/0x790
__spi_pump_transfer_message+0x238/0x5d4
__spi_sync+0x2b0/0x454
spi_write_then_read+0x11c/0x200
Security readout for executives and security teams
Plain-English summary
A flaw in Linux’s NXP i.MX SPI driver can leave transfer function pointers unset after an error, causing the kernel to dereference a null address. A reachable failure could crash the affected system. The supplied CVSS score is 7.8, but exploitation requires local access.
Executive priority
Prioritize affected operational, embedded, and edge systems where a kernel crash could interrupt critical services. Treat internet-facing status alone as insufficient evidence of exposure because the vector is local. Patch through supported kernel channels after confirming spi-imx use and branch-specific applicability.
Technical view
The spi-imx driver failed to check the return value from spi_imx_setupxfer(). When setup fails, the rx and tx callbacks may remain NULL, and a subsequent PIO transfer can call a null pointer. The supplied trace confirms a kernel NULL-pointer dereference. Upstream stable-kernel commits add the missing error check.
Likely exposure
Exposure is limited to Linux systems using the affected spi-imx driver and reaching its transfer-error path. The supplied CVSS vector indicates local, low-privilege access with no user interaction, not remote network access. Whether ordinary local users can reach the relevant SPI device is not established.
Exploitation context
The supplied record is not in CISA KEV, and no cited source reports active exploitation. Evidence demonstrates a kernel crash condition, but does not establish practical confidentiality or integrity compromise despite the CVSS vector rating all three impacts high.
Researcher notes
The CVE lists several stable-kernel fix commits. The provided affected-version representation contains duplicated commit entries and an ambiguous “0,” so exact branch boundaries require vendor or commit-ancestry validation. The trace supports NULL-call-target denial of service; the supplied evidence does not explain a path to confidentiality or integrity impact.
Mitigation direction
Inventory Linux systems using the spi-imx driver, especially embedded and edge devices.
Apply a vendor-supported kernel containing the applicable upstream fix or backport.
Check Linux distributor guidance for branch-specific fixed package versions.
Until patched, restrict untrusted local access and access to exposed SPI device interfaces.
Validation and detection
Record each system’s running kernel version, distribution package, and architecture.
Confirm whether spi-imx is built, loaded, or actively serving SPI hardware.
Verify the installed kernel includes the applicable fix commit or documented vendor backport.
Review kernel logs for NULL dereferences involving spi_imx_pio_transfer or spi_imx_transfer_one.
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-2025-37801 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
7Source 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.