https://vulnerability.circl.lu/sightings/feed 2026-05-27T12:24:10.481239+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/2ef966d9-b4a8-43a4-a4ef-0f91d067798e/export 2026-05-27T12:24:10.955681+00:00 Automation user https://vulnerability.circl.lu/user/automation {"uuid": "2ef966d9-b4a8-43a4-a4ef-0f91d067798e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53124", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14522", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-53124\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: mpt3sas: Fix NULL pointer access in mpt3sas_transport_port_add()\n\nPort is allocated by sas_port_alloc_num() and rphy is allocated by either\nsas_end_device_alloc() or sas_expander_alloc(), all of which may return\nNULL. So we need to check the rphy to avoid possible NULL pointer access.\n\nIf sas_rphy_add() returned with failure, rphy is set to NULL. We would\naccess the rphy in the following lines which would also result NULL pointer\naccess.\n\ud83d\udccf Published: 2025-05-02T15:56:00.500Z\n\ud83d\udccf Modified: 2025-05-02T15:56:00.500Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/090305c36185c0547e4441d4c08f1cf096b32134\n2. https://git.kernel.org/stable/c/6f0c2f70d9929208d8427ec72c3ed91e2251e289\n3. https://git.kernel.org/stable/c/9937f784a608944107dcc2ba9a9c3333f8330b9e\n4. https://git.kernel.org/stable/c/b5e5bbb3fa5f8412e96c5eda7f4a4af6241d6bd3\n5. https://git.kernel.org/stable/c/a26c775ccc4cfe46f9b718b51bd24313053c7e0b\n6. https://git.kernel.org/stable/c/d3c57724f1569311e4b81e98fad0931028b9bdcd", "creation_timestamp": "2025-05-02T16:16:22.000000Z"} 2025-05-02T16:16:22+00:00 https://vulnerability.circl.lu/sighting/7e0b2610-b856-46f0-b47d-ab5ca4666832/export 2026-05-27T12:24:10.953456+00:00 Automation user https://vulnerability.circl.lu/user/automation {"uuid": "7e0b2610-b856-46f0-b47d-ab5ca4666832", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53124", "type": "seen", "source": "https://t.me/cvedetector/24369", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2023-53124 - MPT3SAS NULL Pointer Access Vulnerability\", \n \"Content\": \"CVE ID : CVE-2023-53124 \nPublished : May 2, 2025, 4:15 p.m. | 1\u00a0hour, 4\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nscsi: mpt3sas: Fix NULL pointer access in mpt3sas_transport_port_add() \n \nPort is allocated by sas_port_alloc_num() and rphy is allocated by either \nsas_end_device_alloc() or sas_expander_alloc(), all of which may return \nNULL. So we need to check the rphy to avoid possible NULL pointer access. \n \nIf sas_rphy_add() returned with failure, rphy is set to NULL. We would \naccess the rphy in the following lines which would also result NULL pointer \naccess. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"02 May 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-02T20:08:33.000000Z"} 2025-05-02T20:08:33+00:00