LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50219: bpf: Fix KASAN use-after-free Read in compute_effective_progs

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix KASAN use-after-free Read in compute_effective_progs Syzbot found a Use After Free bug in compute_effective_progs(). The reproducer creates a number of BPF links, and causes a fault injected alloc to fail, while calling bpf_link_detach on them. Link detach triggers the link to be freed by bpf_link_free(), which calls __cgroup_bpf_detach() and update_effective_progs(). If the memory allocation in this function fails, the function restores the pointer to the bpf_cgroup_link on the cgroup list, but the memory gets freed just after it returns. After this, every subsequent call to update_effective_progs() causes this already deallocated pointer to be dereferenced in prog_list_length(), and triggers KASAN UAF error. To fix this issue don't preserve the pointer to the prog or link in the list, but remove it and replace it with a dummy prog without shrinking the table. The subsequent call to __cgroup_bpf_detach() or __cgroup_bpf_detach() will correct it.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-50219 is a Linux kernel memory-safety bug in BPF cgroup link handling. Under an allocation-failure path during BPF link detach, the kernel could later dereference freed memory. The public record does not provide CVSS, CWE, affected distributions, or evidence of active exploitation.

Executive priority

Track and remediate through normal kernel patch management unless local risk factors raise urgency. Business urgency increases for shared Linux platforms, container hosts, and systems where untrusted users can influence BPF or cgroup activity.

Technical view

The issue is a use-after-free read in compute_effective_progs(). When update_effective_progs() fails allocation during bpf_link_detach, a freed bpf_cgroup_link pointer can remain on a cgroup list and later be dereferenced by prog_list_length(). The fix replaces preserved list pointers with a dummy program until detach cleanup corrects state.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions or vendor kernels that include the vulnerable BPF cgroup link code. The bundle lists Linux versions including 5.7, 5.10.138, 5.15.61, 5.18.18, 5.19.2, and 6.0 as affected, but does not map distributions.

Exploitation context

The source describes a syzbot-discovered kernel bug involving many BPF links and fault-injected allocation failure. KEV is false and no cited source reports active exploitation. The bundle does not establish whether practical exploitation exists outside controlled testing.

Researcher notes

Evidence supports a kernel BPF/cgroup use-after-free read fixed in Linux stable commits. Missing data includes CVSS, CWE, distro mappings, privilege requirements, impact beyond KASAN detection, and public exploitability. Avoid expanding affected scope beyond Linux kernel versions and backports confirmed by vendors.

Mitigation direction

  • Apply vendor-supported kernel updates containing the referenced Linux stable fixes.
  • Check Linux stable and distribution advisories for backport status.
  • Prioritize systems that allow BPF or cgroup management by less-trusted users.
  • Reboot into the fixed kernel after maintenance approval.
  • Avoid treating scanner detection as sufficient remediation.

Validation and detection

  • Inventory running Linux kernel versions across production and build systems.
  • Compare deployed kernels with vendor advisories for CVE-2022-50219.
  • Confirm the running kernel includes an applicable referenced stable fix or backport.
  • Review exposure of hosts using BPF, containers, or cgroup-heavy workloads.
  • Avoid reproducer testing on production systems.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50219 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
6Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxaf6eea57437a830293eab56246b6025cc7d46ee7, af6eea57437a830293eab56246b6025cc7d46ee7, af6eea57437a830293eab56246b6025cc7d46ee7, af6eea57437a830293eab56246b6025cc7d46ee7, af6eea57437a830293eab56246b6025cc7d46ee7unaffected
LinuxLinux5.7, 0, 5.10.138, 5.15.61, 5.18.18, 5.19.2, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.