CVE-2026-68223: media: meson: vdec: Fix memory leak in error path of vdec_open
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
- Fixed version: Linux Linux 1391b75bf0119b5d37f1c1c3078d452a01967f9b, 2cf0171ad594860e31723c671e37824ce12c01ea, 5f97120d1a50c9efffe54425fac42bb7ef13ac86; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1391b75bf0119b5d37f1c1c3078d452a01967f9b, 2cf0171ad594860e31723c671e37824ce12c01ea, 5f97120d1a50c9efffe54425fac42bb7ef13ac86; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Published
- Aug 10, 2026
- Updated
- Aug 19, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.3affected
- 3e7f51bd96077acad6acd7b45668f65b44233c4e and later · before 5f97120d1a50c9efffe54425fac42bb7ef13ac86affected · git
- 3e7f51bd96077acad6acd7b45668f65b44233c4e and later · before fb77d6f4580f316c9148b942af0028ee489d121eaffected · git
- 3e7f51bd96077acad6acd7b45668f65b44233c4e and later · before d9058a19731036c03a779bfe8c3ca0d9aa198599affected · git
- 3e7f51bd96077acad6acd7b45668f65b44233c4e and later · before c6cd08a71a630f19b10c318e76e3c56e1dd10e00affected · git
- 3e7f51bd96077acad6acd7b45668f65b44233c4e and later · before 2cf0171ad594860e31723c671e37824ce12c01eaaffected · git
- 3e7f51bd96077acad6acd7b45668f65b44233c4e and later · before 1391b75bf0119b5d37f1c1c3078d452a01967f9baffected · git
- 3e7f51bd96077acad6acd7b45668f65b44233c4e and later · before 99f3527bd1a27ff798d59177ed045b0dd87deaefaffected · git
- 3e7f51bd96077acad6acd7b45668f65b44233c4e and later · before 940f161f734b25f175a95d2684c2021f6323693aaffected · git
- before 5.3not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.6-1 | 7.1.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68221Aug 10, 2026 · media: nuvoton: npcm-video: fix memory leaks in probe and remove0Monitor
- ← EarlierCVE-2026-68222Aug 10, 2026 · media: msi2500: Return queued buffers on start_streaming() failure31Monitor
- Later →CVE-2026-68224Aug 10, 2026 · media: mali-c55: Fix possible ERR_PTR in enable_streams0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1391b75bf0119b5d37f1c1c3078d452a01967f9b | Vendor (CNA) |
| Linux Linux | 2cf0171ad594860e31723c671e37824ce12c01ea | Vendor (CNA) |
| Linux Linux | 5f97120d1a50c9efffe54425fac42bb7ef13ac86 | Vendor (CNA) |
| Linux Linux | 940f161f734b25f175a95d2684c2021f6323693a | Vendor (CNA) |
| Linux Linux | 99f3527bd1a27ff798d59177ed045b0dd87deaef | Vendor (CNA) |
| Linux Linux | c6cd08a71a630f19b10c318e76e3c56e1dd10e00 | Vendor (CNA) |
| Linux Linux | d9058a19731036c03a779bfe8c3ca0d9aa198599 | Vendor (CNA) |
| Linux Linux | fb77d6f4580f316c9148b942af0028ee489d121e | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.150.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2cf0171ad594860e31723c671e37824ce12c01ea
- git.kernel.org/stable/c/5f97120d1a50c9efffe54425fac42bb7ef13ac86
- git.kernel.org/stable/c/940f161f734b25f175a95d2684c2021f6323693a
- git.kernel.org/stable/c/99f3527bd1a27ff798d59177ed045b0dd87deaef
- git.kernel.org/stable/c/c6cd08a71a630f19b10c318e76e3c56e1dd10e00
- git.kernel.org/stable/c/d9058a19731036c03a779bfe8c3ca0d9aa198599
- git.kernel.org/stable/c/fb77d6f4580f316c9148b942af0028ee489d121e
Vendor advisories and official records. Exploit/PoC links are deliberately left out.