In the Linux kernel, the following vulnerability has been resolved: sctp: clear control chunk transport if it is being removed… (CVE-2026-74688)
A use-after-free vulnerability in the Linux kernel SCTP implementation was resolved by clearing cached transport pointers for queued control chunks when the transport is removed. The issue occurs because SCTP caches a transport pointer without taking a reference, and if the peer transport is removed while a control chunk is still queued, the chunk retains a dangling pointer. When the chunk is later transmitted, this leads to dereferencing a stale pointer, causing a use-after-free condition.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel SCTP subsystem involves sctp_make_heartbeat_ack() caching the destination transport in chunk->transport without a reference. When src_out_of_asoc_ok is enabled, HEARTBEAT ACK chunks may remain queued instead of being sent immediately. If the peer transport is removed during this time, sctp_assoc_rm_peer() drops and schedules the transport for freeing but only clears cached transport pointers in out_chunk_list, not in control_chunk_list. Consequently, queued control chunks retain dangling transport pointers. Upon transmission triggered by an ASCONF_ACK, SCTP dereferences the stale pointer, causing a use-after-free. The fix clears chunk->transport for queued control chunks in control_chunk_list when removing the transport.
Potential Impact
This use-after-free vulnerability could lead to kernel memory corruption, potentially causing system crashes or other undefined behavior. The exact impact depends on exploitation conditions but involves dereferencing freed memory within the SCTP kernel code.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to clear cached transport pointers for queued control chunks when the transport is removed, preventing use-after-free. Users should apply the official kernel updates that include this fix. Patch status is not explicitly confirmed in the provided data; check the vendor advisory for current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: sctp: clear control chunk transport if it is being removed… (CVE-2026-74688)
Description
A use-after-free vulnerability in the Linux kernel SCTP implementation was resolved by clearing cached transport pointers for queued control chunks when the transport is removed. The issue occurs because SCTP caches a transport pointer without taking a reference, and if the peer transport is removed while a control chunk is still queued, the chunk retains a dangling pointer. When the chunk is later transmitted, this leads to dereferencing a stale pointer, causing a use-after-free condition.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel SCTP subsystem involves sctp_make_heartbeat_ack() caching the destination transport in chunk->transport without a reference. When src_out_of_asoc_ok is enabled, HEARTBEAT ACK chunks may remain queued instead of being sent immediately. If the peer transport is removed during this time, sctp_assoc_rm_peer() drops and schedules the transport for freeing but only clears cached transport pointers in out_chunk_list, not in control_chunk_list. Consequently, queued control chunks retain dangling transport pointers. Upon transmission triggered by an ASCONF_ACK, SCTP dereferences the stale pointer, causing a use-after-free. The fix clears chunk->transport for queued control chunks in control_chunk_list when removing the transport.
Potential Impact
This use-after-free vulnerability could lead to kernel memory corruption, potentially causing system crashes or other undefined behavior. The exact impact depends on exploitation conditions but involves dereferencing freed memory within the SCTP kernel code.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to clear cached transport pointers for queued control chunks when the transport is removed, preventing use-after-free. Users should apply the official kernel updates that include this fix. Patch status is not explicitly confirmed in the provided data; check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-3vfv-7x6v-8jg6
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-74688"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a8a27f1acd9273b499bc782
Added to database: 08/22/2026, 22:51:29 UTC
Last enriched: 08/23/2026, 00:23:45 UTC
Last updated: 08/23/2026, 01:32:08 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.