rseq: Fix segfault on registration when rseq_cs is non-zero
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d7822b1e24f2df5df98c76f0e94a5416349ff759 · < 2df285dab00fa03a3ef939b6cb0d0d0aeb0791db| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
rseq: Fix segfault on registration when rseq_cs is non-zero
The rseq_cs field is documented as being set to 0 by user-space prior to registration, however this is not currently enforced by the kernel. This can result in a segfault on return to user-space if the value stored in the rseq_cs field doesn't point to a valid struct rseq_cs.
The correct solution to this would be to fail the rseq registration when the rseq_cs field is non-zero. However, some older versions of glibc will reuse the rseq area of previous threads without clearing the rseq_cs field and will also terminate the process if the rseq registration fails in a secondary thread. This wasn't caught in testing because in this case the leftover rseq_cs does point to a valid struct rseq_cs.
What we can do is clear the rseq_cs field on registration when it's non-zero which will prevent segfaults on registration and won't break the glibc versions that reuse rseq areas on thread creation.
From the CVE record · Linux
The Linux kernel does not enforce that the rseq_cs field is zero during rseq registration. A local process registering with a nonzero rseq_cs value that does not point to a valid struct rseq_cs can segfault on return to user space; no other user interaction is described.
Engineers running Linux kernels with the affected rseq registration behavior should check their installations; affected versions are not specified.