LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50278: PNP: fix name memory leak in pnp_alloc_dev()

In the Linux kernel, the following vulnerability has been resolved: PNP: fix name memory leak in pnp_alloc_dev() After commit 1fa5ae857bb1 ("driver core: get rid of struct device's bus_id string array"), the name of device is allocated dynamically, move dev_set_name() after pnp_add_id() to avoid memory leak.

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-50278 is a Linux kernel memory leak in Plug and Play device allocation. The public record does not provide a CVSS score, CWE, or active exploitation evidence. Treat it as a kernel hygiene and availability-risk item until your Linux distribution maps it to shipped kernel packages.

Executive priority

Schedule remediation through normal kernel patch cycles, with faster action for high-availability systems or fleets already under memory pressure. There is no cited evidence of active exploitation or a scored severity in the provided sources.

Technical view

The issue is in Linux PNP pnp_alloc_dev(). After a driver-core change made device names dynamically allocated, calling dev_set_name() before pnp_add_id() could leak the allocated name. Stable kernel commits move dev_set_name() after pnp_add_id() to avoid the leak.

Likely exposure

Exposure is likely limited to Linux systems running affected kernel versions or downstream builds that have not incorporated the listed stable fixes. The source bundle lists affected Linux versions through 6.2, with multiple stable-branch fix commits.

Exploitation context

The source bundle marks KEV as false and provides no public exploitation evidence. It describes a memory leak, not privilege escalation or code execution. Practical impact depends on whether local system activity can repeatedly reach the affected PNP allocation path.

Researcher notes

Evidence is limited to the CVE record and Linux stable commit references. The bundle does not include a reproducer, CVSS vector, CWE, attacker prerequisites, or distribution package mappings. Avoid extrapolating beyond memory leak and potential availability impact.

Mitigation direction

  • Map fleet kernels to vendor package versions and upstream stable commits.
  • Apply Linux distribution kernel updates that include the listed stable fixes.
  • Prioritize systems where PNP paths are relevant or kernel memory pressure is operationally risky.
  • Check vendor advisories before assuming a specific backport status.

Validation and detection

  • Record running kernel versions across Linux assets.
  • Confirm whether vendor kernels include one of the referenced stable commits.
  • Review kernel changelogs for the PNP pnp_alloc_dev() memory leak fix.
  • Monitor affected systems for abnormal kernel memory growth until patched.
Prepared
Confidence
medium
Sources
11

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-50278 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
10Source 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
LinuxLinux1fa5ae857bb14f6046205171d98506d8112dd74e, 1fa5ae857bb14f6046205171d98506d8112dd74e, 1fa5ae857bb14f6046205171d98506d8112dd74e, 1fa5ae857bb14f6046205171d98506d8112dd74e, 1fa5ae857bb14f6046205171d98506d8112dd74e, 1fa5ae857bb14f6046205171d98506d8112dd74e, 1fa5ae857bb14f6046205171d98506d8112dd74e, 1fa5ae857bb14f6046205171d98506d8112dd74e, 1fa5ae857bb14f6046205171d98506d8112dd74eunaffected
LinuxLinux2.6.30, 0, 4.9.337, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2, 6.2affected
Weakness

CWE details

No CWE listed

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