CVE-2023-54143: media: mediatek: vcodec: fix resource leaks in vdec_msg_queue_init()
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.19% (FIRST EPSS).
- Fixed version: Linux Linux 451dc187cadd47771e5d9434fe220fad7be84057, 858322c409e0aba8f70810d23f35c482744f007c, b7dbc27301f560c3b915235c53383155b3512083.
Low priority for now. Upgrade to Linux Linux 451dc187cadd47771e5d9434fe220fad7be84057, 858322c409e0aba8f70810d23f35c482744f007c, b7dbc27301f560c3b915235c53383155b3512083 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: mediatek: vcodec: fix resource leaks in vdec_msg_queue_init() If we encounter any error in the vdec_msg_queue_init() then we need to set "msg_queue->wdma_addr.size = 0;". Normally, this is done inside the vdec_msg_queue_deinit() function. However, if the first call to allocate &msg_queue->wdma_addr fails, then the vdec_msg_queue_deinit() function is a no-op. For that situation, just set the size to zero explicitly and return. There were two other error paths which did not clean up before returning. Change those error paths to goto mem_alloc_err.
- Published
- Dec 24, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
Is your version affected? Check itNoroxi 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.18affected
- b199fe46f35c57a415acd4d5295b0f4e35048c11 and later · before 858322c409e0aba8f70810d23f35c482744f007caffected · git
- b199fe46f35c57a415acd4d5295b0f4e35048c11 and later · before b7dbc27301f560c3b915235c53383155b3512083affected · git
- b199fe46f35c57a415acd4d5295b0f4e35048c11 and later · before 451dc187cadd47771e5d9434fe220fad7be84057affected · git
- b199fe46f35c57a415acd4d5295b0f4e35048c11 and later · before cf10b0bb503c974ba049d6f888b21178be20a962affected · git
- before 5.18not affected · semver
- 6.1.53 and later · up to and including 6.1.*not affected · semver
- 6.4.16 and later · up to and including 6.4.*not affected · semver
- 6.5.3 and later · up to and including 6.5.*not affected · semver
- 6.6 and laternot affected · original_commit_for_fix
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.55-1 | 6.1.55-1 |
| Debian:13 | linux | before 6.5.3-1 | 6.5.3-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-2023-54141Dec 24, 2025 · wifi: ath11k: Add missing hw_ops->get_ring_selector() for IPQ50180Monitor
- ← EarlierCVE-2023-54142Dec 24, 2025 · gtp: Fix use-after-free in __gtp_encap_destroy().31Monitor
- Later →CVE-2023-54144Dec 24, 2025 · drm/amdkfd: Fix kernel warning during topology setup0Monitor
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 | 451dc187cadd47771e5d9434fe220fad7be84057 | Vendor (CNA) |
| Linux Linux | 858322c409e0aba8f70810d23f35c482744f007c | Vendor (CNA) |
| Linux Linux | b7dbc27301f560c3b915235c53383155b3512083 | Vendor (CNA) |
| Linux Linux | cf10b0bb503c974ba049d6f888b21178be20a962 | Vendor (CNA) |
| debian:linux | 6.1.55-1 · 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.