CVE-2022-49887: media: meson: vdec: fix possible refcount leak in vdec_probe()
In the Linux kernel, the following vulnerability has been resolved:
media: meson: vdec: fix possible refcount leak in vdec_probe()
v4l2_device_unregister need to be called to put the refcount got by
v4l2_device_register when vdec_probe fails or vdec_remove is called.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel media-driver bug that can leak an internal reference count during video decoder setup or removal. The documented impact is availability, not data theft or tampering. It requires local low-privileged access and has no supplied evidence of active exploitation.
Executive priority
Treat as a normal-priority availability issue for affected Linux fleets, higher for embedded media devices or appliances. It does not justify emergency response without local exposure or vendor confirmation, but it should be included in regular kernel patch cycles.
Technical view
The meson vdec driver can miss v4l2_device_unregister() after v4l2_device_register() succeeds, leaving a refcount leak when vdec_probe() fails or vdec_remove() runs. CVSS 3.1 is 5.5: local attack vector, low complexity, low privileges, no user interaction, high availability impact.
Likely exposure
Exposure is most plausible on Linux systems using the meson video decoder media driver, especially embedded or ARM-based platforms. The provided affected data is Linux kernel focused, but version range details are incomplete, so confirm against vendor or distribution advisories.
Exploitation context
The source bundle does not show KEV listing or any cited active exploitation. The CVSS vector indicates local access with low privileges is required. No confidentiality or integrity impact is documented.
Researcher notes
Evidence is limited to the CVE description, CVSS vector, and Linux stable commit references. The record describes a refcount leak fix, not a complete exploit scenario. Validate exposure through kernel configuration, driver presence, and vendor package mapping.
Mitigation direction
Apply kernel or distribution updates that include the referenced stable fixes.
Check vendor guidance for affected kernel packages and supported fixed versions.
Prioritize systems where the meson vdec media driver is enabled or loaded.
Retire or isolate unsupported kernels that cannot receive vendor fixes.
Validation and detection
Inventory Linux kernel versions and packages across relevant assets.
Check whether the meson vdec media driver is present, enabled, or loaded.
Compare running kernels against distribution advisories and referenced stable commits.
Confirm remediation by verifying the updated kernel package or patched source is deployed.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-49887 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.