# CVE-2026-68212: media: saa7134: Fix a possible memory leak in saa7134_video_init1

> A memory leak in the saa7134 video driver during device probing can lead to resource exhaustion and denial of service.

- **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:** 19 Aug 2026
- **Also known as:** BELL-CVE-2026-68212, DEBIAN-CVE-2026-68212, GHSA-f8wh-4fq2-8xv3, UBUNTU-CVE-2026-68212

## What is CVE-2026-68212?

CVE-2026-68212 is a memory corruption 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: saa7134: Fix a possible memory leak in saa7134_video_init1

In saa7134_video_init1(), the return value of the first
saa7134_pgtable_alloc() is not checked. If it fails, the function
continues as if successful, leaving the driver with an invalid page
table. Additionally, if vb2_queue_init() for the VBI queue fails after
the video queue page table has been allocated, the allocated memory is
not freed before returning. The second saa7134_pgtable_alloc() also
lacks a return value check. Errors occur during device probing before
the device is fully registered, the normal cleanup path in
saa7134_finidev() is not executed, leading to memory leaks and
potential use of uninitialized DMA resources.

Check the return value of both saa7134_pgtable_alloc() calls and
propagate errors. On failure of any later step, free allocated page
tables to avoid memory leaks. Ensure control handlers are also
released on error to prevent further resource leakage.

Found by code review.

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


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

Apply the vendor's patch.

## Is CVE-2026-68212 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68212 is a memory corruption 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-68212 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-68212/ (Markdown: https://insights.sbomify.com/CVE-2026-68212/index.md)
```

## Sources

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

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