CVE-2025-38067

MEDIUM EPSS 37.0%
Published Jun 18, 20251y ago · Modified Jun 17, 20262w ago
5.5 CVSS 3.1
Medium
Find Similar
Published Jun 18, 2025 1y ago
Last Modified Jun 17, 2026 2w ago

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.

CVSS Details

Base Score
5.5
Exploitability
1.8
Impact
3.6
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Attack Vector Local
Attack Complexity Low
Privileges Required Low
User Interaction None
Scope Unchanged
Confidentiality None
Integrity None
Availability High

Threat Intelligence

EPSS Exploit Probability
37.0% percentile
Exploit & Patch Status
No Known Exploit
Patch Available

Affected Products 7

VendorProductVersionRange
linuxlinux_kernel*≥4.18  –  <5.10.240
linuxlinux_kernel*≥5.11  –  <5.15.189
linuxlinux_kernel*≥5.16  –  <6.1.146
linuxlinux_kernel*≥6.2  –  <6.6.99
linuxlinux_kernel*≥6.7  –  <6.12.39
linuxlinux_kernel*≥6.13  –  <6.14.9
debiandebian_linux11.0any

References 10

  • cert-portal.siemens.com https://cert-portal.siemens.com/productcert/html/ssa-082556.html
  • git.kernel.org https://git.kernel.org/stable/c/2df285dab00fa03a3ef939b6cb0d0d0aeb0791db
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/3e4028ef31b69286c9d4878cee0330235f53f218
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/48900d839a3454050fd5822e34be8d54c4ec9b86
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/b2b05d0dc2f4f0646922068af435aed5763d16ba
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/eaf112069a904b6207b4106ff083e0208232a2eb
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/f004f58d18a2d3dc761cf973ad27b4a5997bd876
    Patch
  • git.kernel.org https://git.kernel.org/stable/c/fd881d0a085fc54354414aed990ccf05f282ba53
    Patch
  • lists.debian.org https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
    Third Party Advisory
  • lists.debian.org https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html
    Third Party Advisory

Remediation

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