vt_ioctl: fix array_index_nospec in vt_setactivate
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e97267cb4d1ee01ca0929638ec0fcbb0904f903d · < ffe54289b02e9c732d6f04c8ebbe3b2d90d32118| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
vt_ioctl: fix array_index_nospec in vt_setactivate
array_index_nospec ensures that an out-of-bounds value is set to zero on the transient path. Decreasing the value by one afterwards causes a transient integer underflow. vsa.console should be decreased first and then sanitized with array_index_nospec.
Kasper Acknowledgements: Jakob Koschel, Brian Johannesmeyer, Kaveh Razavi, Herbert Bos, Cristiano Giuffrida from the VUSec group at VU Amsterdam.
From the CVE record · Linux
The Linux kernel’s vt_setactivate function can cause a transient integer underflow when it decrements a console value after applying array_index_nospec. The input does not specify what an attacker could achieve or whether exploitation requires network access, authentication, or user interaction.
Engineers running the Linux kernel should check their deployments; affected versions are not specified.