sctp: clear control chunk transport if it is being removed
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in Kernel fad4766a74220fe579c6fcaa10ba01c23529814f, Kernel 18d704bdd809377dfd81a3c2f42426763b5da227, Kernel 4d6b9cac6df5e0cfef1a66b3edd7aebdb9e4b7e7 and 12 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=8a07eb0a50aebc8c95478d49c28c7f8419a26cef <fad4766a74220fe579c6fcaa10ba01c23529814f, >=8a07eb0a50aebc8c95478d49c28c7f8419a26cef <18d704bdd809377dfd81a3c2f42426763b5da227, >=8a07eb0a50aebc8c95478d49c28c7f8419a26cef <4d6b9cac6df5e0cfef1a66b3edd7aebdb9e4b7e7, >=8a07eb0a50aebc8c95478d49c28c7f8419a26cef <6160e756db81d6cb63e3e2952efcf6c5134be385, >=8a07eb0a50aebc8c95478d49c28c7f8419a26cef <8de65194a04d2552cd39b6c67d942d490f22d174, >=8a07eb0a50aebc8c95478d49c28c7f8419a26cef <936658ec41c28c397ef390140e02d4c91ade92f0, >=8a07eb0a50aebc8c95478d49c28c7f8419a26cef <c9158ceaf27780ef64534ad72f44ffde3f8ccc49, >=8a07eb0a50aebc8c95478d49c28c7f8419a26cef <dbb3f418a8665ffb0514e1a9520ab6a1c5d4d886, =3.1 | fad4766a74220fe579c6fcaa10ba01c23529814f, 18d704bdd809377dfd81a3c2f42426763b5da227, 4d6b9cac6df5e0cfef1a66b3edd7aebdb9e4b7e7, 6160e756db81d6cb63e3e2952efcf6c5134be385, 8de65194a04d2552cd39b6c67d942d490f22d174, 936658ec41c28c397ef390140e02d4c91ade92f0, c9158ceaf27780ef64534ad72f44ffde3f8ccc49, dbb3f418a8665ffb0514e1a9520ab6a1c5d4d886 |
| linux-kernel: Kernel | >=5.11.0 <5.15.216, >=5.16.0 <6.1.183, >=6.13.0 <6.18.45, >=6.19.0 <7.1.9, >=6.2.0 <6.6.152, >=6.7.0 <6.12.104, >=3.1.0 <5.10.265 | 5.15.216, 6.1.183, 6.18.45, 7.1.9, 6.6.152, 6.12.104, 5.10.265 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket