CVE-2026-80854: usb: gadget: f_tcm: keep port count until LUN teardown completes
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.18% (FIRST EPSS).
- Fixed version: Linux Linux 178f59a0bccd3f66cdfa5184310f31a58b7257c4, 2efbfd42441d3ef8137aff2d59e9835e1d5ae780, 85aa61fedcb4eb13f3dc5db73f6dc359f41f5d95.
Low priority for now. Upgrade to Linux Linux 178f59a0bccd3f66cdfa5184310f31a58b7257c4, 2efbfd42441d3ef8137aff2d59e9835e1d5ae780, 85aa61fedcb4eb13f3dc5db73f6dc359f41f5d95 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: usb: gadget: f_tcm: keep port count until LUN teardown completes tcm_usbg_drop_nexus() permits session removal once tpg_port_count reaches zero. However, usbg_port_unlink() currently decrements that count from the fabric_pre_unlink() callback, before core_dev_del_lun() waits for active se_lun references to drain. If removal of the last LUN races a nexus removal, the latter can observe a zero port count and call target_remove_session(). This frees sess_cmd_map while an in-flight struct usbg_cmd, including its work item, can still be accessed. Overlapping the last-LUN unlink with nexus removal reproduces this lifetime violation as a DEBUG_OBJECTS "free active" warning for usbg_cmd_work, followed by a target-core BUG/Oops. The generic target-core unlink path has no callback after core_dev_del_lun() completes. Add an optional fabric_post_unlink() callback and use it for the f_tcm port count. The count now remains nonzero until core_dev_del_lun() has finished draining active LUN references, preventing nexus removal from freeing the session during command completion.
- Published
- Sep 4, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 7th 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
- 3.5affected
- c52661d60f636d17e26ad834457db333bd1df494 and later · before c494c5562ca69b61a82f566e3b87a445d2c28929affected · git
- c52661d60f636d17e26ad834457db333bd1df494 and later · before c1f359d9a5efed458946063de65ddbeaacc4f165affected · git
- c52661d60f636d17e26ad834457db333bd1df494 and later · before 178f59a0bccd3f66cdfa5184310f31a58b7257c4affected · git
- c52661d60f636d17e26ad834457db333bd1df494 and later · before ad6f0375d2e93a1d8c015463e5e92dfcb26e311baffected · git
- c52661d60f636d17e26ad834457db333bd1df494 and later · before 2efbfd42441d3ef8137aff2d59e9835e1d5ae780affected · git
- c52661d60f636d17e26ad834457db333bd1df494 and later · before 85aa61fedcb4eb13f3dc5db73f6dc359f41f5d95affected · git
- c52661d60f636d17e26ad834457db333bd1df494 and later · before bbd6aa311a9f4dd17822c7557451458d3d2e980baffected · git
- c52661d60f636d17e26ad834457db333bd1df494 and later · before eaa96a8458f54d6cf0954242ab8b1df2a6fccafaaffected · git
- c52661d60f636d17e26ad834457db333bd1df494 and later · before c39d0916da47d94909391876c9e5bd429ea7b1b9affected · git
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 | before 6.1.187-1 | 6.1.187-1 |
| 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.1.13-1 | 7.1.13-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-80852Sep 4, 2026 · tls: device: fix out-of-bounds write in tls_append_frag()0Monitor
- ← EarlierCVE-2026-80853Sep 4, 2026 · KVM: SEV: Allocate full pages for {DE,EN}CRYPT ops on SNP-enabled hosts0Monitor
- Later →CVE-2026-80855Sep 4, 2026 · fuse: fix invalidate lock leak on open O_TRUNC DAX failure0Monitor
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 | 178f59a0bccd3f66cdfa5184310f31a58b7257c4 | Vendor (CNA) |
| Linux Linux | 2efbfd42441d3ef8137aff2d59e9835e1d5ae780 | Vendor (CNA) |
| Linux Linux | 85aa61fedcb4eb13f3dc5db73f6dc359f41f5d95 | Vendor (CNA) |
| Linux Linux | ad6f0375d2e93a1d8c015463e5e92dfcb26e311b | Vendor (CNA) |
| Linux Linux | bbd6aa311a9f4dd17822c7557451458d3d2e980b | Vendor (CNA) |
| Linux Linux | c1f359d9a5efed458946063de65ddbeaacc4f165 | Vendor (CNA) |
| Linux Linux | c39d0916da47d94909391876c9e5bd429ea7b1b9 | Vendor (CNA) |
| Linux Linux | c494c5562ca69b61a82f566e3b87a445d2c28929 | Vendor (CNA) |
| Linux Linux | eaa96a8458f54d6cf0954242ab8b1df2a6fccafa | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | 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 (8 more)Show less
- git.kernel.org/stable/c/2efbfd42441d3ef8137aff2d59e9835e1d5ae780
- git.kernel.org/stable/c/85aa61fedcb4eb13f3dc5db73f6dc359f41f5d95
- git.kernel.org/stable/c/ad6f0375d2e93a1d8c015463e5e92dfcb26e311b
- git.kernel.org/stable/c/bbd6aa311a9f4dd17822c7557451458d3d2e980b
- git.kernel.org/stable/c/c1f359d9a5efed458946063de65ddbeaacc4f165
- git.kernel.org/stable/c/c39d0916da47d94909391876c9e5bd429ea7b1b9
- git.kernel.org/stable/c/c494c5562ca69b61a82f566e3b87a445d2c28929
- git.kernel.org/stable/c/eaa96a8458f54d6cf0954242ab8b1df2a6fccafa
Vendor advisories and official records. Exploit/PoC links are deliberately left out.