CVE-2026-89896

media: cedrus: fix memory leak in cedrus_init_ctrls()

N/A
Published: September 16, 2026 at 10:31 AM UTC
Updated: October 19, 2026 at 09:18 AM 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: cedrus: fix memory leak in cedrus_init_ctrls() In cedrus_init_ctrls(), the V4L2 control handler is initialized before allocating memory for ctx->ctrls. If this allocation fails, the function returns -ENOMEM without freeing the previously allocated handler resources, leading to a memory leak. Fix this by calling v4l2_ctrl_handler_free() on the ctx->ctrls allocation failure path. The bug was first flagged by an experimental analysis tool we are developing for kernel memory-management bugs while analyzing v6.13-rc1. The tool is still under development and is not yet publicly available. Manual inspection confirms that the bug is still present in v7.1.1. An x86_64 allyesconfig build showed no new warnings. As we do not have an Allwinner SoC or board with a Cedrus VPU available to test with, no runtime testing was able to be performed.

Affected

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

4.2050e761516f2b8c0cdeb31a8c6ca1b4ef98cd13f1
Vendor states this is fixed in 22441be29ec27c693f40c1ef499093275ef529d1 (fixed)
Vendor states this is fixed in 6fabacc3b79a528450aef4c32464da2ec681049e (fixed)
Vendor states this is fixed in 729a1ffab968b3c493f61d1cd683f5bafec500ea (fixed)
Vendor states this is fixed in 79fd0b0161506fc9507bf7a6fe4c975a857a5be8 (fixed)
Vendor states this is fixed in 81aa608ac3a56cdd4aab0bd12442ed529a24ba31 (fixed)
Vendor states this is fixed in 9df2fbe563194da1967a5db083442186c1323efe (fixed)
Vendor states this is fixed in ce5693b6e3a693fcdc3800af309363f6250104c8 (fixed)
Vendor states this is fixed in f78cf36cabf911da348ea80e4e9f430d74f6905c (fixed)
Vendor states this is fixed in 4.20 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.51 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.5 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (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