CVE-2026-68223

media: meson: vdec: Fix memory leak in error path of vdec_open

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: meson: vdec: Fix memory leak in error path of vdec_open The vdec_open() function previously jumped directly to err_m2m_release when vdec_init_ctrls() failed, skipping release of the m2m context. This caused a resource leak. Fix it by introducing a proper err_m2m_ctx_release label that calls v4l2_m2m_ctx_release(sess->m2m_ctx) before releasing the m2m device. This was identified via kmemleak: unreferenced object 0xffff0000205d6878 (size 8): comm "v4l_id", pid 5289, jiffies 4294938580 hex dump (first 8 bytes): 40 d2 49 18 00 00 ff ff @.I..... backtrace (crc d3204599): kmemleak_alloc+0xc8/0xf0 __kvmalloc_node_noprof+0x60c/0x850 v4l2_ctrl_handler_init_class+0x1b4/0x2e8 [videodev] vdec_open+0x1f4/0x788 [meson_vdec] v4l2_open+0x144/0x460 [videodev] chrdev_open+0x1ac/0x500 do_dentry_open+0x3f0/0xfe8 vfs_open+0x68/0x320 do_open+0x2d8/0x9a8 path_openat+0x1d0/0x4f0 do_filp_open+0x190/0x380 do_sys_openat2+0xf8/0x1b0 __arm64_sys_openat+0x13c/0x1e8 invoke_syscall+0xdc/0x268 el0_svc_common.constprop.0+0x178/0x258 do_el0_svc+0x4c/0x70

Affected

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

5.3 ≤ v < 5.10.2655.3 ≤ v < 5.15.2165.3 ≤ v < 6.1.1835.3 ≤ v < 6.12.1015.3 ≤ v < 6.18.425.3 ≤ v < 6.6.1485.3 ≤ v < 7.1.65.3 ≤ v < 7.23e7f51bd96077acad6acd7b45668f65b44233c4e5.3
Vendor states this is fixed in 1391b75bf0119b5d37f1c1c3078d452a01967f9b (fixed)
Vendor states this is fixed in 2cf0171ad594860e31723c671e37824ce12c01ea (fixed)
Vendor states this is fixed in 5f97120d1a50c9efffe54425fac42bb7ef13ac86 (fixed)
Vendor states this is fixed in 940f161f734b25f175a95d2684c2021f6323693a (fixed)
Vendor states this is fixed in 99f3527bd1a27ff798d59177ed045b0dd87deaef (fixed)
Vendor states this is fixed in c6cd08a71a630f19b10c318e76e3c56e1dd10e00 (fixed)
Vendor states this is fixed in d9058a19731036c03a779bfe8c3ca0d9aa198599 (fixed)
Vendor states this is fixed in fb77d6f4580f316c9148b942af0028ee489d121e (fixed)
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 5.3 (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