LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48861: vdpa: fix use-after-free on vp_vdpa_remove

In the Linux kernel, the following vulnerability has been resolved: vdpa: fix use-after-free on vp_vdpa_remove When vp_vdpa driver is unbind, vp_vdpa is freed in vdpa_unregister_device and then vp_vdpa->mdev.pci_dev is dereferenced in vp_modern_remove, triggering use-after-free. Call Trace of unbinding driver free vp_vdpa : do_syscall_64 vfs_write kernfs_fop_write_iter device_release_driver_internal pci_device_remove vp_vdpa_remove vdpa_unregister_device kobject_release device_release kfree Call Trace of dereference vp_vdpa->mdev.pci_dev: vp_modern_remove pci_release_selected_regions pci_release_region pci_resource_len pci_resource_end (dev)->resource[(bar)].end

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel memory-safety flaw in the vDPA driver removal path. When the vp_vdpa driver is unbound, freed memory can later be referenced. The most likely business impact is host instability or kernel crash on systems using this virtualization-related driver path. The source bundle does not provide a CVSS score or confirmed exploitation.

Executive priority

Treat as targeted infrastructure hygiene unless vDPA is used in critical virtualization hosts. Prioritize patch validation for those systems, but do not escalate as internet-wide emergency based on the supplied evidence.

Technical view

CVE-2022-48861 is a use-after-free in Linux vp_vdpa_remove. vdpa_unregister_device frees vp_vdpa, after which vp_modern_remove dereferences vp_vdpa->mdev.pci_dev during PCI region release. The issue is tied to driver unbind/removal behavior in affected Linux kernel versions and is addressed by upstream stable commits referenced in the CVE record.

Likely exposure

Exposure appears limited to Linux systems using the vp_vdpa/vDPA virtualization driver path, especially where the driver may be unbound or removed. The affected-version data in the bundle is sparse and should be validated against distribution kernel packages and backports.

Exploitation context

The bundle marks this CVE as not in KEV and provides no evidence of active exploitation, public exploit availability, or remote attack paths. The described trigger is driver unbind/removal, suggesting local or operational exposure rather than broad internet-facing exposure.

Researcher notes

The core evidence is a kernel call-trace showing freed vp_vdpa dereferenced through mdev.pci_dev after vdpa_unregister_device. Missing CVSS, CWE, exploitability notes, and distribution impact reduce certainty. Version data should be normalized against upstream stable and downstream backport records.

Mitigation direction

  • Update to a vendor-supported kernel containing the referenced upstream stable fixes.
  • Check Linux distribution advisories for backported fixes to maintained kernel packages.
  • Avoid unnecessary vp_vdpa driver unbind or reload operations until patched.
  • Prioritize hosts using vDPA, virtio, or related virtualization device paths.

Validation and detection

  • Inventory Linux kernel versions on virtualization hosts and appliances.
  • Identify systems using vp_vdpa, vDPA, or related virtio PCI driver paths.
  • Compare installed kernels with vendor advisories and referenced stable commits.
  • Review kernel logs for crashes around vp_vdpa unbind or device removal.
Prepared
Confidence
medium
Sources
5

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-48861 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
4Source 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux64b9f64f80a6f4b7ea51bf0510119cb15e801dc6, 64b9f64f80a6f4b7ea51bf0510119cb15e801dc6, 64b9f64f80a6f4b7ea51bf0510119cb15e801dc6unaffected
LinuxLinux5.13, 0, 5.15.29, 5.16.15, 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.