Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-50661: seccomp: Move copy_seccomp() to no failure path.

Noroxi assessment

Priority: Monitor (action score 0/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.26% (FIRST EPSS).
  • Fixed version: Linux Linux 29a69fa075d0577eff1137426669de21187ec182, 5b81f0c6c60e35bf8153230ddfb03ebb14e17986, a1140cb215fa13dcec06d12ba0c3ee105633b7c4.

Low priority for now. Upgrade to Linux Linux 29a69fa075d0577eff1137426669de21187ec182, 5b81f0c6c60e35bf8153230ddfb03ebb14e17986, a1140cb215fa13dcec06d12ba0c3ee105633b7c4 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: Move copy_seccomp() to no failure path. Our syzbot instance reported memory leaks in do_seccomp() [0], similar to the report [1]. It shows that we miss freeing struct seccomp_filter and some objects included in it. We can reproduce the issue with the program below [2] which calls one seccomp() and two clone() syscalls. The first clone()d child exits earlier than its parent and sends a signal to kill it during the second clone(), more precisely before the fatal_signal_pending() test in copy_process(). When the parent receives the signal, it has to destroy the embryonic process and return -EINTR to user space. In the failure path, we have to call seccomp_filter_release() to decrement the filter's refcount. Initially, we called it in free_task() called from the failure path, but the commit 3a15fb6ed92c ("seccomp: release filter after task is fully dead") moved it to release_task() to notify user space as early as possible that the filter is no longer used. To keep the change and current seccomp refcount semantics, let's move copy_seccomp() just after the signal check and add a WARN_ON_ONCE() in free_task() for future debugging. [0]: unreferenced object 0xffff8880063add00 (size 256): comm "repro_seccomp", pid 230, jiffies 4294687090 (age 9.914s) hex dump (first 32 bytes): 01 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 ................ ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ backtrace: do_seccomp (./include/linux/slab.h:600 ./include/linux/slab.h:733 kernel/seccomp.c:666 kernel/seccomp.c:708 kernel/seccomp.c:1871 kernel/seccomp.c:1991) do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:120) unreferenced object 0xffffc90000035000 (size 4096): comm "repro_seccomp", pid 230, jiffies 4294687090 (age 9.915s) hex dump (first 32 bytes): 01 00 00 00 00 00 00 00 00 00 00 00 05 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: __vmalloc_node_range (mm/vmalloc.c:3226) __vmalloc_node (mm/vmalloc.c:3261 (discriminator 4)) bpf_prog_alloc_no_stats (kernel/bpf/core.c:91) bpf_prog_alloc (kernel/bpf/core.c:129) bpf_prog_create_from_user (net/core/filter.c:1414) do_seccomp (kernel/seccomp.c:671 kernel/seccomp.c:708 kernel/seccomp.c:1871 kernel/seccomp.c:1991) do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:120) unreferenced object 0xffff888003fa1000 (size 1024): comm "repro_seccomp", pid 230, jiffies 4294687090 (age 9.915s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: bpf_prog_alloc_no_stats (./include/linux/slab.h:600 ./include/linux/slab.h:733 kernel/bpf/core.c:95) bpf_prog_alloc (kernel/bpf/core.c:129) bpf_prog_create_from_user (net/core/filter.c:1414) do_seccomp (kernel/seccomp.c:671 kernel/seccomp.c:708 kernel/seccomp.c:1871 kernel/seccomp.c:1991) do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:120) unreferenced object 0xffff888006360240 (size 16): comm "repro_seccomp", pid 230, jiffies 4294687090 (age 9.915s) hex dump (first 16 bytes): 01 00 37 00 76 65 72 6c e0 83 01 06 80 88 ff ff ..7.verl........ backtrace: bpf_prog_store_orig_filter (net/core/filter.c:1137) bpf_prog_create_from_user (net/core/filter.c:1428) do_seccomp (kernel/seccomp.c:671 kernel/seccomp.c:708 kernel/seccomp.c:1871 kernel/seccomp.c:1991) do_syscall_64 (arch/x86/entry/common.c:50 arch/x86/entry/common.c:80) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:120) unreferenced object 0xffff888 ---truncated---

—No exploit Fix available
Published
Dec 9, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 18th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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.

Follow CVE-2022-50661

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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.

—

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

    • 5.9affected
    • 3a15fb6ed92cb32b0a83f406aa4a96f28c9adbc3 and later · before d4a895e924b486f2a38463114509e1088ef4d7f5affected · git
    • 3a15fb6ed92cb32b0a83f406aa4a96f28c9adbc3 and later · before a31a647a3d1073a642c5bbe3457731fb353cb980affected · git
    • 3a15fb6ed92cb32b0a83f406aa4a96f28c9adbc3 and later · before 29a69fa075d0577eff1137426669de21187ec182affected · git
    • 3a15fb6ed92cb32b0a83f406aa4a96f28c9adbc3 and later · before 5b81f0c6c60e35bf8153230ddfb03ebb14e17986affected · git
    • 3a15fb6ed92cb32b0a83f406aa4a96f28c9adbc3 and later · before a1140cb215fa13dcec06d12ba0c3ee105633b7c4affected · git
    • before 5.9not affected · semver
    • 5.10.180 and later · up to and including 5.10.*not affected · semver
    • 5.15.86 and later · up to and including 5.15.*not affected · semver
    • 6.0.16 and later · up to and including 6.0.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.4-16.1.4-1
