# CVE-2026-93199: i3c: master: Do not treat master device as a duplicate target


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-102401, BELL-CVE-2026-93199, DEBIAN-CVE-2026-93199, GHSA-c82m-2rvg-fqpm, UBUNTU-CVE-2026-93199

## What is CVE-2026-93199?

CVE-2026-93199 is a vulnerability in Linux, published on 17 Sep 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

i3c: master: Do not treat master device as a duplicate target

i3c_master_search_i3c_dev_duplicate() searches the bus for another I3C
device with the same PID as the reference device.  The search can match
master->this, causing the controller itself to be returned as a
duplicate.

Since the controller is not a target device, it cannot be a duplicate of
one.  Exclude master->this from matching so that the function only
returns real duplicate target devices.

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


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

Upgrade to a fixed version.

## Is CVE-2026-93199 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93199 is a vulnerability in Linux, published on 17 Sep 2026. 
Exploitation: There is no known exploitation of CVE-2026-93199 in the wild and no public exploit code.

Affected product: Linux. 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-93199/ (Markdown: https://insights.sbomify.com/CVE-2026-93199/index.md)
```

## Sources

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

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