CVE-2026-68212

media: saa7134: Fix a possible memory leak in saa7134_video_init1

N/A
Published: August 10, 2026 at 12:00 PM UTC
Updated: August 19, 2026 at 05:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.16 ≤ v < 5.10.2653.16 ≤ v < 5.15.2163.16 ≤ v < 6.1.1833.16 ≤ v < 6.12.1013.16 ≤ v < 6.18.423.16 ≤ v < 6.6.1483.16 ≤ v < 7.1.63.16 ≤ v < 7.23.16a00e68888d5d2b583b13d7d58204a27207af95fd
Vendor states this is fixed in 134c979dd721e22f196d71026432ee37d1f5cc38 (fixed)
Vendor states this is fixed in 1731dd61b6c0b7435c139951d2b7eada6c9667a8 (fixed)
Vendor states this is fixed in 34082a48376fd225a5c3d971c8962eb1320a54e0 (fixed)
Vendor states this is fixed in 44e16e3e022bf4a26adf03bc05a6dd5ffc34ef6d (fixed)
Vendor states this is fixed in b7936e8cbec1b96b126058eeb005e5b9111df38e (fixed)
Vendor states this is fixed in e1ef361ee31d1dba5dcae2cdd50f9c1352df0c23 (fixed)
Vendor states this is fixed in e773b1d4bd191e7520bf9e02cb676d62c1b20556 (fixed)
Vendor states this is fixed in f86ed548386e3050e5f8f25b450d09dc009d9a88 (fixed)
Vendor states this is fixed in 3.16 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card