bpf: fix a memory leak in the LRU and LRU_PERCPU hash maps
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1a9e80f757bbb1562d82e350afce2bb2f712cc3d, Kernel 79ea1a12fb9a8275b6e19d4ca625dd872dedcbb9, Kernel 965e9cccbe6b9c7b379908cebcb5e3a47f20dd5e and 1 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.11, >=20b6cc34ea74b6a84599c1f8a70f3315b56a1883 <1a9e80f757bbb1562d82e350afce2bb2f712cc3d, >=20b6cc34ea74b6a84599c1f8a70f3315b56a1883 <79ea1a12fb9a8275b6e19d4ca625dd872dedcbb9, >=20b6cc34ea74b6a84599c1f8a70f3315b56a1883 <965e9cccbe6b9c7b379908cebcb5e3a47f20dd5e, >=20b6cc34ea74b6a84599c1f8a70f3315b56a1883 <b34ffb0c6d23583830f9327864b9c1f486003305 | 1a9e80f757bbb1562d82e350afce2bb2f712cc3d, 79ea1a12fb9a8275b6e19d4ca625dd872dedcbb9, 965e9cccbe6b9c7b379908cebcb5e3a47f20dd5e, b34ffb0c6d23583830f9327864b9c1f486003305 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket