CVE-2026-93200: i3c: master: Fix use-after-free of master->this
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.16% (FIRST EPSS).
- Fixed version: Linux Linux 027679d613ea73b8a00831369ec34eea804ce1bd, 23a1c4288a60e253a05a882bd8928ed61beb4a48, 4f3145db05fede36b35f8249b8acde5bd5d54864; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to Linux Linux 027679d613ea73b8a00831369ec34eea804ce1bd, 23a1c4288a60e253a05a882bd8928ed61beb4a48, 4f3145db05fede36b35f8249b8acde5bd5d54864; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes 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: Fix use-after-free of master->this sysfs attribute callbacks for the master controller device dereference master->this. However, master->this is freed in i3c_master_detach_free_devs() before the master device itself is released. As a result, sysfs accesses can dereference a freed master->this pointer, leading to a use-after-free. Keep master->this alive until i3c_masterdev_release(), which is called after the master device and its sysfs state are being torn down. Do not free master->this as part of the normal device detach path. On the error path in i3c_master_set_info(), reset master->this and bus.cur_master to NULL before freeing the allocated device.
- Published
- Sep 17, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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 a9b9cae0bd887ef0d438887f20b0a417491e45f0affected · git
- 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 94af669037d129914828a851d8b2a79b4537b73faffected · git
- 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before e766605a0490723df7b61e6abd0c392889732dd7affected · git
- 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 027679d613ea73b8a00831369ec34eea804ce1bdaffected · git
- 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 23a1c4288a60e253a05a882bd8928ed61beb4a48affected · git
- 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 4f3145db05fede36b35f8249b8acde5bd5d54864affected · git
- 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 50034d8d0f797c3a7a599f750a7d3e792e80dea5affected · git
- 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before feb0ed76601f3c2f91f08688c5a7d8b9d382f720affected · git
- before 5.0not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-93198Sep 17, 2026 · dm-pcache: validate the persisted dirty_tail chain at load0Monitor
- ← EarlierCVE-2026-93199Sep 17, 2026 · i3c: master: Do not treat master device as a duplicate target0Monitor
- Later →CVE-2026-93201Sep 17, 2026 · dm-pcache: validate seg_id fields from persistent memory31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 027679d613ea73b8a00831369ec34eea804ce1bd | Vendor (CNA) |
| Linux Linux | 23a1c4288a60e253a05a882bd8928ed61beb4a48 | Vendor (CNA) |
| Linux Linux | 4f3145db05fede36b35f8249b8acde5bd5d54864 | Vendor (CNA) |
| Linux Linux | 50034d8d0f797c3a7a599f750a7d3e792e80dea5 | Vendor (CNA) |
| Linux Linux | 94af669037d129914828a851d8b2a79b4537b73f | Vendor (CNA) |
| Linux Linux | a9b9cae0bd887ef0d438887f20b0a417491e45f0 | Vendor (CNA) |
| Linux Linux | e766605a0490723df7b61e6abd0c392889732dd7 | Vendor (CNA) |
| Linux Linux | feb0ed76601f3c2f91f08688c5a7d8b9d382f720 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | 6.6.161.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.6-1 · Debian:14 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package 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.
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.
Credits
All researchersFinders, 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/23a1c4288a60e253a05a882bd8928ed61beb4a48
- git.kernel.org/stable/c/4f3145db05fede36b35f8249b8acde5bd5d54864
- git.kernel.org/stable/c/50034d8d0f797c3a7a599f750a7d3e792e80dea5
- git.kernel.org/stable/c/94af669037d129914828a851d8b2a79b4537b73f
- git.kernel.org/stable/c/a9b9cae0bd887ef0d438887f20b0a417491e45f0
- git.kernel.org/stable/c/e766605a0490723df7b61e6abd0c392889732dd7
- git.kernel.org/stable/c/feb0ed76601f3c2f91f08688c5a7d8b9d382f720
Vendor advisories and official records. Exploit/PoC links are deliberately left out.