sctp: prevent possible shift-out-of-bounds in sctp_transport_update_rto
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b58537a1f5629bdc98a8b9dc2051ce0e952f6b4b · < 1cfa4eac275cc4875755c1303d48a4ddfe507ca8| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
sctp: prevent possible shift-out-of-bounds in sctp_transport_update_rto
syzbot reported a possible shift-out-of-bounds [1]
Blamed commit added rto_alpha_max and rto_beta_max set to 1000.
It is unclear if some sctp users are setting very large rto_alpha and/or rto_beta.
In order to prevent user regression, perform the test at run time.
Also add READ_ONCE() annotations as sysctl values can change under us.
[1]
From the CVE record · Linux
The Linux kernel’s SCTP transport RTO update can perform an out-of-bounds shift when RTO parameters are very large. A syzbot report triggered a UBSAN warning; the input does not establish whether an attacker can trigger it, or any network, authentication, or user-interaction requirements.
Engineers running Linux kernels with SCTP support should check their deployments; affected versions are not specified.