# CVE-2024-26866: spi: lpspi: Avoid potential use-after-free in probe()

> A use-after-free vulnerability in the Linux kernel's LPSPI driver probe function can cause a system crash via NULL pointer dereference.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Apr 2024
- **Updated:** 11 May 2026
- **Also known as:** AZL-55974, BELL-CVE-2024-26866, DEBIAN-CVE-2024-26866, GHSA-c37g-rxhp-7mqc, ROOT-OS-DEBIAN-11-CVE-2024-26866, ROOT-OS-DEBIAN-12-CVE-2024-26866, ROOT-OS-UBUNTU-2204-CVE-2024-26866, UBUNTU-CVE-2024-26866

## What is CVE-2024-26866?

CVE-2024-26866 is a medium-severity use after free vulnerability in Linux kernel, published on 17 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

spi: lpspi: Avoid potential use-after-free in probe()

fsl_lpspi_probe() is allocating/disposing memory manually with
spi_alloc_host()/spi_alloc_target(), but uses
devm_spi_register_controller(). In case of error after the latter call the
memory will be explicitly freed in the probe function by
spi_controller_put() call, but used afterwards by "devm" management outside
probe() (spi_unregister_controller() <- devm_spi_unregister() below).

Unable to handle kernel NULL pointer dereference at virtual address 0000000000000070
...
Call trace:
 kernfs_find_ns
 kernfs_find_and_get_ns
 sysfs_remove_group
 sysfs_remove_groups
 device_remove_attrs
 device_del
 spi_unregister_controller
 devm_spi_unregister
 release_nodes
 devres_release_all
 really_probe
 driver_probe_device
 __device_attach_driver
 bus_for_each_drv
 __device_attach
 device_initial_probe
 bus_probe_device
 deferred_probe_work_func
 process_one_work
 worker_thread
 kthread
 ret_from_fork

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2024-26866?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-26866?

Apply the vendor's patch.

## Is CVE-2024-26866 being exploited?

There is no known exploitation of CVE-2024-26866 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-26866 and fix it if it is affected.

What it is: CVE-2024-26866 is a medium-severity use after free vulnerability in Linux kernel, published on 17 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-26866 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-26866/ (Markdown: https://insights.sbomify.com/CVE-2024-26866/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-26866
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-26866
- OSV: https://osv.dev/vulnerability/CVE-2024-26866

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-26866/
Summaries are generated and may contain mistakes; the official description above is the record.