# CVE-2026-23068: spi: spi-sprd-adi: Fix double free in probe error path

> A double-free vulnerability in the Linux kernel's SPI driver allows attackers to cause a denial of service or potentially execute code via a failed probe path.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 4 Feb 2026
- **Updated:** 11 May 2026
- **Also known as:** AZL-77163, BELL-CVE-2026-23068, DEBIAN-CVE-2026-23068, GHSA-2r6w-8qqx-7jq3, ROOT-OS-DEBIAN-11-CVE-2026-23068, ROOT-OS-UBUNTU-2204-CVE-2026-23068, ROOT-OS-UBUNTU-2404-CVE-2026-23068, UBUNTU-CVE-2026-23068

## What is CVE-2026-23068?

CVE-2026-23068 is a high-severity use after free vulnerability in Linux kernel, published on 4 Feb 2026. 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: spi-sprd-adi: Fix double free in probe error path

The driver currently uses spi_alloc_host() to allocate the controller
but registers it using devm_spi_register_controller().

If devm_register_restart_handler() fails, the code jumps to the
put_ctlr label and calls spi_controller_put(). However, since the
controller was registered via a devm function, the device core will
automatically call spi_controller_put() again when the probe fails.
This results in a double-free of the spi_controller structure.

Fix this by switching to devm_spi_alloc_host() and removing the
manual spi_controller_put() call.

Weakness: CWE-415 (Double Free)

## Which versions are affected by CVE-2026-23068?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-23068?

Apply the vendor's patch.

## Is CVE-2026-23068 being exploited?

There is no known exploitation of CVE-2026-23068 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-2026-23068 and fix it if it is affected.

What it is: CVE-2026-23068 is a high-severity use after free vulnerability in Linux kernel, published on 4 Feb 2026. 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-2026-23068 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-2026-23068/ (Markdown: https://insights.sbomify.com/CVE-2026-23068/index.md)
```

## Sources

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

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