{"uuid": "b301a020-ff82-450f-990a-b602c5acf77a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2024-50005", "type": "seen", "source": "https://t.me/cvedetector/8529", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-50005 - Linux Kernel RCU Dereference Vuln in mac802154 Scan Worker\", \n  \"Content\": \"CVE ID : CVE-2024-50005 \nPublished : Oct. 21, 2024, 7:15 p.m. | 34\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nmac802154: Fix potential RCU dereference issue in mac802154_scan_worker  \n  \nIn the `mac802154_scan_worker` function, the `scan_req->type` field was  \naccessed after the RCU read-side critical section was unlocked. According  \nto RCU usage rules, this is illegal and can lead to unpredictable  \nbehavior, such as accessing memory that has been updated or causing  \nuse-after-free issues.  \n  \nThis possible bug was identified using a static analysis tool developed  \nby myself, specifically designed to detect RCU-related issues.  \n  \nTo address this, the `scan_req->type` value is now stored in a local  \nvariable `scan_req_type` while still within the RCU read-side critical  \nsection. The `scan_req_type` is then used after the RCU lock is released,  \nensuring that the type value is safely accessed without violating RCU  \nrules. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"21 Oct 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-10-21T21:52:30.000000Z"}