CVE-2022-50862— bpf: prevent decl_tag from being referenced in func_proto
Quick assessment
Affected
Linux Linux
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于decl_tag在func_proto中被引用，可能导致内核警告。
Possible ATT&CK Techniques 2 AI
T1068 · Exploitation for Privilege Escalation T1135 · Network Share DiscoveryAffected Version Matrix 6
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Linux | Linux | bd16dee66ae4de3f1726c69ac901d2b7a53b0c86< e9dbb4c539d058852b76937dcd7347d3f38054f2 |
affected |
bd16dee66ae4de3f1726c69ac901d2b7a53b0c86< ea68376c8bed5cd156900852aada20c3a0874d17 |
affected | ||
5.16 |
affected | ||
< 5.16 |
unaffected | ||
6.0.7≤ 6.0.* |
unaffected | ||
6.1≤ * |
unaffected |
Get alerts for future matching vulnerabilities
Log in to subscribe
I. Basic Information for CVE-2022-50862
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
bpf: prevent decl_tag from being referenced in func_proto
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
bpf: prevent decl_tag from being referenced in func_proto
Syzkaller was able to hit the following issue:
------------[ cut here ]------------
WARNING: CPU: 0 PID: 3609 at kernel/bpf/btf.c:1946
btf_type_id_size+0x2d5/0x9d0 kernel/bpf/btf.c:1946
Modules linked in:
CPU: 0 PID: 3609 Comm: syz-executor361 Not tainted
6.0.0-syzkaller-02734-g0326074ff465 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 09/22/2022
RIP: 0010:btf_type_id_size+0x2d5/0x9d0 kernel/bpf/btf.c:1946
Code: ef e8 7f 8e e4 ff 41 83 ff 0b 77 28 f6 44 24 10 18 75 3f e8 6d 91
e4 ff 44 89 fe bf 0e 00 00 00 e8 20 8e e4 ff e8 5b 91 e4 ff <0f> 0b 45
31 f6 e9 98 02 00 00 41 83 ff 12 74 18 e8 46 91 e4 ff 44
RSP: 0018:ffffc90003cefb40 EFLAGS: 00010293
RAX: 0000000000000000 RBX: 0000000000000002 RCX: 0000000000000000
RDX: ffff8880259c0000 RSI: ffffffff81968415 RDI: 0000000000000005
RBP: ffff88801270ca00 R08: 0000000000000005 R09: 000000000000000e
R10: 0000000000000011 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000011 R14: ffff888026ee6424 R15: 0000000000000011
FS: 000055555641b300(0000) GS:ffff8880b9a00000(0000)
knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000f2e258 CR3: 000000007110e000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
btf_func_proto_check kernel/bpf/btf.c:4447 [inline]
btf_check_all_types kernel/bpf/btf.c:4723 [inline]
btf_parse_type_sec kernel/bpf/btf.c:4752 [inline]
btf_parse kernel/bpf/btf.c:5026 [inline]
btf_new_fd+0x1926/0x1e70 kernel/bpf/btf.c:6892
bpf_btf_load kernel/bpf/syscall.c:4324 [inline]
__sys_bpf+0xb7d/0x4cf0 kernel/bpf/syscall.c:5010
__do_sys_bpf kernel/bpf/syscall.c:5069 [inline]
__se_sys_bpf kernel/bpf/syscall.c:5067 [inline]
__x64_sys_bpf+0x75/0xb0 kernel/bpf/syscall.c:5067
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f0fbae41c69
Code: 28 c3 e8 2a 14 00 00 66 2e 0f 1f 84 00 00 00 00 00 48 89 f8 48 89
f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 c7 c1 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffc8aeb6228 EFLAGS: 00000246 ORIG_RAX: 0000000000000141
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f0fbae41c69
RDX: 0000000000000020 RSI: 0000000020000140 RDI: 0000000000000012
RBP: 00007f0fbae05e10 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007f0fbae05ea0
R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
</TASK>
Looks like it tries to create a func_proto which return type is
decl_tag. For the details, see Martin's spot on analysis in [0].
0: https://lore.kernel.org/bpf/CAKH8qBuQDLva_hHxxBuZzyAcYNO4ejhovz6TQeVSk8HY-2SO6g@mail.gmail.com/T/#mea6524b3fcd6298347432226e81b1e6155efc62c
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于decl_tag在func_proto中被引用，可能导致内核警告。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)
Affected Products
II. Public POCs for CVE-2022-50862
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POC
Premium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2022-50862
请登录查看更多情报信息。
Other References for CVE-2022-50862 (2)
Same Patch Batch · Linux · 2025-12-30 · 244 CVEs total
| CVE-2023-54184 | 9.8 CRITICAL | scsi: target: iscsit: Free cmds before session free |
| CVE-2023-54223 | 9.8 CRITICAL | net/mlx5e: xsk: Fix invalid buffer access for legacy rq |
| CVE-2023-54237 | 9.8 CRITICAL | net/smc: fix potential panic dues to unprotected smc_llc_srv_add_link() |
| CVE-2023-54257 | 9.8 CRITICAL | net: macb: fix a memory corruption in extended buffer descriptor mode |
| CVE-2023-54258 | 9.8 CRITICAL | cifs: fix potential oops in cifs_oplock_break |
| CVE-2023-54269 | 9.8 CRITICAL | SUNRPC: double free xprt_ctxt while still in use |
| CVE-2023-54280 | 9.8 CRITICAL | cifs: fix potential race when tree connecting ipc |
| CVE-2023-54292 | 9.8 CRITICAL | RDMA/irdma: Fix data race on CQP request done |
| CVE-2023-54203 | 9.1 CRITICAL | ksmbd: fix slab-out-of-bounds in init_smb2_rsp_hdr |
| CVE-2022-50880 | 8.8 HIGH | wifi: ath10k: add peer map clean up for peer delete in ath10k_sta_state() |
| CVE-2023-54262 | 8.8 HIGH | net/mlx5e: Don't clone flow post action attributes second time |
| CVE-2023-54214 | 8.8 HIGH | Bluetooth: L2CAP: Fix potential user-after-free |
| CVE-2023-54162 | 8.8 HIGH | ksmbd: fix possible memory leak in smb2_lock() |
| CVE-2023-54318 | 8.8 HIGH | net/smc: use smc_lgr_list.lock to protect smc_lgr_list.list iterate in smcr_port_add |
| CVE-2023-54250 | 8.2 HIGH | ksmbd: avoid out of bounds access in decode_preauth_ctxt() |
| CVE-2023-54164 | 8.0 HIGH | Bluetooth: ISO: fix iso_conn related locking and validity issues |
| CVE-2023-54206 | 7.8 HIGH | net/sched: flower: fix filter idr initialization |
| CVE-2023-54202 | 7.8 HIGH | drm/i915: fix race condition UAF in i915_perf_add_config_ioctl |
| CVE-2023-54210 | 7.8 HIGH | Bluetooth: hci_sync: Avoid use-after-free in dbg for hci_remove_adv_monitor() |
| CVE-2023-54243 | 7.8 HIGH | netfilter: ebtables: fix table blob use-after-free |
Showing top 20 of 244 CVEs. View all on vendor page → →
IV. Related Vulnerabilities
Same product: Linux
-
CVE-2026-98868
dm-pcache: reject a kset that overruns its segment -
CVE-2026-98867
dm-pcache: bound the logical key offset from persistent memo -
CVE-2026-98866
sched/cache: Introduce task_struct->sched_cache_grp to fix U -
CVE-2026-98865
sched_ext: Don't run ops.dequeue() with a DSQ lock held -
CVE-2026-98864
sched_ext: Wait for SCX_OPSS_DISPATCHING before reenqueueing
Same vendor: Linux
-
CVE-2026-98868
dm-pcache: reject a kset that overruns its segment -
CVE-2026-98867
dm-pcache: bound the logical key offset from persistent memo -
CVE-2026-98866
sched/cache: Introduce task_struct->sched_cache_grp to fix U -
CVE-2026-98865
sched_ext: Don't run ops.dequeue() with a DSQ lock held -
CVE-2026-98864
sched_ext: Wait for SCX_OPSS_DISPATCHING before reenqueueing
V. Comments for CVE-2022-50862
No comments yet