cve.bz

CVE-2022-50650 linux linux

7.8 highEPSS 0.2%Fix available

High (7.8) in linux linux. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix reference state management for synchronous callbacks Currently, verifier verifies callback functions (sync and async) as if they will be executed once, (i.e. it explores execution state as if the function was being called once). The next insn to explore is set to start of subprog and the exit from nested frame is handled using curframe > 0 and prepare_func_exit. In case of async callback it uses a customized variant of push_stack simulating a kind of branch to set up custom state and execution context for the async callback. While this approach is simple and works when callback really will be executed only once, it is unsafe for all of our current helpers which are for_each style, i.e. they execute the callback multiple times. A callback releasing acquired references of the caller may do so multiple times, but currently verifier sees it as one call inside the frame, which then returns to caller. Hence, it thinks it released some reference that the cb e.g. got access through callback_ctx (register filled inside cb from spilled typed register on stack). Similarly, it may see that an acquire call is unpaired inside the callback, so the caller will copy the reference state of callback and then will have to release the register with new ref_obj_ids. But again, the callback may execute multiple times, but the verifier will only account for acquired references for a single symbolic execution of the callback, which will cause leaks. Note that for async callback case, things are different. While currently we have bpf_timer_set_callback which only executes it once, even for multiple executions it would be safe, as reference state is NULL and check_reference_leak would force program to release state before BPF_EXIT. The state is also unaffected by analysis for the caller frame. Hence async callback is safe. Since we want the reference state to be accessible, e.g. for pointers loaded from stack through callback_ctx's PTR_TO_STACK, we still have to copy caller's reference_state to callback's bpf_func_state, but we enforce that whatever references it adds to that reference_state has been released before it hits BPF_EXIT. This requires introducing a new callback_ref member in the reference state to distinguish between caller vs callee references. Hence, check_reference_leak now errors out if it sees we are in callback_fn and we have not released callback_ref refs. Since there can be multiple nested callbacks, like frame 0 -> cb1 -> cb2 etc. we need to also distinguish between whether this particular ref belongs to this callback frame or parent, and only error for our own, so we store state->frameno (which is always non-zero for callbacks). In short, callbacks can read parent reference_state, but cannot mutate it, to be able to use pointers acquired by the caller. They must only undo their changes (by releasing their own acquired_refs before BPF_EXIT) on top of caller reference_state before returning (at which point the caller and callback state will match anyway, so no need to copy it back to caller).

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-50650 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-50650?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-50650?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-50650 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2022-50650

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2022-50650](https://cve.bz/cve/badge/CVE-2022-50650.svg)](https://cve.bz/cve/CVE-2022-50650)

HTML:

<a href="https://cve.bz/cve/CVE-2022-50650"><img src="https://cve.bz/cve/badge/CVE-2022-50650.svg" alt="CVE-2022-50650"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.13 and later

Fixed in

ProductRelease lineFixed in
Linux5.155.15.75
Linux5.195.19.17
Linux6.06.0.3
Linuxlater releases6.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14linux6.0.3-1DEBIAN-CVE-2022-50650
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2022-50650
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2022-50650
Ubuntu20.04:LTSlinux-aws-5.155.15.0-1030.34~20.04.1UBUNTU-CVE-2022-50650
Ubuntu20.04:LTSlinux-azure-5.155.15.0-1033.40~20.04.1UBUNTU-CVE-2022-50650
Ubuntu20.04:LTSlinux-gcp-5.155.15.0-1029.36~20.04.1UBUNTU-CVE-2022-50650
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2022-50650
Ubuntu20.04:LTSlinux-hwe-5.15, linux-lowlatency-hwe-5.155.15.0-60.66~20.04.1UBUNTU-CVE-2022-50650
Ubuntu20.04:LTSlinux-intel-iotg-5.155.15.0-1025.30~20.04.1UBUNTU-CVE-2022-50650
Ubuntu20.04:LTSlinux-oracle-5.155.15.0-1029.35~20.04.1UBUNTU-CVE-2022-50650
Ubuntu20.04:LTSlinux-riscv-5.155.15.0-1029.33~20.04.1UBUNTU-CVE-2022-50650
Ubuntu22.04:LTSlinux, linux-lowlatency5.15.0-60.66UBUNTU-CVE-2022-50650
Ubuntu22.04:LTSlinux-aws5.15.0-1030.34UBUNTU-CVE-2022-50650
14 more for Ubuntu in the JSON and on Ubuntu's page.
Red Hatenterprise_linux:9::appstreamrv, perf, rtla and 24 more0:5.14.0-362.8.1.el9_3RHSA-2023:6583
Red Hatenterprise_linux:9::appstream, enterprise_linux:9::crb, enterprise_linux:9::nfv and 1 morebpftool-debuginfo0:7.2.0-362.8.1.el9_3RHSA-2023:6583
Red Hatenterprise_linux:9::baseosbpftool, bpftool-debuginfo0:7.2.0-362.8.1.el9_3RHSA-2023:6583
Red Hatenterprise_linux:9::baseoskernel, kernel-64k, kernel-core and 41 more0:5.14.0-362.8.1.el9_3RHSA-2023:6583
Red Hatenterprise_linux:9::crblibperf, perf-debuginfo, kernel-debuginfo and 12 more0:5.14.0-362.8.1.el9_3RHSA-2023:6583
Red Hatenterprise_linux:9::nfvkernel-rt, kernel-rt-kvm, kernel-rt-core and 20 more0:5.14.0-362.8.1.el9_3RHSA-2023:6583
Red Hatenterprise_linux:9::realtimekernel-rt, kernel-rt-core, perf-debuginfo and 18 more0:5.14.0-362.8.1.el9_3RHSA-2023:6583

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat.

Red Hat

Red Hat rates this Low.

Red Hat's statement

This flaw requires the ability to load BPF programs, which is typically restricted to privileged users or those with CAP_BPF capability. The impact is limited to denial of service through resource exhaustion.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelNot affected
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelFix deferred
Red Hat Enterprise Linux 8kernel-rtFix deferred
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2022-50650.

References

Check your stackJSON