CVE-2024-35883: spi: mchp-pci1xxx: Fix a possible null pointer dereference in pci1xxx_spi_probe
In the Linux kernel, the following vulnerability has been resolved:
spi: mchp-pci1xxx: Fix a possible null pointer dereference in pci1xxx_spi_probe
In function pci1xxxx_spi_probe, there is a potential null pointer that
may be caused by a failed memory allocation by the function devm_kzalloc.
Hence, a null pointer check needs to be added to prevent null pointer
dereferencing later in the code.
To fix this issue, spi_bus->spi_int[iter] should be checked. The memory
allocated by devm_kzalloc will be automatically released, so just directly
return -ENOMEM without worrying about memory leaks.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is a reliability bug in the Microchip PCI1xxxx SPI driver. If memory allocation fails during driver setup, the kernel code may dereference a null pointer. The source does not provide CVSS, confirmed impact, or real-world exploitation evidence.
Executive priority
Treat this as a normal kernel patch management item unless affected hardware and driver usage are confirmed. There is no provided evidence of active exploitation, but kernel availability bugs still warrant timely maintenance updates.
Technical view
CVE-2024-35883 affects pci1xxxx_spi_probe in the Linux kernel mchp-pci1xxx SPI driver. A devm_kzalloc allocation result was not checked before later use. The kernel fix adds a null check for spi_bus->spi_int[iter] and returns -ENOMEM on failure.
Likely exposure
Exposure is likely limited to Linux systems using affected kernel versions with the mchp-pci1xxx SPI driver path present and relevant hardware or probing conditions. Source data does not prove broad remote exposure.
Exploitation context
CISA KEV status is false in the provided bundle, and no cited source reports active exploitation. The described trigger depends on a failed kernel memory allocation during driver probe; practical exploitability is not established by the sources.
Researcher notes
The public record is narrow: missing allocation failure handling in pci1xxxx_spi_probe. Sources do not include CVSS, CWE, exploit details, or distribution-specific fixed releases. Validate against kernel commit history and downstream backports before declaring systems remediated.
Mitigation direction
Update to a Linux kernel or distribution package containing the referenced stable fixes.
Check your Linux vendor advisory for exact fixed versions in your distribution.
Prioritize systems using Microchip PCI1xxxx SPI hardware or the mchp-pci1xxx driver.
Avoid inventing compensating controls; follow kernel or distribution guidance if patching is delayed.
Validation and detection
Inventory Linux kernel versions against the CVE record and distribution advisories.
Check whether the mchp-pci1xxx SPI driver is built, loaded, or relevant to deployed hardware.
Confirm patched kernels include one of the referenced upstream stable commits or downstream backports.
Review kernel logs for driver probe failures if relevant hardware is present.
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-2024-35883 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.