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

> A user can cause out-of-bounds memory access in the Linux kernel mlx5 driver by creating IPoIB PKEY interfaces with fewer rx queues than the parent.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Aug 2024
- **Updated:** 5 Aug 2026
- **Also known as:** DEBIAN-CVE-2022-48883, GHSA-4hhg-35c9-5c3m, UBUNTU-CVE-2022-48883

## What is CVE-2022-48883?

CVE-2022-48883 is a high-severity memory corruption vulnerability in Linux kernel, published on 21 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-129 (Improper Validation of Array Index)

## Which versions are affected by CVE-2022-48883?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2022-48883?

Apply the vendor's patch.

## Is CVE-2022-48883 being exploited?

There is no known exploitation of CVE-2022-48883 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-48883 and fix it if it is affected.

What it is: CVE-2022-48883 is a high-severity memory corruption vulnerability in Linux kernel, published on 21 Aug 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-48883 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-48883/ (Markdown: https://insights.sbomify.com/CVE-2022-48883/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-48883
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-48883
- OSV: https://osv.dev/vulnerability/CVE-2022-48883

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-48883/
Summaries are generated and may contain mistakes; the official description above is the record.