CVE-2026-93236: media: meson: vdec: fix NULL pointer deref in vdec_try_fmt_common
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.21% (FIRST EPSS).
- Fixed version: Linux Linux 20aa934ace6917262ff579a73ec018d06a7bad1c, 276f28672bb6d5d5feca78db4219c7b5adf1be26, 3839b6be2279fc4f558723f2c0fbfc9c42070958; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 Release Notes.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 20aa934ace6917262ff579a73ec018d06a7bad1c, 276f28672bb6d5d5feca78db4219c7b5adf1be26, 3839b6be2279fc4f558723f2c0fbfc9c42070958; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 Release Notes 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 NULL pointer deref in vdec_try_fmt_common When VIDIOC_TRY_FMT is called with an unsupported pixel format on the OUTPUT queue, vdec_try_fmt_common() falls back to V4L2_PIX_FMT_MPEG2. However, if a distro has locally patched MPEG2 support out (as it has been broken for some time) the platform format table does not contain MPEG2 so find_format() returns NULL and the subsequent dereference of fmt_out->max_width triggers a NULL pointer dereference. Fix this by falling back to the first format in the platform's format array instead of hardcoding V4L2_PIX_FMT_MPEG2. This is always valid since every platform defines at least one format.
- Published
- Sep 24, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 11th 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 276f28672bb6d5d5feca78db4219c7b5adf1be26affected · git
- 3e7f51bd96077acad6acd7b45668f65b44233c4e and later · before c620906fb1b2ad75d408ea9d06040d66952d4a31affected · git
- 3e7f51bd96077acad6acd7b45668f65b44233c4e and later · before 3839b6be2279fc4f558723f2c0fbfc9c42070958affected · git
- 3e7f51bd96077acad6acd7b45668f65b44233c4e and later · before 680a89683197cdfe4e03e6fd7755454c647d39c1affected · git
- 3e7f51bd96077acad6acd7b45668f65b44233c4e and later · before f2375a308640e401c142c5426d52c3d10e016d25affected · git
- 3e7f51bd96077acad6acd7b45668f65b44233c4e and later · before 96dafbae77f50bfe2228bcfedcd8652c5e5f08e8affected · git
- 3e7f51bd96077acad6acd7b45668f65b44233c4e and later · before d61ba609c3226af3c84268ba606ea06ee63e511baffected · git
- 3e7f51bd96077acad6acd7b45668f65b44233c4e and later · before 20aa934ace6917262ff579a73ec018d06a7bad1caffected · 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.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.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-93234Sep 24, 2026 · drm/gud: validate TV mode names before creating enum property0Monitor
- ← EarlierCVE-2026-93235Sep 24, 2026 · f2fs: fix to zero post-EOF data when extending file size0Monitor
- Later →CVE-2026-93237Sep 24, 2026 · LoongArch: Add DIRECT_MAP_PHYSMEM_END definition31Monitor
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 | 20aa934ace6917262ff579a73ec018d06a7bad1c | Vendor (CNA) |
| Linux Linux | 276f28672bb6d5d5feca78db4219c7b5adf1be26 | Vendor (CNA) |
| Linux Linux | 3839b6be2279fc4f558723f2c0fbfc9c42070958 | Vendor (CNA) |
| Linux Linux | 680a89683197cdfe4e03e6fd7755454c647d39c1 | Vendor (CNA) |
| Linux Linux | 96dafbae77f50bfe2228bcfedcd8652c5e5f08e8 | Vendor (CNA) |
| Linux Linux | c620906fb1b2ad75d408ea9d06040d66952d4a31 | Vendor (CNA) |
| Linux Linux | d61ba609c3226af3c84268ba606ea06ee63e511b | Vendor (CNA) |
| Linux Linux | f2375a308640e401c142c5426d52c3d10e016d25 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-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-1181 · Sep 25, 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/276f28672bb6d5d5feca78db4219c7b5adf1be26
- git.kernel.org/stable/c/3839b6be2279fc4f558723f2c0fbfc9c42070958
- git.kernel.org/stable/c/680a89683197cdfe4e03e6fd7755454c647d39c1
- git.kernel.org/stable/c/96dafbae77f50bfe2228bcfedcd8652c5e5f08e8
- git.kernel.org/stable/c/c620906fb1b2ad75d408ea9d06040d66952d4a31
- git.kernel.org/stable/c/d61ba609c3226af3c84268ba606ea06ee63e511b
- git.kernel.org/stable/c/f2375a308640e401c142c5426d52c3d10e016d25
Vendor advisories and official records. Exploit/PoC links are deliberately left out.