{"uuid": "bb04e22b-a3f6-4236-a831-6672e9799cf1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-57934", "type": "seen", "source": "https://t.me/cvedetector/15924", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-57934 - \"Linux_kernel fgraph_array READ_ONCE NULL Pointer Dereference Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2024-57934 \nPublished : Jan. 21, 2025, 12:15 p.m. | 21\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nfgraph: Add READ_ONCE() when accessing fgraph_array[]  \n  \nIn __ftrace_return_to_handler(), a loop iterates over the fgraph_array[]  \nelements, which are fgraph_ops. The loop checks if an element is a  \nfgraph_stub to prevent using a fgraph_stub afterward.  \n  \nHowever, if the compiler reloads fgraph_array[] after this check, it might  \nrace with an update to fgraph_array[] that introduces a fgraph_stub. This  \ncould result in the stub being processed, but the stub contains a null  \n\"func_hash\" field, leading to a NULL pointer dereference.  \n  \nTo ensure that the gops compared against the fgraph_stub matches the gops  \nprocessed later, add a READ_ONCE(). A similar patch appears in commit  \n63a8dfb (\"function_graph: Add READ_ONCE() when accessing fgraph_array[]\"). \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-21T13:36:52.000000Z"}