CVE-2025-38067: rseq: Fix segfault on registration when rseq_cs is non-zero
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.62% (FIRST EPSS); higher than 50.4% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 2df285dab00fa03a3ef939b6cb0d0d0aeb0791db, 3e4028ef31b69286c9d4878cee0330235f53f218, 48900d839a3454050fd5822e34be8d54c4ec9b86.
Low priority for now. Upgrade to Linux Linux 2df285dab00fa03a3ef939b6cb0d0d0aeb0791db, 3e4028ef31b69286c9d4878cee0330235f53f218, 48900d839a3454050fd5822e34be8d54c4ec9b86 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jun 18, 2025
- Updated
- Nov 5, 2026
- EPSS
- 0.6% · 50th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.18affected
- d7822b1e24f2df5df98c76f0e94a5416349ff759 and later · before 48900d839a3454050fd5822e34be8d54c4ec9b86affected · git
- d7822b1e24f2df5df98c76f0e94a5416349ff759 and later · before 3e4028ef31b69286c9d4878cee0330235f53f218affected · git
- d7822b1e24f2df5df98c76f0e94a5416349ff759 and later · before b2b05d0dc2f4f0646922068af435aed5763d16baaffected · git
- d7822b1e24f2df5df98c76f0e94a5416349ff759 and later · before eaf112069a904b6207b4106ff083e0208232a2ebaffected · git
- d7822b1e24f2df5df98c76f0e94a5416349ff759 and later · before f004f58d18a2d3dc761cf973ad27b4a5997bd876affected · git
- d7822b1e24f2df5df98c76f0e94a5416349ff759 and later · before 2df285dab00fa03a3ef939b6cb0d0d0aeb0791dbaffected · git
- d7822b1e24f2df5df98c76f0e94a5416349ff759 and later · before fd881d0a085fc54354414aed990ccf05f282ba53affected · git
- before 4.18not affected · semver
- 5.10.240 and later · up to and including 5.10.*not affected · semver
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel5.11 and later · before 5.15.189
- linux linux kernel5.16 and later · before 6.1.146
- linux linux kernel4.18 and later · before 5.10.240
- linux linux kernel6.7 and later · before 6.12.39
- linux linux kernel6.13 and later · before 6.14.9
- linux linux kernel6.2 and later · before 6.6.99
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.147-1 | 6.1.147-1 |
| Debian:13 | linux | before 6.12.41-1 | 6.12.41-1 |
| Debian:14 | linux | before 6.16.3-1 | 6.16.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38064Jun 18, 2025 · virtio: break and reset virtio devices on device_shutdown()22Monitor
- ← EarlierCVE-2025-38066Jun 18, 2025 · dm cache: prevent BUG_ON by blocking retries on failed device resumes22Monitor
- Later →CVE-2025-38069Jun 18, 2025 · PCI: endpoint: pci-epf-test: Fix double free that causes kernel to oops31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2df285dab00fa03a3ef939b6cb0d0d0aeb0791db | Vendor (CNA) |
| Linux Linux | 3e4028ef31b69286c9d4878cee0330235f53f218 | Vendor (CNA) |
| Linux Linux | 48900d839a3454050fd5822e34be8d54c4ec9b86 | Vendor (CNA) |
| Linux Linux | b2b05d0dc2f4f0646922068af435aed5763d16ba | Vendor (CNA) |
| Linux Linux | eaf112069a904b6207b4106ff083e0208232a2eb | Vendor (CNA) |
| Linux Linux | f004f58d18a2d3dc761cf973ad27b4a5997bd876 | Vendor (CNA) |
| Linux Linux | fd881d0a085fc54354414aed990ccf05f282ba53 | Vendor (CNA) |
| debian:linux | 6.1.147-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/3e4028ef31b69286c9d4878cee0330235f53f218
- git.kernel.org/stable/c/48900d839a3454050fd5822e34be8d54c4ec9b86
- git.kernel.org/stable/c/b2b05d0dc2f4f0646922068af435aed5763d16ba
- git.kernel.org/stable/c/eaf112069a904b6207b4106ff083e0208232a2eb
- git.kernel.org/stable/c/f004f58d18a2d3dc761cf973ad27b4a5997bd876
- git.kernel.org/stable/c/fd881d0a085fc54354414aed990ccf05f282ba53
- lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
- cert-portal.siemens.com/productcert/html/ssa-082556.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.