{"uuid": "bf66a2c0-84cd-471a-80e4-5d2565068bf8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-56665", "type": "seen", "source": "https://t.me/cvedetector/13768", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56665 - Linux Kernel BPF/Perf Unauthorized Program Array Access\", \n  \"Content\": \"CVE ID : CVE-2024-56665 \nPublished : Dec. 27, 2024, 3:15 p.m. | 32\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbpf,perf: Fix invalid prog_array access in perf_event_detach_bpf_prog  \n  \nSyzbot reported [1] crash that happens for following tracing scenario:  \n  \n  - create tracepoint perf event with attr.inherit=1, attach it to the  \n    process and set bpf program to it  \n  - attached process forks -> chid creates inherited event  \n  \n    the new child event shares the parent's bpf program and tp_event  \n    (hence prog_array) which is global for tracepoint  \n  \n  - exit both process and its child -> release both events  \n  - first perf_event_detach_bpf_prog call will release tp_event->prog_array  \n    and second perf_event_detach_bpf_prog will crash, because  \n    tp_event->prog_array is NULL  \n  \nThe fix makes sure the perf_event_detach_bpf_prog checks prog_array  \nis valid before it tries to remove the bpf program from it.  \n  \n[1]  \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:59.000000Z"}