s390/syscalls: Add spectre boundary for syscall dispatch table
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 56e62a73702836017564eaacd5212e4d0fa1c01d · < 4d05dd18d867d58c6952a3bc260d244899da7256| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
s390/syscalls: Add spectre boundary for syscall dispatch table
The s390 syscall number is directly controlled by userspace, but does not have an array_index_nospec() boundary to prevent access past the syscall function pointer tables.
From the CVE record · Linux
The Linux kernel’s s390 syscall dispatch table lacks a Spectre boundary for syscall numbers controlled by userspace. A local user can supply a syscall number that may allow speculative access past the syscall function pointer tables; the input does not specify authentication requirements or additional user interaction.
Teams running Linux kernels on s390 systems should check their kernel versions; affected versions were not specified.