net: atm: reject out-of-range traffic classes in QoS validation
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < e62adb157c2eaad9ad4867ec6cd9af5b9a51b1c7| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: atm: reject out-of-range traffic classes in QoS validation
Reject ATM traffic classes above ATM_ANYCLASS in check_tp(). SO_ATMQOS stores the supplied QoS after check_qos() succeeds, so accepting larger values leaves invalid traffic_class values in vcc->qos.
That bad state later reaches pvc_info(), which indexes class_name[] with vcc->qos.{rx,tp}.traffic_class. Values above ATM_ANYCLASS cause an out-of-bounds read when /proc/net/atm/pvc is read.
Tighten the existing QoS validation so invalid traffic_class values are rejected at the point where user supplied QoS is accepted.
From the CVE record · Linux
The Linux kernel’s ATM QoS validation can accept an out-of-range traffic class and store it in a socket’s QoS state. If user-supplied QoS contains such a value, a later read of /proc/net/atm/pvc can trigger an out-of-bounds read. The input does not specify authentication requirements.
Engineers running Linux kernels with ATM support should check their systems; affected versions are not specified.