Acknowledged
Created: Jun 18, 2025
Updated: Sep 4, 2026
Resolved Date: Jun 19, 2025
Found In Version: 10.25.33.1
Severity: Standard
Applicable for: Wind River Linux LTS 25
Component/s: Kernel
In the Linux kernel, the following vulnerability has been resolved:EOL][EOL]bpf, x86: fix freeing of not-finalized bpf_prog_pack[EOL][EOL]syzbot reported a few issues with bpf_prog_pack [1], [2]. This only happens[EOL]with multiple subprogs. In jit_subprogs(), we first call bpf_int_jit_compile()[EOL]on each sub program. And then, we call it on each sub program again. jit_data[EOL]is not freed in the first call of bpf_int_jit_compile(). Similarly we don't[EOL]call bpf_jit_binary_pack_finalize() in the first call of bpf_int_jit_compile().[EOL][EOL]If bpf_int_jit_compile() failed for one sub program, we will call[EOL]bpf_jit_binary_pack_finalize() for this sub program. However, we don't have a[EOL]chance to call it for other sub programs. Then we will hit "goto out_free" in[EOL]jit_subprogs(), and call bpf_jit_free on some subprograms that haven't got[EOL]bpf_jit_binary_pack_finalize() yet.[EOL][EOL]At this point, bpf_jit_binary_pack_free() is called and the whole 2MB page is[EOL]freed erroneously.[EOL][EOL]Fix this with a custom bpf_jit_free() for x86_64, which calls[EOL]bpf_jit_binary_pack_finalize() if necessary. Also, with custom[EOL]bpf_jit_free(), bpf_prog_aux->use_bpf_prog_pack is not needed any more,[EOL]remove it.[EOL][EOL][1] https://syzkaller.appspot.com/bug?extid=2f649ec6d2eea1495a8f[EOL][2] https://syzkaller.appspot.com/bug?extid=87f65c75f4a72db05445
CREATE(Triage):(User=lchen-cn) [CVE-2022-50168 (https://nvd.nist.gov/vuln/detail/CVE-2022-50168)