# CVE-2026-68224: media: mali-c55: Fix possible ERR_PTR in enable_streams

> A missing error check in the Mali-C55 media driver allows dereferencing an error pointer, potentially causing a kernel crash.

- **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:** 10 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-68224, GHSA-4jrf-f2gh-qhvr, UBUNTU-CVE-2026-68224

## What is CVE-2026-68224?

CVE-2026-68224 is a vulnerability in Linux, published on 10 Aug 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: mali-c55: Fix possible ERR_PTR in enable_streams

The media_pad_remote_pad_unique() function returns either a valid
pointer or an ERR_PTR() on failure (-ENOTUNIQ if multiple links are
enabled, -ENOLINK if no connected pad is found). The return value
was assigned directly to isp->remote_src and dereferenced in the
next line without checking for errors, which could lead to an
ERR_PTR dereference.

Add proper error checking with IS_ERR() before dereferencing the
pointer. Also set isp->remote_src to NULL on error to maintain
consistency with other error paths in the function.

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


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

Apply the vendor's patch.

## Is CVE-2026-68224 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68224 is a vulnerability in Linux, published on 10 Aug 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-68224 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-68224/ (Markdown: https://insights.sbomify.com/CVE-2026-68224/index.md)
```

## Sources

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

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