CVE-2025-21834: seccomp: passthrough uretprobe systemcall without filtering
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.18% (FIRST EPSS).
- 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 5a262628f4cf2437d863fe41f9d427177b87664c, cf6cb56ef24410fb5308f9655087f1eddf4452e6, fa80018aa5be10c35e9fa896b7b4061a8dce3eed.
Low priority for now. Upgrade to Linux Linux 5a262628f4cf2437d863fe41f9d427177b87664c, cf6cb56ef24410fb5308f9655087f1eddf4452e6, fa80018aa5be10c35e9fa896b7b4061a8dce3eed 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: seccomp: passthrough uretprobe systemcall without filtering When attaching uretprobes to processes running inside docker, the attached process is segfaulted when encountering the retprobe. The reason is that now that uretprobe is a system call the default seccomp filters in docker block it as they only allow a specific set of known syscalls. This is true for other userspace applications which use seccomp to control their syscall surface. Since uretprobe is a "kernel implementation detail" system call which is not used by userspace application code directly, it is impractical and there's very little point in forcing all userspace applications to explicitly allow it in order to avoid crashing tracked processes. Pass this systemcall through seccomp without depending on configuration. Note: uretprobe is currently only x86_64 and isn't expected to ever be supported in i386. [kees: minimized changes for easier backporting, tweaked commit log]
- Published
- Mar 6, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 7th 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.1%
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 |
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
- 6.11affected
- ff474a78cef5cb5f32be52fe25b78441327a2e7c and later · before 5a262628f4cf2437d863fe41f9d427177b87664caffected · git
- ff474a78cef5cb5f32be52fe25b78441327a2e7c and later · before fa80018aa5be10c35e9fa896b7b4061a8dce3eedaffected · git
- ff474a78cef5cb5f32be52fe25b78441327a2e7c and later · before cf6cb56ef24410fb5308f9655087f1eddf4452e6affected · git
- before 6.11not affected · semver
- 6.12.14 and later · up to and including 6.12.*not affected · semver
- 6.13.3 and later · up to and including 6.13.*not affected · semver
- 6.14 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.11 and later · before 6.12.14
- linux linux kernel6.13 and later · before 6.13.3
- linux linux kernel6.14
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.50.1.el10_2 | 6.12.0-211.50.1.el10_2 |
+96
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-21829Mar 6, 2025 · RDMA/rxe: Fix the warning "__rxe_cleanup+0x12c/0x170 [rdma_rxe]"22Monitor
- ← EarlierCVE-2025-21833Mar 6, 2025 · iommu/vt-d: Avoid use of NULL after WARN_ON_ONCE22Monitor
- Later →CVE-2024-58051Mar 6, 2025 · ipmi: ipmb: Add check devm_kasprintf() returned value22Monitor
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 | 5a262628f4cf2437d863fe41f9d427177b87664c | Vendor (CNA) |
| Linux Linux | cf6cb56ef24410fb5308f9655087f1eddf4452e6 | Vendor (CNA) |
| Linux Linux | fa80018aa5be10c35e9fa896b7b4061a8dce3eed | Vendor (CNA) |
| almalinux:kernel | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-211.50.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.12.15-1 · Debian:13 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-debuginfo-common-ppc64le | 0:6.12.0-211.50.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| rocky linux:kernel | 0:6.12.0-211.50.1.el10_2 · Rocky Linux:10 | 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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.