CVE-2024-46769

What it actually does

Missing NULL check after devm_kasprintf() in intel_spi_populate_chip() allows pdata->name to be set to NULL on allocation failure, enabling subsequent NULL pointer dereference when the name field is accessed.

Why it matters to the business

Systems using affected Linux kernel versions may experience crashes or denial of service during SPI device initialization under memory pressure, increasing operational downtime risk for hardware-dependent workloads; low EPSS and absence from KEV indicate limited real-world exploitation urgency despite the 2024 disclosure.

How an attack unfolds

An attacker triggers SPI device population code paths while the system is under memory exhaustion, causing devm_kasprintf() to return NULL; the unchecked assignment leads to a crash when pdata->name is later dereferenced, achieving local denial of service with no remote vector or known threat actor involvement.

How to fix it

Update the Linux kernel to a version containing commit 6e68abdc5d674f9f4185bf1e1956368d05df4838 which adds the missing return-value check after devm_kasprintf(); apply the fixed version from the stable git tree or vendor backports.

How to confirm the fix worked

Verify the presence of the NULL check on the devm_kasprintf() result inside intel_spi_populate_chip() in the running kernel source or confirm the kernel build includes commit 6e68abdc5d674f9f4185bf1e1956368d05df4838.

Typical attack path

1. Attain local execution context on target system
2. Induce memory pressure to force allocation failure
3. Trigger intel_spi device initialization via hardware or driver load
4. Cause NULL dereference and kernel panic

How to detect it

Review kernel logs for oops or panic messages referencing intel_spi_populate_chip or NULL dereference during SPI initialization; correlate with memory pressure events in system logs.

What your security team should do

• Prioritize kernel updates on systems exposing SPI interfaces or using intel_spi driver
• Test updated kernels in staging environments before broad deployment
• Monitor vendor security advisories for backported fixes