Cloudanix VulnDB

CVE-2026-93199

None

CVSS

—

EPSS

0.2%

Published

Sep 17, 2026

CISA due date

—

Cloudanix analysis

Schedule a fix SSVC: Track

A Linux kernel bug could cause certain hardware communication controllers to mistakenly identify themselves as duplicate devices, potentially disrupting specialized bus operations until fixed by an update.

Exploitation
Local Privilege
Attacker needs
Local User
Complexity
Theoretical
Impact
Other
Component
OS kernel
Class
Improper Input Validation
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

The i3c_master_search_i3c_dev_duplicate() function fails to exclude the master device reference (master->this) from PID-based duplicate searches, allowing the controller itself to incorrectly match as a target device due to missing validation of device role.

Why it matters to the business

Embedded Linux systems using I3C buses may experience incorrect device enumeration or bus initialization failures, leading to hardware communication issues in affected devices and potential operational disruptions in specialized hardware.

How an attack unfolds

An attacker with local access crafts or simulates I3C bus conditions where a PID search occurs, relying on the flawed matching logic to cause the kernel to misidentify the master as a duplicate target, potentially triggering error paths or resource mishandling.

How to fix it

Update to a Linux kernel version containing the fix that excludes master->this from duplicate matching in i3c_master_search_i3c_dev_duplicate(). Apply the resolution from the referenced commit when backporting to supported kernels.

How to confirm the fix worked

Confirm the presence of the exclusion logic for master->this in i3c_master_search_i3c_dev_duplicate() via source inspection or kernel version checks; test I3C bus enumeration with duplicate PID scenarios to verify only real targets are reported.

Typical attack path

  1. Obtain local code execution or module loading capability on the target system
  2. Trigger I3C master initialization or device search routines on the bus
  3. Supply or emulate target devices sharing PID values with the master
  4. Observe or induce incorrect duplicate handling behavior in the kernel

How to detect it

Examine kernel logs for I3C bus enumeration errors or duplicate device warnings during master initialization; review dmesg or system logs around I3C device registration events for unexpected duplicate handling.

What your security team should do

  • Prioritize kernel updates for systems with I3C hardware support
  • Monitor upstream stable kernel releases for the included fix
  • Review I3C driver usage in custom or embedded deployments for exposure

The record

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.

Affected packages

Ecosystem Package Introduced Fixed