LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50119: rpmsg: Fix possible refcount leak in rpmsg_register_device_override()

In the Linux kernel, the following vulnerability has been resolved: rpmsg: Fix possible refcount leak in rpmsg_register_device_override() rpmsg_register_device_override need to call put_device to free vch when driver_set_override fails. Fix this by adding a put_device() to the error path.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a reference-count cleanup bug in the rpmsg device registration path. If driver_set_override fails, a device reference may not be released. The public record does not provide CVSS, CWE, exploit evidence, or detailed business impact, so urgency should be driven by kernel exposure and vendor patch status.

Executive priority

Treat as a normal kernel maintenance item unless affected kernels are present in products using rpmsg. Lack of severity scoring and exploit evidence lowers emergency priority, but unsupported or embedded kernels can remain exposed longer.

Technical view

rpmsg_register_device_override() did not call put_device() on the error path when driver_set_override() failed, creating a possible reference-count leak for vch. The listed fix adds put_device() to that failure path. The source bundle identifies Linux kernel 5.19 through 5.19.2 before 6.0 as affected, with stable kernel commits referenced.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions where the rpmsg subsystem and this registration path are reachable. The source bundle does not identify affected distributions, appliances, default configurations, or required privileges.

Exploitation context

No active exploitation is stated. The CVE is not marked KEV, and the provided sources do not describe public exploit activity, exploitability conditions, or practical attack paths.

Researcher notes

The evidence supports a narrow memory-management defect, not a confirmed privilege escalation or remote code execution issue. Impact and reachability are not described in the public bundle, so validation should focus on kernel version, rpmsg usage, and vendor backport status.

Mitigation direction

  • Check vendor kernel advisories for CVE-2022-50119 applicability.
  • Update affected Linux kernels using vendor-supported packages or stable fixes.
  • Prioritize systems that rely on rpmsg or remote processor messaging.
  • Track embedded or appliance firmware updates from suppliers.

Validation and detection

  • Inventory Linux kernel versions across servers, devices, and appliances.
  • Identify systems using kernels 5.19 through 5.19.2 before 6.0.
  • Check whether rpmsg-related kernel functionality is enabled or used.
  • Confirm vendor packages include the referenced stable kernel fix commits.
Prepared
Confidence
medium
Sources
9

Public sources used

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-50119 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
0ADP providers
8Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb585daa34a0a852e6d5e553132b411b6a0192d27, c14c6676ad5b78950a45121a7ee6cfb85778e71f, 3d14785980571ebb313a976e589b9d3563adc704, 5f1bb9f4d4b55c39180329c4e379aa740039eed3, bfd4a664ddfbe12f008efb0b0ab6bf25a8ab2538, bb17d110cbf270d5247a6e261c5ad50e362d1675, bb17d110cbf270d5247a6e261c5ad50e362d1675unaffected
LinuxLinux5.19, 0, 5.19.2, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.