CVE-2022-49502: media: rga: fix possible memory leak in rga_probe
In the Linux kernel, the following vulnerability has been resolved:
media: rga: fix possible memory leak in rga_probe
rga->m2m_dev needs to be freed when rga_probe fails.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel resource leak in the RGA media driver. If driver initialization fails, memory allocated for rga->m2m_dev may not be released. The stated impact is availability only, with local low-privilege access required. It is not described as data theft or privilege escalation in the supplied sources.
Executive priority
Treat this as a moderate-priority availability issue. It matters most for Linux devices that use the affected media driver. It should be handled through normal kernel patch governance, with higher priority for embedded or appliance fleets where local users can reach the driver path.
Technical view
CVE-2022-49502 fixes a CWE-401 memory leak in rga_probe. The kernel stable commits free rga->m2m_dev on probe failure. CVSS 3.1 is 5.5: local attack vector, low complexity, low privileges, no user interaction, unchanged scope, and high availability impact.
Likely exposure
Exposure is most likely on Linux systems using the RGA media driver and affected kernel versions listed in the CVE data. Systems without this driver path are less likely to be exposed. Distribution-specific backports and package fix status are not established by the provided sources.
Exploitation context
The source bundle does not show active exploitation, and KEV is false. The CVSS vector requires local low-privilege access. The public description supports a denial-of-service-style availability concern from a memory leak, not confidentiality or integrity compromise.
Researcher notes
Evidence is limited to the kernel CVE description, CVSS data, and stable commit references. The source bundle does not provide exploit details, affected distributions, or runtime trigger conditions beyond probe failure. Avoid broad claims that all Linux deployments are practically exploitable.
Mitigation direction
Update to a kernel containing the referenced stable fix commits.
Check distribution vendor advisories for backported kernel fixes.
Prioritize systems where the RGA media driver is enabled or required.
If patching is delayed, review whether the driver can be disabled safely.
Validation and detection
Inventory Linux kernel versions against the affected versions in the CVE record.
Confirm whether the RGA media driver is built, loaded, or used.
Verify vendor kernel packages include one of the referenced stable fixes.
Record any distribution backport evidence before marking systems remediated.
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-401: 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.
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-401 · source CWE mapping
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.