# CVE-2026-15417: CP210x Denial of Service

> A local unprivileged user can cause a kernel crash in the CP210x Windows driver by using incorrect settings, leading to denial of service.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **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:** 10 Sep 2026
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-mh8r-v298-qg9c

## What is CVE-2026-15417?

CVE-2026-15417 is a medium-severity denial of service vulnerability in Silicon Labs silabser.sys driver, published on 10 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the silabser.sys Windows 8 driver for CP210x devices, a local unprivileged user can use incorrect driver settings to cause a kernel crash.

Weakness: CWE-369 (Divide By Zero)

## Which versions are affected by CVE-2026-15417?


## How do I fix CVE-2026-15417?

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

## Is CVE-2026-15417 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15417 and fix it if it is affected.

What it is: CVE-2026-15417 is a medium-severity denial of service vulnerability in Silicon Labs silabser.sys driver, published on 10 Sep 2026. 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-2026-15417 in the wild and no public exploit code.

Affected product: Silicon Labs silabser.sys driver. 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-2026-15417/ (Markdown: https://insights.sbomify.com/CVE-2026-15417/index.md)
```

## Sources

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

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