bus: mhi: ep: Fix device refcount leak in the error path of MHI device creation
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.21% (FIRST EPSS).
- Fixed version: Linux Linux 4fae8fd4adc7f4765463ddeb1a5fad23936432f6, 51ddb831a36102fd0ea25f354935e49abce9f0a1, 5587e7871ce994bb079f97fe7e430d99627e5292.
Low priority for now. Upgrade to Linux Linux 4fae8fd4adc7f4765463ddeb1a5fad23936432f6, 51ddb831a36102fd0ea25f354935e49abce9f0a1, 5587e7871ce994bb079f97fe7e430d99627e5292 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: bus: mhi: ep: Fix device refcount leak in the error path of MHI device creation mhi_ep_create_device() takes one device reference for the UL channel and another for the DL channel after allocating the transfer device. These references are normally released by mhi_ep_destroy_device() before the device itself is removed. If dev_set_name() or device_add() fails, the error path currently drops only one reference. The remaining channel references keep the device from being released and leave the channels associated with a device that was never registered. Route both failures through a common unwind path that drops the DL channel reference, the UL channel reference, and the initial reference from device_initialize().
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- EPSS
- 0.2% · 11th 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.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.
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.19affected
- 297c77a0f27312b9a04696018c4cbd47926ca92b and later · before 8acc3813ab5015af73eeb74c9032443162f122d1affected · git
- 297c77a0f27312b9a04696018c4cbd47926ca92b and later · before 51ddb831a36102fd0ea25f354935e49abce9f0a1affected · git
- 297c77a0f27312b9a04696018c4cbd47926ca92b and later · before 4fae8fd4adc7f4765463ddeb1a5fad23936432f6affected · git
- 297c77a0f27312b9a04696018c4cbd47926ca92b and later · before 5587e7871ce994bb079f97fe7e430d99627e5292affected · git
- 297c77a0f27312b9a04696018c4cbd47926ca92b and later · before 8f3f64faee335eb678fd7dca7b95dfe3d0b271fdaffected · git
- 297c77a0f27312b9a04696018c4cbd47926ca92b and later · before 6f12862600bb70e599a614d706a095ea5f8f9858affected · git
- before 5.19not affected · semver
- 6.1.188 and later · up to and including 6.1.*not affected · semver
- 6.6.157 and later · up to and including 6.6.*not 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 | all versions | — |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-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
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
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 | 4fae8fd4adc7f4765463ddeb1a5fad23936432f6 | Vendor (CNA) |
| Linux Linux | 51ddb831a36102fd0ea25f354935e49abce9f0a1 | Vendor (CNA) |
| Linux Linux | 5587e7871ce994bb079f97fe7e430d99627e5292 | Vendor (CNA) |
| Linux Linux | 6f12862600bb70e599a614d706a095ea5f8f9858 | Vendor (CNA) |
| Linux Linux | 8acc3813ab5015af73eeb74c9032443162f122d1 | Vendor (CNA) |
| Linux Linux | 8f3f64faee335eb678fd7dca7b95dfe3d0b271fd | Vendor (CNA) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-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 (5 more)Show less
- git.kernel.org/stable/c/51ddb831a36102fd0ea25f354935e49abce9f0a1
- git.kernel.org/stable/c/5587e7871ce994bb079f97fe7e430d99627e5292
- git.kernel.org/stable/c/6f12862600bb70e599a614d706a095ea5f8f9858
- git.kernel.org/stable/c/8acc3813ab5015af73eeb74c9032443162f122d1
- git.kernel.org/stable/c/8f3f64faee335eb678fd7dca7b95dfe3d0b271fd
Vendor advisories and official records. Exploit/PoC links are deliberately left out.