Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
  • Fixed version: Linux Linux 150e71808d3715a0deefbb189c780d03fdbdc735, 3728d90ec66d4ad33d357e7d6e82b02d34e1c99c, 4dc1b3eeba7991905a5b5b8129ebea51be7d87b7.

Low priority for now. Upgrade to Linux Linux 150e71808d3715a0deefbb189c780d03fdbdc735, 3728d90ec66d4ad33d357e7d6e82b02d34e1c99c, 4dc1b3eeba7991905a5b5b8129ebea51be7d87b7 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Sep 17, 2026
Updated
Oct 30, 2026
EPSS
0.2% · 10th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-93199

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.0affected
    • 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 3728d90ec66d4ad33d357e7d6e82b02d34e1c99caffected · git
    • 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 6f2340857fc206e7ebfc50c568fb65c3055e568baffected · git
    • 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before d72a5e9060030a1c205b54157c15a428b741d83faffected · git
    • 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 7b25b755d59077dd9484ba1360b8fe6396e5ccfbaffected · git
    • 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 533faf3d2e67ded0a62b7ba753c0fe993d1dfc26affected · git
    • 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before d0cc00957292e353ad46039034cd8f82fc4f8057affected · git
    • 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 150e71808d3715a0deefbb189c780d03fdbdc735affected · git
    • 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 4dc1b3eeba7991905a5b5b8129ebea51be7d87b7affected · git
    • before 5.0not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:12linux-6.12before 6.12.113-1~deb12u16.12.113-1~deb12u1
Debian:13linuxbefore 6.12.113-16.12.113-1
Debian:14linuxbefore 7.2.6-17.2.6-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-93197Sep 17, 2026 · memcg: move LRU size accounting on reparenting instead of copying it
    0Monitor
  • ← EarlierCVE-2026-93198Sep 17, 2026 · dm-pcache: validate the persisted dirty_tail chain at load
    0Monitor
  • Later →CVE-2026-93200Sep 17, 2026 · i3c: master: Fix use-after-free of master->this
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux150e71808d3715a0deefbb189c780d03fdbdc735Vendor (CNA)
Linux Linux3728d90ec66d4ad33d357e7d6e82b02d34e1c99cVendor (CNA)
Linux Linux4dc1b3eeba7991905a5b5b8129ebea51be7d87b7Vendor (CNA)
Linux Linux533faf3d2e67ded0a62b7ba753c0fe993d1dfc26Vendor (CNA)
Linux Linux6f2340857fc206e7ebfc50c568fb65c3055e568bVendor (CNA)
Linux Linux7b25b755d59077dd9484ba1360b8fe6396e5ccfbVendor (CNA)
Linux Linuxd0cc00957292e353ad46039034cd8f82fc4f8057Vendor (CNA)
Linux Linuxd72a5e9060030a1c205b54157c15a428b741d83fVendor (CNA)
debian:linux6.12.113-1 · Debian:13Package registry (OSV)
debian:linux7.2.6-1 · Debian:14Package registry (OSV)
debian:linux-6.126.12.113-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records