{"timestamp":"2024-02-22T19:34:47.236363Z","id":"CVE-2023-52452","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}

[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","programFiles":["kernel/bpf/verifier.c","tools/testing/selftests/bpf/progs/iters.c","tools/testing/selftests/bpf/progs/test_global_func16.c","tools/testing/selftests/bpf/progs/verifier_basic_stack.c","tools/testing/selftests/bpf/progs/verifier_int_ptr.c","tools/testing/selftests/bpf/progs/verifier_raw_stack.c","tools/testing/selftests/bpf/progs/verifier_var_off.c","tools/testing/selftests/bpf/verifier/atomic_cmpxchg.c","tools/testing/selftests/bpf/verifier/calls.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","versions":[{"version":"01f810ace9ed37255f27608a0864abebccf0aab3","lessThan":"0954982db8283016bf38e9db2da5adf47a102e19","versionType":"git","status":"affected"},{"version":"01f810ace9ed37255f27608a0864abebccf0aab3","lessThan":"fbcf372c8eda2290470268e0afb5ab5d5f5d5fde","versionType":"git","status":"affected"},{"version":"01f810ace9ed37255f27608a0864abebccf0aab3","lessThan":"6b4a64bafd107e521c01eec3453ce94a3fb38529","versionType":"git","status":"affected"},{"version":"f3c4b01689d392373301e6e60d1b02c5b4020afc","versionType":"git","status":"affected"},{"version":"d1b725ea5d104caea250427899f4e2e3ab15b4fc","versionType":"git","status":"affected"},{"version":"5.10.33","lessThan":"5.11","versionType":"semver","status":"affected"},{"version":"5.11.17","lessThan":"5.12","versionType":"semver","status":"affected"}]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","programFiles":["kernel/bpf/verifier.c","tools/testing/selftests/bpf/progs/iters.c","tools/testing/selftests/bpf/progs/test_global_func16.c","tools/testing/selftests/bpf/progs/verifier_basic_stack.c","tools/testing/selftests/bpf/progs/verifier_int_ptr.c","tools/testing/selftests/bpf/progs/verifier_raw_stack.c","tools/testing/selftests/bpf/progs/verifier_var_off.c","tools/testing/selftests/bpf/verifier/atomic_cmpxchg.c","tools/testing/selftests/bpf/verifier/calls.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","versions":[

https://git.kernel.org/stable/c/0954982db8283016bf38e9db2da5adf47a102e19

https://git.kernel.org/stable/c/6b4a64bafd107e521c01eec3453ce94a3fb38529

https://git.kernel.org/stable/c/fbcf372c8eda2290470268e0afb5ab5d5f5d5fde

NIST AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

NIST CWE-665

OR
     *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.12 up to (excluding) 6.6.14
     *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7.0 up to (excluding) 6.7.2

https://git.kernel.org/stable/c/0954982db8283016bf38e9db2da5adf47a102e19 No Types Assigned

https://git.kernel.org/stable/c/0954982db8283016bf38e9db2da5adf47a102e19 Patch

https://git.kernel.org/stable/c/6b4a64bafd107e521c01eec3453ce94a3fb38529 No Types Assigned

https://git.kernel.org/stable/c/6b4a64bafd107e521c01eec3453ce94a3fb38529 Patch

https://git.kernel.org/stable/c/fbcf372c8eda2290470268e0afb5ab5d5f5d5fde No Types Assigned

https://git.kernel.org/stable/c/fbcf372c8eda2290470268e0afb5ab5d5f5d5fde Patch

In the Linux kernel, the following vulnerability has been resolved:

bpf: Fix accesses to uninit stack slots

Privileged programs are supposed to be able to read uninitialized stack
memory (ever since 6715df8d5) but, before this patch, these accesses
were permitted inconsistently. In particular, accesses were permitted
above state->allocated_stack, but not below it. In other words, if the
stack was already "large enough", the access was permitted, but
otherwise the access was rejected instead of being allowed to "grow the
stack". This undesired rejection was happening in two places:
- in check_stack_slot_within_bounds()
- in check_stack_range_initialized()
This patch arranges for these accesses to be permitted. A bunch of tests
that were relying on the old rejection had to change; all of them were
changed to add also run unprivileged, in which case the old behavior
persists. One tests couldn't be updated - global_func16 - because it
can't run unprivileged for other reasons.

This patch also fixes the tracking of the stack size for variable-offset
reads. This second fix is bundled in the same commit as the first one
because they're inter-related. Before this patch, writes to the stack
using registers containing a variable offset (as opposed to registers
with fixed, known values) were not properly contributing to the
function's needed stack size. As a result, it was possible for a program
to verify, but then to attempt to read out-of-bounds data at runtime
because a too small stack had been allocated for it.

Each function tracks the size of the stack it needs in
bpf_subprog_info.stack_depth, which is maintained by
update_stack_depth(). For regular memory accesses, check_mem_access()
was calling update_state_depth() but it was passing in only the fixed
part of the offset register, ignoring the variable offset. This was
incorrect; the minimum possible value of that register should be used
instead.

This tracking is now fixed by centralizing the tracking of stack size in
grow_stack_state(), and by lifting the calls t

Linux https://git.kernel.org/stable/c/0954982db8283016bf38e9db2da5adf47a102e19 [No types assigned]

Linux https://git.kernel.org/stable/c/6b4a64bafd107e521c01eec3453ce94a3fb38529 [No types assigned]

Linux https://git.kernel.org/stable/c/fbcf372c8eda2290470268e0afb5ab5d5f5d5fde [No types assigned]