CVE-2026-74301: Bluetooth: btmtk: fix URB leak in alloc_mtk_intr_urb error path
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 2643524743b9cc3c6f5f34cde2a8c627d793f21c, 4e354991da5890d5ce7bfea3f66fb897ae301756, 7f206a8d8d82296aa2d30bf5f3e5bb73fc44591d.
Low priority for now. Upgrade to Linux Linux 2643524743b9cc3c6f5f34cde2a8c627d793f21c, 4e354991da5890d5ce7bfea3f66fb897ae301756, 7f206a8d8d82296aa2d30bf5f3e5bb73fc44591d 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: Bluetooth: btmtk: fix URB leak in alloc_mtk_intr_urb error path When btmtk_isopkt_pad() fails, the previously allocated URB is not freed, leaking the urb structure. Add usb_free_urb() before returning the error.
- Published
- Aug 15, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
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.
Is your version affected? Check itNoroxi 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
- 6.11affected
- ceac1cb0259de682d78f5c784ef8e0b13022e9d9 and later · before 2643524743b9cc3c6f5f34cde2a8c627d793f21caffected · git
- ceac1cb0259de682d78f5c784ef8e0b13022e9d9 and later · before 7f206a8d8d82296aa2d30bf5f3e5bb73fc44591daffected · git
- ceac1cb0259de682d78f5c784ef8e0b13022e9d9 and later · before 4e354991da5890d5ce7bfea3f66fb897ae301756affected · git
- ceac1cb0259de682d78f5c784ef8e0b13022e9d9 and later · before f396f4005180928cd9e15e352a6512865d3bc908affected · git
- before 6.11not affected · semver
- 6.12.97 and later · up to and including 6.12.*not affected · semver
- 6.18.40 and later · up to and including 6.18.*not affected · semver
- 7.1.5 and later · up to and including 7.1.*not affected · semver
- 7.2 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-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-74298Aug 15, 2026 · RDMA/core: Fix FRMR set pinned push error path0Monitor
- ← EarlierCVE-2026-74299Aug 15, 2026 · RDMA/core: Fix FRMR aging push to queue error flow0Monitor
- Later →CVE-2026-74303Aug 15, 2026 · Bluetooth: hci_qca: fix NULL pointer dereference in qca_dmp_hdr() for non-serdev device0Monitor
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 | 2643524743b9cc3c6f5f34cde2a8c627d793f21c | Vendor (CNA) |
| Linux Linux | 4e354991da5890d5ce7bfea3f66fb897ae301756 | Vendor (CNA) |
| Linux Linux | 7f206a8d8d82296aa2d30bf5f3e5bb73fc44591d | Vendor (CNA) |
| Linux Linux | f396f4005180928cd9e15e352a6512865d3bc908 | Vendor (CNA) |
| debian:linux | 6.12.100-1 · Debian:13 | 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).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.