CVE-2021-47653: media: davinci: vpif: fix use-after-free on driver unbind
In the Linux kernel, the following vulnerability has been resolved:
media: davinci: vpif: fix use-after-free on driver unbind
The driver allocates and registers two platform device structures during
probe, but the devices were never deregistered on driver unbind.
This results in a use-after-free on driver unbind as the device
structures were allocated using devres and would be freed by driver
core when remove() returns.
Fix this by adding the missing deregistration calls to the remove()
callback and failing probe on registration errors.
Note that the platform device structures must be freed using a proper
release callback to avoid leaking associated resources like device
names.
Security readout for executives and security teams
Plain-English summary
CVE-2021-47653 is a Linux kernel use-after-free in the DaVinci VPIF media driver during driver unbind. It is rated high because local low-privileged access could potentially affect confidentiality, integrity, and availability. Business urgency is highest for Linux systems that include and use this specific media driver or affected embedded hardware paths.
Executive priority
Treat as a targeted high-priority kernel maintenance issue, not a broad internet-facing emergency. Patch affected Linux systems where this driver is present, especially embedded devices with long update cycles. Ask asset owners to confirm whether DaVinci VPIF functionality exists in your environment.
Technical view
The VPIF driver allocates and registers two platform devices during probe but failed to deregister them on remove. Because the structures were devres-managed, driver core could free them after remove, leaving registered device references and causing use-after-free on unbind. The kernel fix adds deregistration in remove, handles registration errors, and uses a proper release callback.
Likely exposure
Exposure appears limited to affected Linux kernel versions with the media davinci VPIF driver present and reachable, especially embedded or media-focused systems using DaVinci VPIF functionality. The CVSS vector is local, low complexity, low privileges, and no user interaction. Systems without this driver or hardware path are less likely to be exposed.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not marked KEV. Exploitation would require local access with low privileges and the ability to trigger relevant driver unbind behavior. No public exploit details are provided in the source bundle.
Researcher notes
Key evidence is the upstream Linux fix description and stable commit references. The issue is CWE-416 use-after-free on driver unbind. Affected version data in the bundle is broad and somewhat commit-oriented, so confirm exposure through kernel source, configuration, module presence, and vendor backports.
Mitigation direction
Apply kernel updates that include the referenced stable fixes for CVE-2021-47653.
Check Linux distribution or device vendor advisories for backported fixes.
Prioritize systems using DaVinci VPIF or related media/embedded functionality.
If unused, consider vendor-supported removal or disabling of the affected driver.
Validation and detection
Inventory Linux kernel versions against vendor-fixed builds or referenced stable commits.
Confirm whether the davinci VPIF media driver is built, loaded, or used.
Review vendor kernel changelogs for CVE-2021-47653 or the referenced commits.
Test updates on representative embedded or media systems before production rollout.
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.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.