sctp: auth: verify auth requirement when auth_chunk is NULL
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ bbd0d59809f923ea2b540cbd781b32110e249f6e · < 18957373920caf5cdaf5cf32e5d1d7a99ca7700a| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
sctp: auth: verify auth requirement when auth_chunk is NULL
sctp_auth_chunk_verify() returns true unconditionally when chunk->auth_chunk is NULL, silently skipping authentication. This is incorrect when:
1. skb_clone() failed in the BH receive path, leaving auth_chunk NULL. In sctp_endpoint_bh_rcv() asoc is NULL for new connections, so the early sctp_auth_recv_cid() check cannot catch this.
2. No AUTH chunk precedes COOKIE-ECHO, so skb_clone() is never called and auth_chunk remains NULL.
Fix by checking sctp_auth_recv_cid() when auth_chunk is NULL: if authentication is required, return false to drop the chunk; otherwise continue normally.
From the CVE record · Linux
The Linux kernel's SCTP authentication check can accept a chunk without verifying authentication when auth_chunk is NULL, even if authentication is required. This can occur in the receive path if skb_clone() fails, or when no AUTH chunk precedes COOKIE-ECHO. The described receive path includes new connections; no prior authentication or user interaction is described.
Engineers running Linux kernels with SCTP support should check their exposure; affected versions are not specified.