In the Linux kernel, the following vulnerability has been resolved: tipc: fix use-after-free of the discoverer in tipc_disc_rcv() bearer_disable()… (CVE-2026-64543)
A use-after-free vulnerability in the Linux kernel's TIPC (Transparent Inter-Process Communication) UDP bearer was resolved. The issue occurs because the discoverer object is freed without proper synchronization, leading to a use-after-free condition in tipc_disc_rcv() during UDP packet processing. This vulnerability is reachable from an unprivileged user namespace when TIPC and UDP media support are enabled. The fix involves freeing the discoverer object using an RCU callback and ensuring all callbacks complete before module unload.
AI Analysis
Technical Summary
The Linux kernel TIPC subsystem had a use-after-free vulnerability (CVE-2026-64543) in the UDP bearer implementation. The bearer_disable() function frees the discoverer object with a plain kfree(), but tipc_disc_rcv() can still dereference this freed object under RCU read lock during UDP packet reception. L2 bearers avoid this due to synchronize_net(), but UDP bearers defer cleanup, causing a race condition. The fix changes the freeing method to use kfree_rcu() with an RCU callback and adds an rcu_barrier() on module exit to prevent use-after-free of module text. The vulnerability is reachable from unprivileged user namespaces via the TIPCv2 generic netlink family, which lacks admin permission checks on bearer commands.
Potential Impact
Successful exploitation can lead to use-after-free memory corruption in the kernel, potentially causing system crashes, denial of service, or escalation of privileges due to the high impact on confidentiality, integrity, and availability as indicated by the CVSS vector. The vulnerability is exploitable locally with low privileges in a user namespace environment where TIPC and UDP media are enabled.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability has been resolved in the Linux kernel source by changing the freeing mechanism to use RCU callbacks and adding synchronization barriers on module unload. Users should monitor official Linux kernel advisories and apply updates when available. No generic mitigations are specified by the vendor advisory.
In the Linux kernel, the following vulnerability has been resolved: tipc: fix use-after-free of the discoverer in tipc_disc_rcv() bearer_disable()… (CVE-2026-64543)
Description
A use-after-free vulnerability in the Linux kernel's TIPC (Transparent Inter-Process Communication) UDP bearer was resolved. The issue occurs because the discoverer object is freed without proper synchronization, leading to a use-after-free condition in tipc_disc_rcv() during UDP packet processing. This vulnerability is reachable from an unprivileged user namespace when TIPC and UDP media support are enabled. The fix involves freeing the discoverer object using an RCU callback and ensuring all callbacks complete before module unload.
CVSS v3.1
Score 7.8high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel TIPC subsystem had a use-after-free vulnerability (CVE-2026-64543) in the UDP bearer implementation. The bearer_disable() function frees the discoverer object with a plain kfree(), but tipc_disc_rcv() can still dereference this freed object under RCU read lock during UDP packet reception. L2 bearers avoid this due to synchronize_net(), but UDP bearers defer cleanup, causing a race condition. The fix changes the freeing method to use kfree_rcu() with an RCU callback and adds an rcu_barrier() on module exit to prevent use-after-free of module text. The vulnerability is reachable from unprivileged user namespaces via the TIPCv2 generic netlink family, which lacks admin permission checks on bearer commands.
Potential Impact
Successful exploitation can lead to use-after-free memory corruption in the kernel, potentially causing system crashes, denial of service, or escalation of privileges due to the high impact on confidentiality, integrity, and availability as indicated by the CVSS vector. The vulnerability is exploitable locally with low privileges in a user namespace environment where TIPC and UDP media are enabled.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability has been resolved in the Linux kernel source by changing the freeing mechanism to use RCU callbacks and adding synchronization barriers on module unload. Users should monitor official Linux kernel advisories and apply updates when available. No generic mitigations are specified by the vendor advisory.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-vfvw-gp7q-pgrc
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64543"]
- Ecosystems
- []
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a6b72d09c2644c7f8476ab7
Added to database: 07/30/2026, 15:50:40 UTC
Last enriched: 07/30/2026, 19:25:14 UTC
Last updated: 07/31/2026, 23:17:49 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.