CVE-2025-38067

CVE Enrichment

CVSS: 5.5 MEDIUM
EPSS: 0.57%
EPSS Percentile: 45.40%
CISA KEV: Not listed

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.

Technical Details

CVSS Version: 3.1
CNA / NVD Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Published: 18-Jun-2025 17:15
Last Modified: 17-Jun-2026 16:15
EPSS Date: 2026-10-12

CVSS Vector


            CVSS:3.1                            AV:L /
                            AC:L /
                            PR:L /
                            UI:N /
                            S:U /
                            C:N /
                            I:N /
                            A:H

Affected Products / Versions

linux / linux_kernel
Version / affected range: * · from (inclusive) 4.18 · before (exclusive) 5.10.240
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux / linux_kernel
Version / affected range: * · from (inclusive) 5.11 · before (exclusive) 5.15.189
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux / linux_kernel
Version / affected range: * · from (inclusive) 5.16 · before (exclusive) 6.1.146
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux / linux_kernel
Version / affected range: * · from (inclusive) 6.2 · before (exclusive) 6.6.99
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux / linux_kernel
Version / affected range: * · from (inclusive) 6.7 · before (exclusive) 6.12.39
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
linux / linux_kernel
Version / affected range: * · from (inclusive) 6.13 · before (exclusive) 6.14.9
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
debian / debian_linux
Version / affected range: 11.0
cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*

References

Last enrichment sync: 24-Oct-2026 05:22
Sources: NVD · FIRST EPSS · CISA KEV
Latest successful provider update; providers refresh independently.

Reported Context (1)

CVE-2025-38067 Q1 2026 Threat Review Details Risks Facing U.S. Public Sector

CVE (5)

Threat Actors (2)

Vendors (7)

Products (6)

Tools (1)

Industries (4)

Countries (2)

Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.