CVE-2022-50219 json
bpf: Fix KASAN use-after-free Read in compute_effective_progs
published 2025-06-18 16 mo ago modified 2026-08-05 3 mo ago also EUVD-2022-55480
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 14%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.10.138, 5.15.61, 5.18.18, 5.19.2, 6.0
- linux Debian 14, Debian 13, Debian 12 6.0.2-1
debian advisories DEBIAN-CVE-2022-50219
- linux Ubuntu 22.04 LTS 5.15.0-53.59
- linux-aws Ubuntu 22.04 LTS 5.15.0-1023.27
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1022.29
- linux-gke Ubuntu 22.04 LTS 5.15.0-1020.25
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1018.21
- linux-kvm Ubuntu 22.04 LTS 5.15.0-1021.26
- linux-azure Ubuntu 22.04 LTS 5.15.0-1023.29
- linux-gkeop Ubuntu 22.04 LTS 5.15.0-1008.12
ubuntu advisories UBUNTU-CVE-2022-50219
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel RHEL 9 5.14.0-284.11.1.el9_2
- perf RHEL 9 5.14.0-284.11.1.el9_2
- rtla RHEL 9 5.14.0-284.11.1.el9_2
- bpftool RHEL 9 7.0.0-284.11.1.el9_2
- kernel-64k RHEL 9 5.14.0-284.11.1.el9_2
- kernel-core RHEL 9 5.14.0-284.11.1.el9_2
- kernel-tools RHEL 9 5.14.0-284.11.1.el9_2
- python3-perf RHEL 9 5.14.0-284.11.1.el9_2
red hat advisories RHSA-2023:2458RHSA-2020:4431
- git.kernel.org/stable/c/3527e3cbb84d8868c4d4e91ba55915f96d39ec3d commit
- git.kernel.org/stable/c/1f8ca9c40e6222ce431e9ba5dae3cccce8ef9443 commit
- git.kernel.org/stable/c/6336388715afa419cc97d0255bda3bba1b96b7ca commit
- git.kernel.org/stable/c/be001f9da71eaa3b61e186fb88bde3279728bdca commit
- git.kernel.org/stable/c/4c46091ee985ae84c60c5e95055d779fcd291d87 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-50219 updated cvss 5.5
kernel: bpf: Fix KASAN use-after-free Read in compute_effective_progs
-
Red Hat Enterprise Linux 8 kernel-rt, kernel-rt-kvm, kernel-rt-core, kernel-rt-modules, kernel-rt-debug-kvm, kernel-rt-debug-core, +6 more Red Hat Enterprise Linux 9 kernel-rt, kernel-rt-kvm, kernel-rt-core, kernel-rt-modules, kernel-rt-debug-kvm, kernel-rt-debug-core, +12 moreaffected: workaround, no fix available “Fix deferred”
-
Red Hat CodeReady Linux Builder (v. 8) kernel-debuginfo-common-x86_64 4.18.0-240.el8, kernel-debuginfo-common-aarch64 4.18.0-240.el8, kernel-debuginfo-common-ppc64le 4.18.0-240.el8fixed: vendor fix RHSA-2020:4431
-
Red Hat Enterprise Linux AppStream (v. 9) perf 5.14.0-284.11.1.el9_2, rtla 5.14.0-284.11.1.el9_2, kernel-devel-matched 5.14.0-284.11.1.el9_2, kernel-64k-devel-matched 5.14.0-284.11.1.el9_2, kernel-debug-devel-matched 5.14.0-284.11.1.el9_2, kernel-debuginfo-common-s390x 5.14.0-284.11.1.el9_2, +5 morefixed: vendor fix RHSA-2023:2458
-
Red Hat Enterprise Linux BaseOS (v. 8) perf 4.18.0-240.el8, kernel 4.18.0-240.el8, bpftool 4.18.0-240.el8, kernel-core 4.18.0-240.el8, kernel-tools 4.18.0-240.el8, python3-perf 4.18.0-240.el8, +15 morefixed: vendor fix RHSA-2020:4431
-
Red Hat Enterprise Linux BaseOS (v. 9) bpftool 7.0.0-284.11.1.el9_2, kernel 5.14.0-284.11.1.el9_2, kernel-64k 5.14.0-284.11.1.el9_2, kernel-core 5.14.0-284.11.1.el9_2, kernel-tools 5.14.0-284.11.1.el9_2, python3-perf 5.14.0-284.11.1.el9_2, +28 more Red Hat Enterprise Linux CRB (v. 9) kernel-debuginfo-common-s390x 5.14.0-284.11.1.el9_2, kernel-debuginfo-common-x86_64 5.14.0-284.11.1.el9_2, kernel-debuginfo-common-aarch64 5.14.0-284.11.1.el9_2, kernel-debuginfo-common-ppc64le 5.14.0-284.11.1.el9_2fixed: vendor fix RHSA-2023:2458
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-416 Use After Free
- Technology feeds
References
-
git.kernel.org
/stable/c/3527e3cbb84d8868c4d4e91ba55915f96d39ec3d
patch
-
git.kernel.org
/stable/c/1f8ca9c40e6222ce431e9ba5dae3cccce8ef9443
patch
-
git.kernel.org
/stable/c/6336388715afa419cc97d0255bda3bba1b96b7ca
patch
-
git.kernel.org
/stable/c/be001f9da71eaa3b61e186fb88bde3279728bdca
patch
-
git.kernel.org
/stable/c/4c46091ee985ae84c60c5e95055d779fcd291d87
patch
Sources
- CVE List CVE-2022-50219
- NVD CVE-2022-50219
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.