# CVE-2010-5332: Memory corruption in n/a

> An out-of-bounds array access in the Linux kernel mlx4 driver can lead to memory corruption, potentially causing denial of service or code execution.

- **Severity:** Medium 5.6 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jul 2019
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-rv5c-3qc2-9cmx, UBUNTU-CVE-2010-5332

## What is CVE-2010-5332?

CVE-2010-5332 is a medium-severity memory corruption vulnerability in Linux kernel, published on 27 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel before 2.6.37, an out of bounds array access happened in drivers/net/mlx4/port.c. When searching for a free entry in either mlx4_register_vlan() or mlx4_register_mac(), and there is no free entry, the loop terminates without updating the local variable free thus causing out of array bounds access.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2010-5332?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2010-5332?

No fix has been published for CVE-2010-5332 yet. Limit exposure of the affected software until one is available.

## Is CVE-2010-5332 being exploited?

There is no known exploitation of CVE-2010-5332 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-2010-5332 and fix it if it is affected.

What it is: CVE-2010-5332 is a medium-severity memory corruption vulnerability in Linux kernel, published on 27 Jul 2019. 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-2010-5332 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-2010-5332/ (Markdown: https://insights.sbomify.com/CVE-2010-5332/index.md)
```

## Sources

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

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