# CVE-2006-6385: Memory corruption in n/a

> Local attackers can execute arbitrary code with kernel privileges via a stack-based buffer overflow in Intel network adapter drivers.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **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:** No
- **Published:** 8 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mmm9-jr3w-fmg8

## What is CVE-2006-6385?

CVE-2006-6385 is a high-severity memory corruption vulnerability in n/a, published on 8 Dec 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Stack-based buffer overflow in Intel PRO 10/100, PRO/1000, and PRO/10GbE PCI, PCI-X, and PCIe network adapter drivers (aka NDIS miniport drivers) before 20061205 allows local users to execute arbitrary code with "kernel-level" privileges via an incorrect function call in certain OID handlers.

## Which versions are affected by CVE-2006-6385?

It affects 4 products.


Products: Intel Pro 1000 Adapters, Intel Pro 1000 Pcie Adapters, Intel Pro 10 100 Adapters, Intel Pro 10gbe Adapters.

## How do I fix CVE-2006-6385?

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

## Is CVE-2006-6385 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-6385 and fix it if it is affected.

What it is: CVE-2006-6385 is a high-severity memory corruption vulnerability in n/a, published on 8 Dec 2006. 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-2006-6385 in the wild and no public exploit code.

Affected product: n/a. 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-2006-6385/ (Markdown: https://insights.sbomify.com/CVE-2006-6385/index.md)
```

## Sources

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

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