The check_alu_op() function in kernel/bpf/verifier.c in the Linux kernel through v5.16-rc5 did not properly update bounds while handling the mov32 instruction, which allows local users to obtain potentially sensitive address information, aka a "pointer leak."
5.3.0-18.195.3.0-24.265.4.0-9.125.13.0-19.195.15.0-17.176.5.0-9.94.13.0-16.195.13.0-1005.65.15.0-1002.45.3.0-1003.35.3.0-1008.95.3.0-1009.105.3.0-1010.115.4.0-1005.54.15.0-1001.16.5.0-1008.85.0.0-1021.24~18.04.15.0.0-1022.25~18.04.15.0.0-1023.26~18.04.15.0.0-1024.27~18.04.15.0.0-1025.285.0.0-1027.305.11.0-1009.9~20.04.25.11.0-1014.15~20.04.15.11.0-1016.17~20.04.15.11.0-1017.18~20.04.15.11.0-1019.20~20.04.15.11.0-1020.21~20.04.25.11.0-1021.22~20.04.25.11.0-1022.23~20.04.15.11.0-1023.24~20.04.15.11.0-1025.27~20.04.1+2 moreExploitability
AV:LAC:LPR:LUI:NScope
S:UImpact
C:HI:NA:NCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N