In the Linux kernel, the following vulnerability has been resolved: tipc: fix slab-use-after-free Read in tipc_aead_decrypt_done tipc_aead_decrypt()… (CVE-2026-63801)
A use-after-free vulnerability was identified and resolved in the Linux kernel's TIPC (Transparent Inter-Process Communication) crypto decrypt path. The issue occurs because the decrypt function does not properly take a network namespace reference before asynchronous decryption, leading to potential dereferencing of freed memory if the network namespace is torn down during the async operation. This vulnerability was fixed by mirroring the encrypt path's reference management to ensure safe asynchronous callbacks.
AI Analysis
Technical Summary
CVE-2026-63801 is a slab-use-after-free vulnerability in the Linux kernel's TIPC crypto decrypt path. The function tipc_aead_decrypt() calls crypto_aead_decrypt() asynchronously without taking a reference on the network namespace (netns), unlike the encrypt path. If the netns is torn down during the asynchronous operation, the completion callback tipc_aead_decrypt_done() dereferences freed memory, leading to a use-after-free. The fix involves taking a net reference before crypto_aead_decrypt(), maintaining it across asynchronous returns, and releasing it properly after completion, preventing access to freed memory.
Potential Impact
The vulnerability allows the kernel to read freed memory during asynchronous decryption operations in TIPC, which can lead to undefined behavior such as kernel crashes or potential information disclosure. The issue arises when the network namespace is destroyed while an asynchronous decrypt operation is pending, causing use-after-free reads in kernel memory.
Mitigation Recommendations
A fix for this vulnerability has been implemented upstream by adding proper network namespace reference counting in the decrypt path to prevent use-after-free conditions. Users should apply the official Linux kernel patches that include this fix. Since this is a kernel vulnerability, upgrading to a kernel version containing this patch is the recommended remediation. Patch status is not explicitly confirmed here; check the vendor or Linux kernel advisories for the exact fixed versions and apply updates accordingly.
In the Linux kernel, the following vulnerability has been resolved: tipc: fix slab-use-after-free Read in tipc_aead_decrypt_done tipc_aead_decrypt()… (CVE-2026-63801)
Description
A use-after-free vulnerability was identified and resolved in the Linux kernel's TIPC (Transparent Inter-Process Communication) crypto decrypt path. The issue occurs because the decrypt function does not properly take a network namespace reference before asynchronous decryption, leading to potential dereferencing of freed memory if the network namespace is torn down during the async operation. This vulnerability was fixed by mirroring the encrypt path's reference management to ensure safe asynchronous callbacks.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-63801 is a slab-use-after-free vulnerability in the Linux kernel's TIPC crypto decrypt path. The function tipc_aead_decrypt() calls crypto_aead_decrypt() asynchronously without taking a reference on the network namespace (netns), unlike the encrypt path. If the netns is torn down during the asynchronous operation, the completion callback tipc_aead_decrypt_done() dereferences freed memory, leading to a use-after-free. The fix involves taking a net reference before crypto_aead_decrypt(), maintaining it across asynchronous returns, and releasing it properly after completion, preventing access to freed memory.
Potential Impact
The vulnerability allows the kernel to read freed memory during asynchronous decryption operations in TIPC, which can lead to undefined behavior such as kernel crashes or potential information disclosure. The issue arises when the network namespace is destroyed while an asynchronous decrypt operation is pending, causing use-after-free reads in kernel memory.
Mitigation Recommendations
A fix for this vulnerability has been implemented upstream by adding proper network namespace reference counting in the decrypt path to prevent use-after-free conditions. Users should apply the official Linux kernel patches that include this fix. Since this is a kernel vulnerability, upgrading to a kernel version containing this patch is the recommended remediation. Patch status is not explicitly confirmed here; check the vendor or Linux kernel advisories for the exact fixed versions and apply updates accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-xqwj-phvh-5pp9
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-63801"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27ad2a4a8d59891315aa
Added to database: 07/19/2026, 19:38:21 UTC
Last enriched: 07/19/2026, 20:19:29 UTC
Last updated: 07/20/2026, 17:26:47 UTC
Views: 10
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.