Answer in brief
CVE-2026-74588 records a Critical severity (CVSS 9.8) vulnerability in sctp: keep chunk->transport in step with the list it is queued on. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6575fb17230814b48b471727c8410c0aadff9274 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6b9e2ea2057113f3393990ba646d2d97c719a80d || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <874a7c2b5e184f06134fdfde27e9ce9271bafe58 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1adf929121e13e0b19200bb9fef715b918d483fe || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e2e7c1de0e226ca1b7fea2de57a6c9bca408709b || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2b3b5eec8b2c30ee237e3c31a6a38de9c39d804d || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5ccf35ef0ed6059cdf8b1f4606a6584d5b67166b || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <9f2cf069a9a72a2d6b97ca8b4c70e714aac99749 | 6575fb17230814b48b471727c8410c0aadff9274, 6b9e2ea2057113f3393990ba646d2d97c719a80d, 874a7c2b5e184f06134fdfde27e9ce9271bafe58, 1adf929121e13e0b19200bb9fef715b918d483fe, e2e7c1de0e226ca1b7fea2de57a6c9bca408709b, 2b3b5eec8b2c30ee237e3c31a6a38de9c39d804d, 5ccf35ef0ed6059cdf8b1f4606a6584d5b67166b, 9f2cf069a9a72a2d6b97ca8b4c70e714aac99749 |
| Linux/Linuxgeneric | 2.6.12 | Not reported |
Published upstream
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 22, 2026
In the Linux kernel, the following vulnerability has been resolved: sctp: keep chunk->transport in step with the list it is queued on __sctp_outq_flush_rtx() moves a gap-acked chunk onto another transport's transmitted list without updating chunk->transport: if (chunk->tsn_gap_acked) { list_move_tail(&chunk->transmitted_list, &transport->transmitted); continue; } The chunk then sits on a live transport's list while chunk->transport still names a different one. If that transport is removed - sctp_assoc_rm_peer() from an ASCONF Delete-IP - sctp_transport_free() RCU-frees it and the chunk is left with a dangling pointer. sctp_assoc_rm_peer() scrubs peer->transmitted and asoc->outqueue.out_chunk_list, but the chunk is on neither. The pointer is not followed while tsn_gap_acked is set. A SACK that reneges on the TSN clears the flag, and the next SACK reaches tchunk->transport->flight_size -= sctp_data_size(tchunk); inside the freed transport. KASAN reports a slab-use-after-free read in sctp_check_transmitted(), freed from sctp_assoc_rm_peer(). Both the removal and the SACKs come from the association peer. Set chunk->transport at the move. The ordinary resend path needs nothing: it reaches its list_move_tail() only after sctp_packet_append_chunk() returned SCTP_XMIT_OK, and __sctp_packet_append_chunk() has rebound the chunk by then. Discovered by XBOW, triaged by Baul Lee <[email protected]>
Quoted source text, attributed separately from HOL analysis.