Red Hat:enterprise_linux:9::appstreambpftool-debuginfobefore 0:7.0.0-284.30.1.el9_20:7.0.0-284.30.1.el9_2
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-284.30.1.el9_20:5.14.0-284.30.1.el9_2
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-develbefore 0:5.14.0-284.30.1.el9_20:5.14.0-284.30.1.el9_2
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-284.30.1.el9_20:5.14.0-284.30.1.el9_2
Red Hat:enterprise_linux:9::appstreamkernel-64k-debuginfobefore 0:5.14.0-284.30.1.el9_20:5.14.0-284.30.1.el9_2
Red Hat:enterprise_linux:9::appstreamkernel-64k-develbefore 0:5.14.0-284.30.1.el9_20:5.14.0-284.30.1.el9_2
Red Hat:enterprise_linux:9::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-284.30.1.el9_20:5.14.0-284.30.1.el9_2
Red Hat:enterprise_linux:9::appstreamkernel-debug-debuginfobefore 0:5.14.0-284.30.1.el9_20:5.14.0-284.30.1.el9_2
Red Hat:enterprise_linux:9::appstreamkernel-debug-develbefore 0:5.14.0-284.30.1.el9_20:5.14.0-284.30.1.el9_2
Red Hat:enterprise_linux:9::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-284.30.1.el9_20:5.14.0-284.30.1.el9_2
Red Hat:enterprise_linux:9::appstreamkernel-debuginfobefore 0:5.14.0-284.30.1.el9_20:5.14.0-284.30.1.el9_2
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-284.30.1.el9_20:5.14.0-284.30.1.el9_2
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-284.30.1.el9_20:5.14.0-284.30.1.el9_2
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-284.30.1.el9_20:5.14.0-284.30.1.el9_2
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-284.30.1.el9_20:5.14.0-284.30.1.el9_2
Red Hat:enterprise_linux:9::appstreamkernel-develbefore 0:5.14.0-284.30.1.el9_20:5.14.0-284.30.1.el9_2
Red Hat:enterprise_linux:9::appstreamkernel-devel-matchedbefore 0:5.14.0-284.30.1.el9_20:5.14.0-284.30.1.el9_2
Red Hat:enterprise_linux:9::appstreamkernel-docbefore 0:5.14.0-284.30.1.el9_20:5.14.0-284.30.1.el9_2
Red Hat:enterprise_linux:9::appstreamkernel-tools-debuginfobefore 0:5.14.0-284.30.1.el9_20:5.14.0-284.30.1.el9_2
Red Hat:enterprise_linux:9::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-284.30.1.el9_20:5.14.0-284.30.1.el9_2
Red Hat:enterprise_linux:9::appstreamkernel-zfcpdump-develbefore 0:5.14.0-284.30.1.el9_20:5.14.0-284.30.1.el9_2
Red Hat:enterprise_linux:9::appstreamkernel-zfcpdump-devel-matchedbefore 0:5.14.0-284.30.1.el9_20:5.14.0-284.30.1.el9_2
Red Hat:enterprise_linux:9::appstreamperfbefore 0:5.14.0-284.30.1.el9_20:5.14.0-284.30.1.el9_2

+36

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2022-50659Dec 9, 2025 · hwrng: geode - Fix PCI device refcount leak
    0Monitor
  • ← EarlierCVE-2022-50660Dec 9, 2025 · wifi: ipw2200: fix memory leak in ipw_wdev_init()
    0Monitor
  • Later →CVE-2022-50662Dec 9, 2025 · RDMA/hns: fix memory leak in hns_roce_alloc_mr()
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux29a69fa075d0577eff1137426669de21187ec182Vendor (CNA)
Linux Linux5b81f0c6c60e35bf8153230ddfb03ebb14e17986Vendor (CNA)
Linux Linuxa1140cb215fa13dcec06d12ba0c3ee105633b7c4Vendor (CNA)
Linux Linuxa31a647a3d1073a642c5bbe3457731fb353cb980Vendor (CNA)
Linux Linuxd4a895e924b486f2a38463114509e1088ef4d7f5Vendor (CNA)
debian:linux6.1.4-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.0.0-284.30.1.el9_2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-284.30.1.el9_2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-284.30.1.el9_2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-284.30.1.el9_2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-284.30.1.el9_2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-284.30.1.el9_2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-284.30.1.el9_2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-284.30.1.el9_2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-284.30.1.el9_2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-284.30.1.el9_2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-284.30.1.el9_2 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-284.30.1.el9_2 · Red Hat:enterprise_linux:9::appstreamPackage 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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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

All records