CVE-2026-80854

usb: gadget: f_tcm: keep port count until LUN teardown completes

N/A
Published: September 4, 2026 at 03:55 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.5c52661d60f636d17e26ad834457db333bd1df494
Vendor states this is fixed in 178f59a0bccd3f66cdfa5184310f31a58b7257c4 (fixed)
Vendor states this is fixed in 2efbfd42441d3ef8137aff2d59e9835e1d5ae780 (fixed)
Vendor states this is fixed in 85aa61fedcb4eb13f3dc5db73f6dc359f41f5d95 (fixed)
Vendor states this is fixed in ad6f0375d2e93a1d8c015463e5e92dfcb26e311b (fixed)
Vendor states this is fixed in bbd6aa311a9f4dd17822c7557451458d3d2e980b (fixed)
Vendor states this is fixed in c1f359d9a5efed458946063de65ddbeaacc4f165 (fixed)
Vendor states this is fixed in c39d0916da47d94909391876c9e5bd429ea7b1b9 (fixed)
Vendor states this is fixed in c494c5562ca69b61a82f566e3b87a445d2c28929 (fixed)
Vendor states this is fixed in eaa96a8458f54d6cf0954242ab8b1df2a6fccafa (fixed)
Vendor states this is fixed in 3.5 (unaffected)
Vendor states this is fixed in 5.10.269 (unaffected)
Vendor states this is fixed in 5.15.220 (unaffected)
Vendor states this is fixed in 6.1.187 (unaffected)
Vendor states this is fixed in 6.12.108 (unaffected)
Vendor states this is fixed in 6.18.49 (unaffected)
Vendor states this is fixed in 6.6.156 (unaffected)
Vendor states this is fixed in 7.1.13 (unaffected)
Vendor states this is fixed in 7.2.3 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card