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

> Remote attackers can cause a system reboot via a crafted L2CAP echo request in the Toshiba Bluetooth Stack driver.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jun 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pgpr-c8rx-9p5p

## What is CVE-2006-3146?

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

### Official description

The TOSRFBD.SYS driver for Toshiba Bluetooth Stack 4.00.29 and earlier on Windows allows remote attackers to cause a denial of service (reboot) via a L2CAP echo request that triggers an out-of-bounds memory access, similar to "Ping o' Death" and as demonstrated by BlueSmack.  NOTE: this issue was originally reported for 4.00.23.

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

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

It affects 1 product.


Products: Toshiba Bluetooth Stack.

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

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

## Is CVE-2006-3146 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-5611](https://insights.sbomify.com/CVE-2006-5611/): Other in n/a (critical 10.0)
- [CVE-2015-0884](https://insights.sbomify.com/CVE-2015-0884/): Privilege escalation in n/a (medium 6.9)
- [CVE-2006-0212](https://insights.sbomify.com/CVE-2006-0212/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-3146 is a medium-severity memory corruption vulnerability in n/a, published on 22 Jun 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-3146 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-3146/ (Markdown: https://insights.sbomify.com/CVE-2006-3146/index.md)
```

## Sources

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

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