Strix
57.3K

CVE-2026-74688

Unknown

Last modified

CVE-2026-74688 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: sctp: clear control chunk transport if it is being removed sctp_make_heartbeat_ack() caches the destination transport in chunk->transport without taking a reference. When src_out_of_asoc_ok is enabled, the HEARTBEAT ACK may remain queued on control_chunk_list instead of being transmitted immediately. If the peer transport is removed while the chunk is still queued, sctp_assoc_rm_peer() drops the transport and schedules it for RCU freeing, but only clears cached transport pointers in out_chunk_list.

Description

In the Linux kernel, the following vulnerability has been resolved: sctp: clear control chunk transport if it is being removed sctp_make_heartbeat_ack() caches the destination transport in chunk->transport without taking a reference. When src_out_of_asoc_ok is enabled, the HEARTBEAT ACK may remain queued on control_chunk_list instead of being transmitted immediately. If the peer transport is removed while the chunk is still queued, sctp_assoc_rm_peer() drops the transport and schedules it for RCU freeing, but only clears cached transport pointers in out_chunk_list. The queued control chunk therefore retains a dangling transport pointer. Once an ASCONF_ACK clears the suppression and the queued control chunk is transmitted, SCTP dereferences the stale transport pointer, leading to a use-after-free. Fix this by also clearing chunk->transport for queued control chunks in control_chunk_list when removing the transport.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 8a07eb0a50aebc8c95478d49c28c7f8419a26cef, < dbb3f418a8665ffb0514e1a9520ab6a1c5d4d886; >= 8a07eb0a50aebc8c95478d49c28c7f8419a26cef, < fad4766a74220fe579c6fcaa10ba01c23529814f; >= 8a07eb0a50aebc8c95478d49c28c7f8419a26cef, < 936658ec41c28c397ef390140e02d4c91ade92f0; >= 8a07eb0a50aebc8c95478d49c28c7f8419a26cef, < 8de65194a04d2552cd39b6c67d942d490f22d174; >= 8a07eb0a50aebc8c95478d49c28c7f8419a26cef, < 6160e756db81d6cb63e3e2952efcf6c5134be385; >= 8a07eb0a50aebc8c95478d49c28c7f8419a26cef, < 18d704bdd809377dfd81a3c2f42426763b5da227; >= 8a07eb0a50aebc8c95478d49c28c7f8419a26cef, < 4d6b9cac6df5e0cfef1a66b3edd7aebdb9e4b7e7; >= 8a07eb0a50aebc8c95478d49c28c7f8419a26cef, < c9158ceaf27780ef64534ad72f44ffde3f8ccc49
LinuxLinux3.1

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-74688?
In the Linux kernel, the following vulnerability has been resolved: sctp: clear control chunk transport if it is being removed sctp_make_heartbeat_ack() caches the destination transport in chunk->transport without taking a reference. When src_out_of_asoc_ok is enabled, the HEARTBEAT ACK may remain queued on control_chunk_list instead of being transmitted immediately. If the peer transport is removed while the chunk is still queued, sctp_assoc_rm_peer() drops the transport and schedules it for RCU freeing, but only clears cached transport pointers in out_chunk_list. The queued control chunk therefore retains a dangling transport pointer. Once an ASCONF_ACK clears the suppression and the queued control chunk is transmitted, SCTP dereferences the stale transport pointer, leading to a use-after-free. Fix this by also clearing chunk->transport for queued control chunks in control_chunk_list when removing the transport.
How severe is CVE-2026-74688?
Severity scoring for CVE-2026-74688 is pending analysis.
How do I fix CVE-2026-74688?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-74688?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST