CVE-2023-54033
published 2025-12-24CVE-2023-54033: In the Linux kernel, the following vulnerability has been resolved: bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps The LRU and LRU_PERCPU maps…
PriorityP418low5.5
EPSS
0.17%
6.3th percentile
In the Linux kernel, the following vulnerability has been resolved:
bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps
The LRU and LRU_PERCPU maps allocate a new element on update before locking the
target hash table bucket. Right after that the maps try to lock the bucket.
If this fails, then maps return -EBUSY to the caller without releasing the
allocated element. This makes the element untracked: it doesn't belong to
either of free lists, and it doesn't belong to the hash table, so can't be
re-used; this eventually leads to the permanent -ENOMEM on LRU map updates,
which is unexpected. Fix this by returning the element to the local free list
if bucket locking fails.
Affected
12 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.37-1 (bookworm) | linux 6.1.37-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 20b6cc34ea74b6a84599c1f8a70f3315b56a1883 < 79ea1a12fb9a8275b6e19d4ca625dd872dedcbb9 | 79ea1a12fb9a8275b6e19d4ca625dd872dedcbb9 |
| linux | linux | >= 20b6cc34ea74b6a84599c1f8a70f3315b56a1883 < 1a9e80f757bbb1562d82e350afce2bb2f712cc3d | 1a9e80f757bbb1562d82e350afce2bb2f712cc3d |
| linux | linux | >= 20b6cc34ea74b6a84599c1f8a70f3315b56a1883 < 965e9cccbe6b9c7b379908cebcb5e3a47f20dd5e | 965e9cccbe6b9c7b379908cebcb5e3a47f20dd5e |
| linux | linux | >= 20b6cc34ea74b6a84599c1f8a70f3315b56a1883 < b34ffb0c6d23583830f9327864b9c1f486003305 | b34ffb0c6d23583830f9327864b9c1f486003305 |
| linux | linux_kernel | >= 0 < 6.1.37-1 | 6.1.37-1 |
| linux | linux_kernel | >= 0 < 6.3.7-1 | 6.3.7-1 |
| linux | linux_kernel | >= 0 < 6.3.7-1 | 6.3.7-1 |
| linux | linux_kernel | >= 5.11.0 < 5.15.115 | 5.15.115 |
| linux | linux_kernel | >= 5.16.0 < 6.1.31 | 6.1.31 |
| linux | linux_kernel | >= 6.2.0 < 6.3.5 | 6.3.5 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps
osv·2025-12-24
CVE-2023-54033 bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps
bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps
In the Linux kernel, the following vulnerability has been resolved:
bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps
The LRU and LRU_PERCPU maps allocate a new element on update before locking the
target hash table bucket. Right after that the maps try to lock the bucket.
If this fails, then maps return -EBUSY to the caller without releasing the
allocated element. This makes the element untracked: it doesn't belong to
either of free lists, and it doesn't belong to the hash table, so can't be
re-used; this eventually leads to the permanent -ENOMEM on LRU map updates,
which is unexpected. Fix this by returning the element to the local free list
if bucket locking fails.
OSV
CVE-2023-54033: In the Linux kernel, the following vulnerability has been resolved: bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps The LRU and LRU_PERCPU
osv·2025-12-24
CVE-2023-54033 CVE-2023-54033: In the Linux kernel, the following vulnerability has been resolved: bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps The LRU and LRU_PERCPU
In the Linux kernel, the following vulnerability has been resolved: bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps The LRU and LRU_PERCPU maps allocate a new element on update before locking the target hash table bucket. Right after that the maps try to lock the bucket. If this fails, then maps return -EBUSY to the caller without releasing the allocated element. This makes the element untracked: it doesn't belong to either of free lists, and it doesn't belong to the hash table, so can't be re-used; this eventually leads to the permanent -ENOMEM on LRU map updates, which is unexpected. Fix this by returning the element to the local free list if bucket locking fails.
GHSA
GHSA-hcpj-xwwg-jgh9: In the Linux kernel, the following vulnerability has been resolved:
bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps
The LRU and LRU_PERCP
ghsa_unreviewed·2025-12-24
CVE-2023-54033 GHSA-hcpj-xwwg-jgh9: In the Linux kernel, the following vulnerability has been resolved:
bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps
The LRU and LRU_PERCP
In the Linux kernel, the following vulnerability has been resolved:
bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps
The LRU and LRU_PERCPU maps allocate a new element on update before locking the
target hash table bucket. Right after that the maps try to lock the bucket.
If this fails, then maps return -EBUSY to the caller without releasing the
allocated element. This makes the element untracked: it doesn't belong to
either of free lists, and it doesn't belong to the hash table, so can't be
re-used; this eventually leads to the permanent -ENOMEM on LRU map updates,
which is unexpected. Fix this by returning the element to the local free list
if bucket locking fails.
Red Hat
kernel: kernel: Denial of Service via memory leak in LRU hash maps
vendor_redhat·2025-12-24·CVSS 5.5
CVE-2023-54033 [LOW] CWE-772 kernel: kernel: Denial of Service via memory leak in LRU hash maps
kernel: kernel: Denial of Service via memory leak in LRU hash maps
In the Linux kernel, the following vulnerability has been resolved:
bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps
The LRU and LRU_PERCPU maps allocate a new element on update before locking the
target hash table bucket. Right after that the maps try to lock the bucket.
If this fails, then maps return -EBUSY to the caller without releasing the
allocated element. This makes the element untracked: it doesn't belong to
either of free lists, and it doesn't belong to the hash table, so can't be
re-used; this eventually leads to the permanent -ENOMEM on LRU map updates,
which is unexpected. Fix this by returning the element to the local free list
if bucket locking fails.
A flaw was found in the Linux kernel. A local
Debian
CVE-2023-54033: linux - In the Linux kernel, the following vulnerability has been resolved: bpf: fix a ...
vendor_debian·2023
CVE-2023-54033 CVE-2023-54033: linux - In the Linux kernel, the following vulnerability has been resolved: bpf: fix a ...
In the Linux kernel, the following vulnerability has been resolved: bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps The LRU and LRU_PERCPU maps allocate a new element on update before locking the target hash table bucket. Right after that the maps try to lock the bucket. If this fails, then maps return -EBUSY to the caller without releasing the allocated element. This makes the element untracked: it doesn't belong to either of free lists, and it doesn't belong to the hash table, so can't be re-used; this eventually leads to the permanent -ENOMEM on LRU map updates, which is unexpected. Fix this by returning the element to the local free list if bucket locking fails.
Scope: local
bookworm: resolved (fixed in 6.1.37-1)
bullseye: resolved
forky: resolved (fixed in 6.3.7-1)
sid: res
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2023-54033 kernel: kernel: Denial of Service via memory leak in LRU hash maps
bugzilla·2025-12-24
CVE-2023-54033 [LOW] CVE-2023-54033 kernel: kernel: Denial of Service via memory leak in LRU hash maps
CVE-2023-54033 kernel: kernel: Denial of Service via memory leak in LRU hash maps
In the Linux kernel, the following vulnerability has been resolved:
bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps
The LRU and LRU_PERCPU maps allocate a new element on update before locking the
target hash table bucket. Right after that the maps try to lock the bucket.
If this fails, then maps return -EBUSY to the caller without releasing the
allocated element. This makes the element untracked: it doesn't belong to
either of free lists, and it doesn't belong to the hash table, so can't be
re-used; this eventually leads to the permanent -ENOMEM on LRU map updates,
which is unexpected. Fix this by returning the element to the local free list
if bucket locking fails.
Discussion:
Upstream adviso
Wiz
CVE-2023-54033 Impact, Exploitability, and Mitigation Steps | Wiz
blogs_wiz
CVE-2023-54033 CVE-2023-54033 Impact, Exploitability, and Mitigation Steps | Wiz
## CVE-2023-54033 :
Linux Kernel vulnerability analysis and mitigation
In the Linux kernel, the following vulnerability has been resolved:
bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps
The LRU and LRU_PERCPU maps allocate a new element on update before locking the
target hash table bucket. Right after that the maps try to lock the bucket.
If this fails, then maps return -EBUSY to the caller without releasing the
allocated element. This makes the element untracked: it doesn't belong to
either of free lists, and it doesn't belong to the hash table, so can't be
re-used; this eventually leads to the permanent -ENOMEM on LRU map updates,
which is unexpected. Fix this by returning the element to the local free list
if bucket locking fails.
Source : NVD
Published December 24, 2
2025-12-24
Published