Menu

Star on GitHub · 3.2k

CVE-2022-50855

In the Linux kernel, the following vulnerability has been resolved: bpf: prevent leak of lsm program after failed attach In [0], we added the ability to bpf_prog_attach LSM programs to cgroups, b…

Published Dec 30, 2025EPSS 0.24%

Overview

CVE-2022-50855 is a known-severity vulnerability. It was published on December 30, 2025.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

bpf: prevent leak of lsm program after failed attach

In [0], we added the ability to bpf_prog_attach LSM programs to cgroups,

but in our validation to make sure the prog is meant to be attached to

BPF_LSM_CGROUP, we return too early if the check fails. This results in

lack of decrementing prog's refcnt (through bpf_prog_put)

leaving the LSM program alive past the point of the expected lifecycle.

This fix allows for the decrement to take place.

[0] https://lore.kernel.org/all/[email protected]/

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2022-50855?

CVE-2022-50855 is a known-severity vulnerability. It was published on December 30, 2025.

How severe is CVE-2022-50855?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2022-50855?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2022-50855?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2022-50855 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.