
Cloud Vulnerability DB
A community-led vulnerabilities database
In the Linux kernel, a vulnerability has been identified and resolved regarding the bpf_refcount_acquire functionality for non-owning references. The issue was discovered in the original bpf_refcount series, where an incorrect assumption was made that a BPF program calling bpf_refcount_acquire on a node could always guarantee the node's existence (NVD).
The vulnerability stems from an incorrect assumption in the bpf_refcount series, specifically when dealing with non-owning references. The issue manifests when bpf_refcount_acquire is called in a critical section where the lock being held is associated with an rbtree that isn't necessarily the lock associated with the tree containing the node. After bpf_rbtree_add fails and calls bpf_obj_drop, the program loses ownership of the node's lifetime, allowing the node's refcount to be decremented to 0 at any time after the failing rbtree_add (NVD).
If exploited, this vulnerability can lead to use-after-free conditions when the refcount is decremented to 0 before the refcount_acquire operation. This results in the system attempting to increment a 0 refcount, which triggers kernel warnings and potential system instability (NVD).
The issue has been addressed by modifying bpf_refcount_acquire_impl to use refcount_inc_not_zero instead of refcount_inc and marking bpf_refcount_acquire as KF_RET_NULL. For owning references, additional verifier bookkeeping has been implemented to track input ownership status for bpf_refcount_acquire calls (NVD).
Source: This report was generated using AI
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."