LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48864: vdpa/mlx5: add validation for VIRTIO_NET_CTRL_MQ_VQ_PAIRS_SET command

In the Linux kernel, the following vulnerability has been resolved: vdpa/mlx5: add validation for VIRTIO_NET_CTRL_MQ_VQ_PAIRS_SET command When control vq receives a VIRTIO_NET_CTRL_MQ_VQ_PAIRS_SET command request from the driver, presently there is no validation against the number of queue pairs to configure, or even if multiqueue had been negotiated or not is unverified. This may lead to kernel panic due to uninitialized resource for the queues were there any bogus request sent down by untrusted driver. Tie up the loose ends there.

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw can let a malformed virtio network control request crash the kernel in systems using the mlx5 vDPA driver. The business risk is service disruption, not confirmed data theft. The sources do not provide CVSS scoring or evidence of active exploitation.

Executive priority

Patch in normal vulnerability maintenance, faster for virtualization or high-availability platforms using mlx5 vDPA. The main known impact is outage from kernel panic. There is no provided evidence of active exploitation or remote unauthenticated compromise.

Technical view

The mlx5 vDPA path failed to validate VIRTIO_NET_CTRL_MQ_VQ_PAIRS_SET requests for queue-pair count and multiqueue negotiation. A bogus request from an untrusted driver could reference uninitialized queue resources and trigger kernel panic. Stable kernel commits add validation.

Likely exposure

Exposure appears limited to Linux systems using the mlx5 vDPA driver with virtio networking, especially where an untrusted driver can send control virtqueue requests. General Linux hosts not using this path are less likely exposed. Version evidence names Linux 5.15, 5.15.29, 5.16.15, and 5.17 as affected.

Exploitation context

The CVE record describes a crash path from a bogus control request, but does not provide exploit maturity details. It is not listed as KEV in the provided bundle. Treat this as a potential denial-of-service issue until vendor or distribution advisories provide stronger exploitation evidence.

Researcher notes

The vulnerable condition is missing validation of queue-pair configuration and multiqueue negotiation before resource use. Source detail is limited to the CVE description and kernel stable commits. No CVSS, CWE, exploit status, or distribution-specific fixed versions are provided in the bundle.

Mitigation direction

  • Update Linux kernels to builds containing the referenced stable validation commits.
  • Prioritize hosts using mlx5 vDPA, virtio networking, or virtualized networking offload paths.
  • Check Linux distribution advisories for backported fixes and package-specific version mapping.
  • Restrict untrusted driver or guest access to vDPA-capable networking where operationally possible.
  • Monitor affected hosts for kernel panic or unexpected reboot events.

Validation and detection

  • Inventory kernels and identify systems using the mlx5 vDPA driver.
  • Map installed kernel packages to distribution advisories or the referenced stable commits.
  • Confirm whether virtio multiqueue and vDPA networking are enabled on exposed systems.
  • Review logs for kernel panic events involving vdpa, mlx5, virtio, or control virtqueue handling.
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-48864 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
LinuxLinux52893733f2c5886fc74be6c386d12b59a3f581df, 52893733f2c5886fc74be6c386d12b59a3f581df, 52893733f2c5886fc74be6c386d12b59a3f581dfunaffected
LinuxLinux5.15, 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.