# CVE-2026-93215: cdx: Fix double free when sysfs file creation fails

> A double free vulnerability in the Linux kernel CDX bus driver allows local attackers to cause a denial of service or potentially execute arbitrary code.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-93215, DEBIAN-CVE-2026-93215, GHSA-hvg6-3p54-385v, UBUNTU-CVE-2026-93215

## What is CVE-2026-93215?

CVE-2026-93215 is an use after free vulnerability in Linux, published on 24 Sep 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:

cdx: Fix double free when sysfs file creation fails

In cdx_create_res_attr(), if sysfs_create_bin_file() fails, the code
frees res_attr but doesn't set cdx_dev->res_attr[num] to NULL. This
leaves a dangling pointer in the array. Then cdx_destroy_res_attr()
frees the already-freed memory. Fix the double free by initializing
cdx_dev->res_attr[num] after sysfs_create_bin_file() completes.

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


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

Apply the vendor's patch.

## Is CVE-2026-93215 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93215 and fix it if it is affected.

What it is: CVE-2026-93215 is an use after free vulnerability in Linux, published on 24 Sep 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-93215 in the wild and no public exploit code.

Affected product: Linux. 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-93215/ (Markdown: https://insights.sbomify.com/CVE-2026-93215/index.md)
```

## Sources

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

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