{"uuid": "e8371aa3-ebac-4d0f-b0cc-ade944753598", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56675", "type": "seen", "source": "https://t.me/cvedetector/13765", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56675 - Linux Kernel BPF UAF Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56675 \nPublished : Dec. 27, 2024, 3:15 p.m. | 32\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors  \n  \nUprobes always use bpf_prog_run_array_uprobe() under tasks-trace-RCU  \nprotection. But it is possible to attach a non-sleepable BPF program to a  \nuprobe, and non-sleepable BPF programs are freed via normal RCU (see  \n__bpf_prog_put_noref()). This leads to UAF of the bpf_prog because a normal  \nRCU grace period does not imply a tasks-trace-RCU grace period.  \n  \nFix it by explicitly waiting for a tasks-trace-RCU grace period after  \nremoving the attachment of a bpf_prog to a perf_event. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"27 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-27T16:50:53.000000Z"}