https://vulnerability.circl.lu/sightings/feed 2026-05-27T11:45:47.145786+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/374d7e27-4256-4111-9384-5482244ca4b6/export 2026-05-27T11:45:47.492829+00:00 Automation user https://vulnerability.circl.lu/user/automation {"uuid": "374d7e27-4256-4111-9384-5482244ca4b6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-49999", "type": "seen", "source": "https://t.me/cvedetector/8520", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-49999 - IBM AFS NULL Pointer Dereference\", \n \"Content\": \"CVE ID : CVE-2024-49999 \nPublished : Oct. 21, 2024, 6:15 p.m. | 44\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nafs: Fix the setting of the server responding flag \n \nIn afs_wait_for_operation(), we set transcribe the call responded flag to \nthe server record that we used after doing the fileserver iteration loop - \nbut it's possible to exit the loop having had a response from the server \nthat we've discarded (e.g. it returned an abort or we started receiving \ndata, but the call didn't complete). \n \nThis means that op->server might be NULL, but we don't check that before \nattempting to set the server flag. \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:02:10.000000Z"} 2024-10-21T21:02:10+00:00