LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48775: Drivers: hv: vmbus: Fix memory leak in vmbus_add_channel_kobj

In the Linux kernel, the following vulnerability has been resolved: Drivers: hv: vmbus: Fix memory leak in vmbus_add_channel_kobj kobject_init_and_add() takes reference even when it fails. According to the doc of kobject_init_and_add(): If this function returns an error, kobject_put() must be called to properly clean up the memory associated with the object. Fix memory leak by calling kobject_put().

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel memory-leak issue in the Hyper-V VMBus driver. The source says an object reference was not released when setup failed. Business impact is unclear because no CVSS, attacker path, or exploitation evidence is provided.

Executive priority

Handle through routine kernel patch management unless internal exposure analysis shows critical Hyper-V workloads cannot tolerate driver memory leaks. There is no source evidence of active exploitation or confirmed severe impact.

Technical view

vmbus_add_channel_kobj mishandled kobject_init_and_add failure handling. Kernel documentation requires kobject_put after failure because a reference is still held. The fix adds cleanup to avoid leaking memory in the hv vmbus channel kobject path.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel versions with the Hyper-V VMBus driver path present. The CVE source lists Linux version entries including 4.15, 4.19.231, 5.4.181, 5.10.102, 5.15.25, 5.16.11, and 5.17.

Exploitation context

The provided sources do not show active exploitation, KEV listing, exploit availability, privilege requirements, or a remote attack path. Treat this as an availability or stability concern until vendor guidance clarifies practical impact.

Researcher notes

The key evidence is a cleanup bug: kobject_init_and_add holds a reference even on error, requiring kobject_put. Sources do not define trigger conditions, reachable attack surface, or security impact beyond memory leakage.

Mitigation direction

  • Update affected Linux kernels through trusted distribution or vendor channels.
  • Confirm vendor advisories map the stable kernel fixes into your deployed kernel packages.
  • Prioritize systems relying on Hyper-V integration components or VMBus functionality.
  • Monitor kernel vendor notes for any later severity or exploitability clarification.

Validation and detection

  • Inventory Linux kernel versions across Hyper-V-hosted workloads.
  • Check whether deployed kernels include one of the referenced stable fixes.
  • Review vendor package changelogs for CVE-2022-48775 or the vmbus memory-leak fix.
  • Verify no exception process is holding affected kernels past normal maintenance windows.
Prepared
Confidence
medium
Sources
8

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-48775 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
2ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc2e5df616e1ae6c2a074cb241ebb65a318ebaf7c, c2e5df616e1ae6c2a074cb241ebb65a318ebaf7c, c2e5df616e1ae6c2a074cb241ebb65a318ebaf7c, c2e5df616e1ae6c2a074cb241ebb65a318ebaf7c, c2e5df616e1ae6c2a074cb241ebb65a318ebaf7c, c2e5df616e1ae6c2a074cb241ebb65a318ebaf7cunaffected
LinuxLinux4.15, 0, 4.19.231, 5.4.181, 5.10.102, 5.15.25, 5.16.11, 5.17affected
Weakness

CWE details

No CWE listed

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