# CVE-2023-53790: linux: In the Linux kernel, the following vulnerability has been resolved: bpf: Zeroing allocated object from slab in bpf m... CVE-2023-53790 is fixed in 20 products on 1 platform, first by ALAS2023-2023-138, released March 20, 2023. It is not reported as exploited. Patch Radar priority: High. - Web page: https://patchblox.com/security/cve/CVE-2023-53790 - Priority: High - CVSS: 7.8 (high) - EPSS: 0.0015 - CISA KEV: not listed - Exploited (vendor report): no - Publicly disclosed: no - Published: Mar 20, 2023 ## Description In the Linux kernel, the following vulnerability has been resolved: bpf: Zeroing allocated object from slab in bpf memory allocator Currently the freed element in bpf memory allocator may be immediately reused, for htab map the reuse will reinitialize special fields in map value (e.g., bpf_spin_lock), but lookup procedure may still access these special fields, and it may lead to hard-lockup as shown below: NMI backtrace for cpu 16 CPU: 16 PID: 2574 Comm: htab.bin Tainted: G L 6.1.0+ #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), RIP: 0010:queued_spin_lock_slowpath+0x283/0x2c0 ...... Call Trace: copy_map_value_locked+0xb7/0x170 bpf_map_copy_value+0x113/0x3c0 __sys_bpf+0x1c67/0x2780 __x64_sys_bpf+0x1c/0x20 do_syscall_64+0x30/0x60 entry_SYSCALL_64_after_hwframe+0x46/0xb0 ...... For htab map, just like the preallocated case, these is no need to initialize these special fields in map value again once these fields have been initialized. For preallocated htab map, these fields are initialized through __GFP_ZERO in bpf_map_area_alloc(), so do the similar thing for non-preallocated htab in bpf memory allocator. And there is no need to use __GFP_ZERO for per-cpu bpf memory allocator, because __alloc_percpu_gfp() does it implicitly. ## Where it's fixed | Platform | Product | Fixed in | Fix | Released | |---|---|---|---|---| | Linux | bpftool amzn 2023 | 6.1.19-30.43.amzn2023 | [ALAS2023-2023-138](https://patchblox.com/security/data/fix/linux/alas2023-2023-138.md) | Mar 20, 2023 | | Linux | bpftool-debuginfo amzn 2023 | 6.1.19-30.43.amzn2023 | [ALAS2023-2023-138](https://patchblox.com/security/data/fix/linux/alas2023-2023-138.md) | Mar 20, 2023 | | Linux | kernel amzn 2023 | 6.1.19-30.43.amzn2023 | [ALAS2023-2023-138](https://patchblox.com/security/data/fix/linux/alas2023-2023-138.md) | Mar 20, 2023 | | Linux | kernel-debuginfo amzn 2023 | 6.1.19-30.43.amzn2023 | [ALAS2023-2023-138](https://patchblox.com/security/data/fix/linux/alas2023-2023-138.md) | Mar 20, 2023 | | Linux | kernel-debuginfo-common-aarch64 amzn 2023 | 6.1.19-30.43.amzn2023 | [ALAS2023-2023-138](https://patchblox.com/security/data/fix/linux/alas2023-2023-138.md) | Mar 20, 2023 | | Linux | kernel-debuginfo-common-x86_64 amzn 2023 | 6.1.19-30.43.amzn2023 | [ALAS2023-2023-138](https://patchblox.com/security/data/fix/linux/alas2023-2023-138.md) | Mar 20, 2023 | | Linux | kernel-devel amzn 2023 | 6.1.19-30.43.amzn2023 | [ALAS2023-2023-138](https://patchblox.com/security/data/fix/linux/alas2023-2023-138.md) | Mar 20, 2023 | | Linux | kernel-headers amzn 2023 | 6.1.19-30.43.amzn2023 | [ALAS2023-2023-138](https://patchblox.com/security/data/fix/linux/alas2023-2023-138.md) | Mar 20, 2023 | | Linux | kernel-libbpf amzn 2023 | 6.1.19-30.43.amzn2023 | [ALAS2023-2023-138](https://patchblox.com/security/data/fix/linux/alas2023-2023-138.md) | Mar 20, 2023 | | Linux | kernel-libbpf-devel amzn 2023 | 6.1.19-30.43.amzn2023 | [ALAS2023-2023-138](https://patchblox.com/security/data/fix/linux/alas2023-2023-138.md) | Mar 20, 2023 | | Linux | kernel-libbpf-static amzn 2023 | 6.1.19-30.43.amzn2023 | [ALAS2023-2023-138](https://patchblox.com/security/data/fix/linux/alas2023-2023-138.md) | Mar 20, 2023 | | Linux | kernel-livepatch-6.1.19-30.43 amzn 2023 | 1.0-0.amzn2023 | [ALAS2023-2023-138](https://patchblox.com/security/data/fix/linux/alas2023-2023-138.md) | Mar 20, 2023 | | Linux | kernel-tools amzn 2023 | 6.1.19-30.43.amzn2023 | [ALAS2023-2023-138](https://patchblox.com/security/data/fix/linux/alas2023-2023-138.md) | Mar 20, 2023 | | Linux | kernel-tools-debuginfo amzn 2023 | 6.1.19-30.43.amzn2023 | [ALAS2023-2023-138](https://patchblox.com/security/data/fix/linux/alas2023-2023-138.md) | Mar 20, 2023 | | Linux | kernel-tools-devel amzn 2023 | 6.1.19-30.43.amzn2023 | [ALAS2023-2023-138](https://patchblox.com/security/data/fix/linux/alas2023-2023-138.md) | Mar 20, 2023 | | Linux | linux Debian 12.15 (bookworm) | 6.1.20-1 | [DEBIAN-CVE-2023-53790](https://patchblox.com/security/data/fix/linux/debian-cve-2023-53790.md) | Dec 9, 2025 | | Linux | linux Debian 13.5 (trixie) | 6.1.20-1 | [DEBIAN-CVE-2023-53790](https://patchblox.com/security/data/fix/linux/debian-cve-2023-53790.md) | Dec 9, 2025 | | Linux | linux Debian 14 | 6.1.20-1 | [DEBIAN-CVE-2023-53790](https://patchblox.com/security/data/fix/linux/debian-cve-2023-53790.md) | Dec 9, 2025 | | Linux | perf amzn 2023 | 6.1.19-30.43.amzn2023 | [ALAS2023-2023-138](https://patchblox.com/security/data/fix/linux/alas2023-2023-138.md) | Mar 20, 2023 | | Linux | perf-debuginfo amzn 2023 | 6.1.19-30.43.amzn2023 | [ALAS2023-2023-138](https://patchblox.com/security/data/fix/linux/alas2023-2023-138.md) | Mar 20, 2023 | | Linux | python3-perf amzn 2023 | 6.1.19-30.43.amzn2023 | [ALAS2023-2023-138](https://patchblox.com/security/data/fix/linux/alas2023-2023-138.md) | Mar 20, 2023 | | Linux | python3-perf-debuginfo amzn 2023 | 6.1.19-30.43.amzn2023 | [ALAS2023-2023-138](https://patchblox.com/security/data/fix/linux/alas2023-2023-138.md) | Mar 20, 2023 | --- Data as of 2026-11-08T13:06:02Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.