Review reviewHigh

CVE-2022-50168

Linux Linux, linux kernel

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_f...

CVSS
7.8
EPSS
0.21%
11.4% percentile
CISA KEV
Not listed
Published
2025.06.18
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.21%
Technical severityCVSS 7.8

Vulnerability overview

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_f...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 1022a5498f6f745c3b5fd3f050a5e11e7ca354f0 < f91ce608a79c0db3e72bd63c23e011a9ebc31505, >= 1022a5498f6f745c3b5fd3f050a5e11e7ca354f0 < 60e66074812dde9cde3d99cdd3caa9e40f1a4516, >= 1022a5498f6f745c3b5fd3f050a5e11e7ca354f0 < 1d5f82d9dd477d5c66e0214a68c3e4f308eadd6d, >= 5.18, >= 5.18 < 5.18.18, >= 5.19 < 5.19.2
Fixed versions
5.18.18, 5.19.2

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available