LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48883: net/mlx5e: IPoIB, Block PKEY interfaces with less rx queues than parent

In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: IPoIB, Block PKEY interfaces with less rx queues than parent A user is able to configure an arbitrary number of rx queues when creating an interface via netlink. This doesn't work for child PKEY interfaces because the child interface uses the parent receive channels. Although the child shares the parent's receive channels, the number of rx queues is important for the channel_stats array: the parent's rx channel index is used to access the child's channel_stats. So the array has to be at least as large as the parent's rx queue size for the counting to work correctly and to prevent out of bound accesses. This patch checks for the mentioned scenario and returns an error when trying to create the interface. The error is propagated to the user.

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 mlx5e/IPoIB issue where a child PKEY network interface can be created with too few receive queues, leading to out-of-bounds access in statistics handling. Business urgency depends on whether systems use Mellanox mlx5 IPoIB PKEY interfaces. No source in the bundle shows active exploitation.

Executive priority

Prioritize as environment-dependent. It matters most for HPC, storage, or data-center Linux systems using Mellanox IPoIB PKEY networking. Without that exposure, urgency is lower, but kernel updates should still follow normal patch cycles.

Technical view

The flaw is in Linux net/mlx5e IPoIB PKEY interface creation. Child PKEY interfaces share parent receive channels, but their channel_stats array must match the parent RX queue count. Without the check, parent RX channel indexes can access beyond the child array. The referenced patch rejects invalid interface creation and returns an error to userspace.

Likely exposure

Likely exposure is limited to Linux systems using the mlx5e driver with IPoIB PKEY child interfaces. The bundle lists Linux as affected and names versions including 5.17, 6.1.7, and 6.2, but the exact fixed ranges are not fully clear from the provided data.

Exploitation context

The source says a user can configure RX queues when creating an interface via netlink. The bundle does not include CVSS, CWE, exploit details, proof of concept, or KEV listing. Treat exploitation status as unconfirmed.

Researcher notes

Key condition is child PKEY interface RX queue count being smaller than the parent’s receive queue count. The fix is defensive validation during interface creation. The bundle lacks scoring, exploitability analysis, and complete affected-version range metadata, so conclusions should remain conservative.

Mitigation direction

  • Apply Linux kernel or distribution updates containing the referenced stable fixes.
  • Check vendor advisories for exact affected and fixed kernel package versions.
  • Prioritize hosts using mlx5e, IPoIB, and PKEY child interfaces.
  • If updates are delayed, review vendor guidance for supported operational workarounds.

Validation and detection

  • Inventory Linux hosts with Mellanox mlx5 networking and IPoIB enabled.
  • Check whether PKEY child interfaces are created or managed on those hosts.
  • Compare running kernel packages against vendor fixed versions or referenced commits.
  • Confirm invalid PKEY interface creation is rejected after patching.
Prepared
Confidence
medium
Sources
4

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-48883 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
1ADP providers
3Source 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

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxbe98737a4faa3a0dc1781ced5bbf5c47865e29d7, be98737a4faa3a0dc1781ced5bbf5c47865e29d7unaffected
LinuxLinux5.17, 0, 6.1.7, 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.