Kernel memory exhaustion via seccomp refcount leak
Published Dec 9, 2025 · Updated May 11, 2026
Memory leak in the Linux kernel allows local users to consume kernel memory through a race involving seccomp and clone calls. copy_process() calls copy_seccomp() before checking fatal_signal_pending(), then aborts an embryonic task without reaching release_task() to decrement the shared filter reference. A local low-privileged account that can install a seccomp filter and control the signal timing can repeat the leak, degrading availability through kernel-memory exhaustion.
Summary
What happened
Memory leak in the Linux kernel allows local users to consume kernel memory through a race involving seccomp and clone calls. copy_process() calls copy_seccomp() before checking fatal_signal_pending(), then aborts an embryonic task without reaching release_task() to decrement the shared filter reference. A local low-privileged account that can install a seccomp filter and control the signal timing can repeat the leak, degrading availability through kernel-memory exhaustion.
The record
- CVE
- CVE-2022-50661
- Published
- Dec 9, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 9, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3a15fb6ed92cb32b0a83f406aa4a96f28c9adbc3 <29a69fa075d0577eff1137426669de21187ec182
- Affected versionversion=3a15fb6ed92cb32b0a83f406aa4a96f28c9adbc3 <5b81f0c6c60e35bf8153230ddfb03ebb14e17986
- Affected versionversion=3a15fb6ed92cb32b0a83f406aa4a96f28c9adbc3 <a1140cb215fa13dcec06d12ba0c3ee105633b7c4
- Affected versionversion=3a15fb6ed92cb32b0a83f406aa4a96f28c9adbc3 <a31a647a3d1073a642c5bbe3457731fb353cb980
- Affected versionversion=3a15fb6ed92cb32b0a83f406aa4a96f28c9adbc3 <d4a895e924b486f2a38463114509e1088ef4d7f5
- Affected versionversion=5.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo