Linux Kernel up to 5.18.17/5.19.1 bpf jit_subprogs privilege escalation

Summaryinfo

A vulnerability labeled as problematic has been found in Linux Kernel up to 5.18.17/5.19.1. This vulnerability affects the function jit_subprogs of the component bpf. Executing a manipulation can lead to an unknown weakness. This vulnerability is tracked as CVE-2022-50168. No exploit exists. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Linux Kernel up to 5.18.17/5.19.1. It has been declared as problematic. This vulnerability affects the function jit_subprogs of the component bpf. The impact remains unknown. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: bpf, x86: fix freeing of not-finalized bpf_prog_pack syzbot reported a few issues with bpf_prog_pack [1], [2]. This only happens with multiple subprogs. In jit_subprogs(), we first call bpf_int_jit_compile() on each sub program. And then, we call it on each sub program again. jit_data is not freed in the first call of bpf_int_jit_compile(). Similarly we don't call bpf_jit_binary_pack_finalize() in the first call of bpf_int_jit_compile(). If bpf_int_jit_compile() failed for one sub program, we will call bpf_jit_binary_pack_finalize() for this sub program. However, we don't have a chance to call it for other sub programs. Then we will hit "goto out_free" in jit_subprogs(), and call bpf_jit_free on some subprograms that haven't got bpf_jit_binary_pack_finalize() yet. At this point, bpf_jit_binary_pack_free() is called and the whole 2MB page is freed erroneously. Fix this with a custom bpf_jit_free() for x86_64, which calls bpf_jit_binary_pack_finalize() if necessary. Also, with custom bpf_jit_free(), bpf_prog_aux->use_bpf_prog_pack is not needed any more, remove it. [1] https://syzkaller.appspot.com/bug?extid=2f649ec6d2eea1495a8f [2] https://syzkaller.appspot.com/bug?extid=87f65c75f4a72db05445

The advisory is available at git.kernel.org. This vulnerability was named CVE-2022-50168 since 06/18/2025. Technical details are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 246973 (Linux Distros Unpatched Vulnerability : CVE-2022-50168), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.18.18 or 5.19.2 eliminates this vulnerability. Applying the patch f91ce608a79c0db3e72bd63c23e011a9ebc31505/60e66074812dde9cde3d99cdd3caa9e40f1a4516/1d5f82d9dd477d5c66e0214a68c3e4f308eadd6d is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (246973) and CERT Bund (WID-SEC-2025-1350). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Affected

• Debian Linux
• Amazon Linux 2
• Red Hat Enterprise Linux
• Ubuntu Linux
• SUSE Linux
• Oracle Linux
• SUSE openSUSE
• Open Source Linux Kernel
• RESF Rocky Linux
• Dell Avamar
• Dell NetWorker
• Dell Secure Connect Gateway
• IBM QRadar SIEM

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 5.18.0
• 5.18.1
• 5.18.2
• 5.18.3
• 5.18.4
• 5.18.5
• 5.18.6
• 5.18.7
• 5.18.8
• 5.18.9
• 5.18.10
• 5.18.11
• 5.18.12
• 5.18.13
• 5.18.14
• 5.18.15
• 5.18.16
• 5.18.17
• 5.19.0
• 5.19.1

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion