CVE-2026-74255

Critical

Description

In the Linux kernel, the following vulnerability has been resolved: tipc: fix UAF in tipc_l2_send_msg() Syzbot reported a slab-use-after-free in ipvlan_hard_header() when called from tipc_l2_send_msg(). The root cause is that tipc_disable_l2_media() calls synchronize_net() while b->media_ptr is still valid. This allows concurrent RCU readers to obtain the device pointer after synchronize_net() has finished. The pointer is cleared later in bearer_disable(), but without any subsequent synchronization, allowing the device to be freed while still in use by readers. Fix this by clearing b->media_ptr in tipc_disable_l2_media() before calling synchronize_net(). This is safe to do now because the call order in bearer_disable() was reversed in 0d051bf93c06 ("tipc: make bearer packet filtering generic") to call tipc_node_delete_links() (which needs the pointer) before disable_media(). https: //lore.kernel.org/netdev/[email protected]/T/#u

SeverityCritical
CVSS9.8
Exploit probability—
ProductLinux
PublishedAug 15, 2026
First seenAug 15, 2026

How to fix

Update
  • Linux Linux609ced2301be1df7e7ed2ef47d1d916674e6ba3b, 71aafa16d79b107b33837f60b6cbc7d0cb8c5708, f4002f1c669cc02e3763f479fc25ff1dfa9e2420, 50ff092633b06382e5091dd5b093ce943d4ac2f9, aef12b5ce793dea6b3a97a58fd0f946000ae8945, 0d8a12d7143126afdf9fbe2e3d438650dd6603ed, 35e0297a93c3c34a3924eeef816c03504e3ab5c5, f4c3d89fc986b0da196ddfc6cfe0ea5d5d08bec6 or later

Affected products

ProductAffected versionsFixed in
Linux Linux282b3a056225b35024246f63feb91d769d714dad ≤ v < 609ced2301be1df7e7ed2ef47d1d916674e6ba3b, 282b3a056225b35024246f63feb91d769d714dad ≤ v < 71aafa16d79b107b33837f60b6cbc7d0cb8c5708, 282b3a056225b35024246f63feb91d769d714dad ≤ v < f4002f1c669cc02e3763f479fc25ff1dfa9e2420, 282b3a056225b35024246f63feb91d769d714dad ≤ v < 50ff092633b06382e5091dd5b093ce943d4ac2f9, 282b3a056225b35024246f63feb91d769d714dad ≤ v < aef12b5ce793dea6b3a97a58fd0f946000ae8945, 282b3a056225b35024246f63feb91d769d714dad ≤ v < 0d8a12d7143126afdf9fbe2e3d438650dd6603ed, 282b3a056225b35024246f63feb91d769d714dad ≤ v < 35e0297a93c3c34a3924eeef816c03504e3ab5c5, 282b3a056225b35024246f63feb91d769d714dad ≤ v < f4c3d89fc986b0da196ddfc6cfe0ea5d5d08bec6, 4.4609ced2301be1df7e7ed2ef47d1d916674e6ba3b, 71aafa16d79b107b33837f60b6cbc7d0cb8c5708, f4002f1c669cc02e3763f479fc25ff1dfa9e2420, 50ff092633b06382e5091dd5b093ce943d4ac2f9, aef12b5ce793dea6b3a97a58fd0f946000ae8945, 0d8a12d7143126afdf9fbe2e3d438650dd6603ed, 35e0297a93c3c34a3924eeef816c03504e3ab5c5, f4c3d89fc986b0da196ddfc6cfe0ea5d5d08bec6

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.