Answer in brief
CVE-2025-38067 records a Unknown severity vulnerability in rseq: Fix segfault on registration when rseq_cs is non-zero. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d7822b1e24f2df5df98c76f0e94a5416349ff759 <48900d839a3454050fd5822e34be8d54c4ec9b86 || >=d7822b1e24f2df5df98c76f0e94a5416349ff759 <3e4028ef31b69286c9d4878cee0330235f53f218 || >=d7822b1e24f2df5df98c76f0e94a5416349ff759 <b2b05d0dc2f4f0646922068af435aed5763d16ba || >=d7822b1e24f2df5df98c76f0e94a5416349ff759 <eaf112069a904b6207b4106ff083e0208232a2eb || >=d7822b1e24f2df5df98c76f0e94a5416349ff759 <f004f58d18a2d3dc761cf973ad27b4a5997bd876 || >=d7822b1e24f2df5df98c76f0e94a5416349ff759 <2df285dab00fa03a3ef939b6cb0d0d0aeb0791db || >=d7822b1e24f2df5df98c76f0e94a5416349ff759 <fd881d0a085fc54354414aed990ccf05f282ba53 | 48900d839a3454050fd5822e34be8d54c4ec9b86, 3e4028ef31b69286c9d4878cee0330235f53f218, b2b05d0dc2f4f0646922068af435aed5763d16ba, eaf112069a904b6207b4106ff083e0208232a2eb, f004f58d18a2d3dc761cf973ad27b4a5997bd876, 2df285dab00fa03a3ef939b6cb0d0d0aeb0791db, fd881d0a085fc54354414aed990ccf05f282ba53 |
| Linux/Linuxgeneric | 4.18 | Not reported |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.5 <* | * |
Published upstream
Jun 18, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 6, 2026
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.
Quoted source text, attributed separately from HOL analysis.