CVSS 3.1
Вероятност да бъде експлоатирана в следващите 30 дни (EPSS)
Атакува се
Време до експлоатация
Атакува се от съседна мрежа, без особени условия, без вход и без действие от потребителя.
Описание
Оригинално описание
In the Linux kernel, the following vulnerability has been resolved: net: thunderbolt: Tear down DMA paths before stopping the rings tbnet_tear_down() stops both rings and frees their frame buffers before calling tb_xdomain_disable_paths(). tb_ring_stop() zeroes the ring's descriptor base and tbnet_free_buffers() unmaps and frees the pages the frames sit in, so by the time __tb_path_deactivate_hop() polls the hop's 'pending' bit, anything still in flight has nowhere to drain to. The teardown sequence has been in this order since the driver was added. The setup path has not: commit ff7cd07f3064 ("net: thunderbolt: Enable DMA paths only after rings are enabled") moved the path enable to the end of tbnet_connected_work() and documented why: /* Both logins successful so enable the rings, high-speed DMA * paths and start the network device queue. * * Note we enable the DMA paths last to make sure we have primed * the Rx ring before any incoming packets are allowed to * arrive. */ Teardown was never updated to match, so the rings and the paths now come down in the same order they go up instead of in reverse. On an ASMedia ASM4242 host router the 'pending' bit then never clears: every teardown burns the full 500 ms timeout and __tb_path_deactivate_hop() returns -ETIMEDOUT. Raising the timeout to 5 s does not help, so the hop is not slow to drain, it never drains at all. The failure is invisible above the thunderbolt core. __tb_path_deactivate_hops() is void and only calls tb_port_warn(); tb_path_deactivate(), tb_tunnel_deactivate() and __tb_disconnect_xdomain_paths() are void as well, and tb_disconnect_xdomain_paths() ends in an unconditional "return 0". So tb_xdomain_disable_paths() reports success and the netdev_warn() below it never fires. Repeated teardowns eventually take the XDomain control channel down, after which the peer node is gone and only a power cycle brings the controller back. Deactivating the paths first fixes it. Measured with kr
Засегнати продукти
- Linux Linux: e69b6c02b4c3b8d03be7136f90dd9551ad5a5a5e преди 7cce39109206bc5497e0953806563644b88bfc44; e69b6c02b4c3b8d03be7136f90dd9551ad5a5a5e преди 0da9a6d27155ad072dd76db8cd637feead99a0e0; e69b6c02b4c3b8d03be7136f90dd9551ad5a5a5e преди b5a21615f627c48dafaa6ef82a34a5b97a4352aa; e69b6c02b4c3b8d03be7136f90dd9551ad5a5a5e преди 103a9b663ac1cacb8465aeff18f84a247154a562; e69b6c02b4c3b8d03be7136f90dd9551ad5a5a5e преди 4dd71cb0d23d40cb58fe4261c7bd183dca66caa0; e69b6c02b4c3b8d03be7136f90dd9551ad5a5a5e преди 9a482b2b117e5fa656b6d24fc01799e8ac2d4368; e69b6c02b4c3b8d03be7136f90dd9551ad5a5a5e преди 68bf02b6b4ad3f748c6db71fd77b6c0402d252f4
- Linux Linux: 4.15; преди 4.15; 5.15.216 до 5.15.*; 6.1.183 до 6.1.*; 6.6.152 до 6.6.*; 6.12.104 до 6.12.*; 6.18.45 до 6.18.*; 7.1.9 до 7.1.*; от 7.2 нататък
История
- 22 август 2026 Публикувано
Други уязвимости в Linux Linux
Първоизточници
- https://www.cve.org/CVERecord?id=CVE-2026-74691
- https://nvd.nist.gov/vuln/detail/CVE-2026-74691
- https://git.kernel.org/stable/c/7cce39109206bc5497e0953806563644b88bfc44
- https://git.kernel.org/stable/c/0da9a6d27155ad072dd76db8cd637feead99a0e0
- https://git.kernel.org/stable/c/b5a21615f627c48dafaa6ef82a34a5b97a4352aa
- https://git.kernel.org/stable/c/103a9b663ac1cacb8465aeff18f84a247154a562
- https://git.kernel.org/stable/c/4dd71cb0d23d40cb58fe4261c7bd183dca66caa0
- https://git.kernel.org/stable/c/9a482b2b117e5fa656b6d24fc01799e8ac2d4368
- https://git.kernel.org/stable/c/68bf02b6b4ad3f748c6db71fd77b6c0402d252f4