CVE-2026-74725: enic: fix tx_hang_reset use-after-free on device removal
enic: fix txhangreset use-after-free on device removal
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1 - Upgrade
Upgrade
debian/linux-6.12to a version that resolves this vulnerability.Fixed in 6.12.113-1~deb12u1 - Upgrade
Upgrade
ubuntu/linux-nvidia-tegrato a version that resolves this vulnerability.Fixed in 6.8.0-1036.39 - Compensating control
In enic_remove(), use disable_work_sync() for tx_hang_reset, reset, and change_mtu_work so the work is canceled and cannot be requeued during device teardown; cancel_work_sync() alone is insufficient.
Event History
Frequently Asked Questions
What timing is required for the use-after-free to occur?
A TX timeout must fire while the device is being removed, allowing enic_tx_hang_reset() to be scheduled after free_netdev() has run.
Why is cancel_work_sync() insufficient during teardown?
The watchdog and notify paths can still schedule the work again between cancellation and unregister_netdev(). This leaves a race in which teardown work can run after the network device has been freed.
Which work items need protection from requeueing during device removal?
The tx_hang_reset work item must be disabled, and the reset and change_mtu_work items must receive the same treatment to close equivalent requeue races.