# CVE-2026-93070: media: ipu6: Do not free aux device pdata after init

> A double-free vulnerability in the Linux kernel IPU6 media driver allows attackers to cause denial of service or potentially execute code.

- **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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-93070, DEBIAN-CVE-2026-93070, GHSA-2q2h-4p8v-3772, UBUNTU-CVE-2026-93070

## What is CVE-2026-93070?

CVE-2026-93070 is a high-severity use after free vulnerability in Linux, published on 17 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:

media: ipu6: Do not free aux device pdata after init

ipu6_bus_initialize_device() stores the isys/psys pdata pointer in
struct ipu6_bus_device and initializes the auxiliary device. After that
point, error unwinding must drop the auxiliary device reference and let
ipu6_bus_release() free both the bus device and adev->pdata.

The isys and psys init paths already call put_device() when MMU
initialization fails, and ipu6_bus_add_device() calls
auxiliary_device_uninit() on auxiliary_device_add() failure. Both paths
therefore run the bus release callback. The extra kfree(pdata) in the
callers can release the same object a second time.

Remove the manual pdata frees after the auxiliary device has been
initialized.

This issue was found by a static analysis checker and confirmed by
manual source review.

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


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

Apply the vendor's patch.

## Is CVE-2026-93070 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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