CVE-2025-21834: seccomp: passthrough uretprobe systemcall without filtering

Published Mar 6, 2025
·
Updated

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 x8664 and isn't expected to ever be supported in i386.

[kees: minimized changes for easier backporting, tweaked commit log]

Affected Software

5 affected componentsFixes available
Linux Kernel
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1
Linux Linux kernel>=6.11<6.12.14
Linux Linux kernel>=6.13<6.13.3
Linux Linux kernel=6.14-rc1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1

Event History

Mar 6, 2025
CVE Published
via MITRE·04:22 PM
Data Sourced
via MITRE·04:22 PM
Description
Data Sourced
via Red Hat·05:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·05:15 PM
Description
Data Sourced
via NVD·05:15 PM
RemedySeverityAffected Software
Apr 8, 2025
Data Sourced
via Ubuntu·06:51 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-21834?

CVE-2025-21834 has been classified as a high severity vulnerability due to its potential to cause segmentation faults in affected applications.

2

How do I fix CVE-2025-21834?

To fix CVE-2025-21834, update to the latest version of the Linux kernel where this vulnerability has been resolved.

3

Which versions of the Linux kernel are affected by CVE-2025-21834?

CVE-2025-21834 affects versions of the Linux kernel prior to the patches applied in the recent updates.

4

What is a uretprobe in relation to CVE-2025-21834?

A uretprobe is a dynamic tracing mechanism in the Linux kernel that allows developers to monitor the function return points of user-space applications, which is exploited in CVE-2025-21834.

5

How does CVE-2025-21834 impact Docker containers?

CVE-2025-21834 causes processes running inside Docker containers to experience segmentation faults when uretprobes are attached, leading to application instability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203