RDS: validate the requested traces user input against max supported
Larger than supported value can lead to array read/write overflow. Reported-by: Colin Ian King <colin.king@canonical.com> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@oracle.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
1c966c5d26
commit
780e982905
1 changed files with 3 additions and 0 deletions
|
@ -310,6 +310,9 @@ static int rds_recv_track_latency(struct rds_sock *rs, char __user *optval,
|
||||||
if (copy_from_user(&trace, optval, sizeof(trace)))
|
if (copy_from_user(&trace, optval, sizeof(trace)))
|
||||||
return -EFAULT;
|
return -EFAULT;
|
||||||
|
|
||||||
|
if (trace.rx_traces > RDS_MSG_RX_DGRAM_TRACE_MAX)
|
||||||
|
return -EFAULT;
|
||||||
|
|
||||||
rs->rs_rx_traces = trace.rx_traces;
|
rs->rs_rx_traces = trace.rx_traces;
|
||||||
for (i = 0; i < rs->rs_rx_traces; i++) {
|
for (i = 0; i < rs->rs_rx_traces; i++) {
|
||||||
if (trace.rx_trace_pos[i] > RDS_MSG_RX_DGRAM_TRACE_MAX) {
|
if (trace.rx_trace_pos[i] > RDS_MSG_RX_DGRAM_TRACE_MAX) {
|
||||||
|
|
Loading…
Reference in a new issue