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/6a2c1007.428ffe26.258b27.015d.GAE@google.com/T/#u
Published: 2026-08-15
Score: 9.8 Critical
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

In the Linux kernel’s TIPC networking stack, a use‑after‑free bug exists in tipc_l2_send_msg() when tipc_disable_l2_media() clears media_ptr after calling synchronize_net() while the pointer still points to a valid device. RCU readers can race this sequence and later access a freed memory location during bearer_disable(), causing the kernel to dereference freed memory. This memory corruption can crash the kernel or, if attacker‑controlled data is placed in the freed region, lead to arbitrary kernel code execution.

Affected Systems

All Linux kernel versions that lack commit 0d8a12d7, which introduces the early clearing of b->media_ptr, are vulnerable. The issue is not vendor specific; any distribution shipping a kernel without this patch is affected.

Risk and Exploitability

Based on the description, the likely attack vector requires an adversary to send specially crafted TIPC packets to a target system where the TIPC module is enabled. It is inferred that local or privileged access is needed to manipulate the TIPC traffic or reproduce the race condition. The EPSS score is under 1% and the vulnerability is not listed in CISA KEV, indicating a low probability of public exploitation. Nevertheless, the CVSS score of 9.8 classifies it as Critical, meaning that exploitation could trigger a kernel panic or privilege escalation on affected systems.

Generated by OpenCVE AI on August 22, 2026 at 01:13 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the Linux kernel to a release that includes the commit fixing tipc_disable_l2_media() before calling synchronize_net()
  • If an immediate kernel upgrade is not possible, disable the TIPC kernel module or block TIPC traffic at the firewall to reduce the attack surface
  • Enable kernel crash dump logging and monitor for abnormal panics or memory corruption indicators that may signal exploitation attempts.

Generated by OpenCVE AI on August 22, 2026 at 01:13 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Thu, 20 Aug 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-825
References
Metrics threat_severity

None

threat_severity

Moderate


Mon, 17 Aug 2026 14:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-416
CWE-788

Mon, 17 Aug 2026 06:00:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}


Sat, 15 Aug 2026 18:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-416
CWE-788

Sat, 15 Aug 2026 06:15:00 +0000

Type Values Removed Values Added
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/6a2c1007.428ffe26.258b27.015d.GAE@google.com/T/#u
Title tipc: fix UAF in tipc_l2_send_msg()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-17T05:45:03.215Z

Reserved: 2026-08-15T05:44:03.876Z

Link: CVE-2026-74255

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-15T06:22:24.627

Modified: 2026-08-17T06:19:18.780

Link: CVE-2026-74255

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-08-15T00:00:00Z

Links: CVE-2026-74255 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-08-22T01:15:05Z

Weaknesses
  • CWE-825

    Expired Pointer Dereference