{"vulnerability": "CVE-2023-5312", "sightings": [{"uuid": "0437d198-0226-498b-b0ff-22344bd81ee4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53129", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14517", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-53129\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\next4: Fix deadlock during directory rename\n\nAs lockdep properly warns, we should not be locking i_rwsem while having\ntransactions started as the proper lock ordering used by all directory\nhandling operations is i_rwsem -> transaction start. Fix the lock\nordering by moving the locking of the directory earlier in\next4_rename().\n\ud83d\udccf Published: 2025-05-02T15:56:04.366Z\n\ud83d\udccf Modified: 2025-05-02T15:56:04.366Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/6b06c4ae64e3557a19b3bb0b6dbf641bc41fc218\n2. https://git.kernel.org/stable/c/b113f90204479f55a17295bedf0cc966a60c7a56\n3. https://git.kernel.org/stable/c/a2bc806e95bde8de3a0d675051d9ae78dcf6c691\n4. https://git.kernel.org/stable/c/2ef7f829214fa8f428d953b49557b89b2b02db66\n5. https://git.kernel.org/stable/c/352c728653a1179ce7bb37a4c8aa8404d83914a2\n6. https://git.kernel.org/stable/c/3c92792da8506a295afb6d032b4476e46f979725", "creation_timestamp": "2025-05-02T16:16:14.000000Z"}, {"uuid": "b2d7a470-94f6-4076-b3ad-d0a052bcd478", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53125", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14521", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-53125\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: smsc75xx: Limit packet length to skb->len\n\nPacket length retrieved from skb data may be larger than\nthe actual socket buffer length (up to 9026 bytes). In such\ncase the cloned skb passed up the network stack will leak\nkernel memory contents.\n\ud83d\udccf Published: 2025-05-02T15:56:01.140Z\n\ud83d\udccf Modified: 2025-05-02T15:56:01.140Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/4a4de0a68b18485c68ab4f0cfa665b1633c6d277\n2. https://git.kernel.org/stable/c/53966d572d056d6b234cfe76a5f9d60049d3c178\n3. https://git.kernel.org/stable/c/9fabdd79051a9fe51388df099aff6e4b660fedd2\n4. https://git.kernel.org/stable/c/e294f0aa47e4844f3d3c8766c02accd5a76a7d4e\n5. https://git.kernel.org/stable/c/105db6574281e1e03fcbf87983f4fee111682306\n6. https://git.kernel.org/stable/c/c7bdc137ca163b90917c1eeba4f1937684bd4f8b\n7. https://git.kernel.org/stable/c/8ee5df9c039e37b9d8eb5e3de08bfb7f53d31cb6\n8. https://git.kernel.org/stable/c/d8b228318935044dafe3a5bc07ee71a1f1424b8d", "creation_timestamp": "2025-05-02T16:16:21.000000Z"}, {"uuid": "987ee017-5373-4556-9649-a1d11effff4c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53126", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14520", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-53126\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: mpi3mr: Fix sas_hba.phy memory leak in mpi3mr_remove()\n\nFree mrioc->sas_hba.phy at .remove.\n\ud83d\udccf Published: 2025-05-02T15:56:02.077Z\n\ud83d\udccf Modified: 2025-05-02T15:56:02.077Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/480aae2f30637b5140e9c7a9b10298e538df2b5e\n2. https://git.kernel.org/stable/c/c60a7c7508645a9f36e4a18a5f548fb79378acd1\n3. https://git.kernel.org/stable/c/d4caa1a4255cc44be56bcab3db2c97c632e6cc10", "creation_timestamp": "2025-05-02T16:16:17.000000Z"}, {"uuid": "2a6567a5-5ea3-47ce-939e-668fcded6d4a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53127", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14519", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-53127\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: mpi3mr: Fix expander node leak in mpi3mr_remove()\n\nAdd a missing resource clean up in .remove.\n\ud83d\udccf Published: 2025-05-02T15:56:03.058Z\n\ud83d\udccf Modified: 2025-05-02T15:56:03.058Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/0023972a7593720f8878aed06c03ac9e541078be\n2. https://git.kernel.org/stable/c/cf9777be5683c5e55680c089df02ee27d2226aa8\n3. https://git.kernel.org/stable/c/ce756daa36e1ba271bb3334267295e447aa57a5c", "creation_timestamp": "2025-05-02T16:16:16.000000Z"}, {"uuid": "98f481f6-9f46-4ac9-816f-7970604d3ec5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53128", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14518", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-53128\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: mpi3mr: Fix throttle_groups memory leak\n\nAdd a missing kfree().\n\ud83d\udccf Published: 2025-05-02T15:56:03.674Z\n\ud83d\udccf Modified: 2025-05-02T15:56:03.674Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/574cc10edaa7dba833764efed8c57ee0e6bf7574\n2. https://git.kernel.org/stable/c/85349a227eb4a56520adc190c666075f80d4ae70\n3. https://git.kernel.org/stable/c/f305a7b6ca21a665e8d0cf70b5936991a298c93c", "creation_timestamp": "2025-05-02T16:16:15.000000Z"}, {"uuid": "e1934e25-c0e6-487f-9bf7-070c862349e8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53120", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/14732", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-53120\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: mpi3mr: Fix config page DMA memory leak\n\nA fix for:\n\nDMA-API: pci 0000:83:00.0: device driver has pending DMA allocations while released from device [count=1]\n\ud83d\udccf Published: 2025-05-02T15:55:57.483Z\n\ud83d\udccf Modified: 2025-05-04T07:50:16.091Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/dca06ccf13de14e144d34f158f73ae0032f80e63\n2. https://git.kernel.org/stable/c/5fc4d698ed4b6507be2eb36d040a678adcb89da4\n3. https://git.kernel.org/stable/c/7d2b02172b6a2ae6aecd7ef6480b9c4bf3dc59f4", "creation_timestamp": "2025-05-04T08:17:54.000000Z"}, {"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"}, {"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"}, {"uuid": "4747be18-ca07-4a6d-b166-cec19ef9768e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53121", "type": "seen", "source": "https://t.me/cvedetector/24365", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-53121 - Linux Kernel TCP Information Disclosure Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2023-53121 \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  \ntcp: tcp_make_synack() can be called from process context  \n  \ntcp_rtx_synack() now could be called in process context as explained in  \n0a375c822497 (\"tcp: tcp_rtx_synack() can be called from process  \ncontext\").  \n  \ntcp_rtx_synack() might call tcp_make_synack(), which will touch per-CPU  \nvariables with preemption enabled. This causes the following BUG:  \n  \n    BUG: using __this_cpu_add() in preemptible [00000000] code: ThriftIO1/5464  \n    caller is tcp_make_synack+0x841/0xac0  \n    Call Trace:  \n       \n     dump_stack_lvl+0x10d/0x1a0  \n     check_preemption_disabled+0x104/0x110  \n     tcp_make_synack+0x841/0xac0  \n     tcp_v6_send_synack+0x5c/0x450  \n     tcp_rtx_synack+0xeb/0x1f0  \n     inet_rtx_syn_ack+0x34/0x60  \n     tcp_check_req+0x3af/0x9e0  \n     tcp_rcv_state_process+0x59b/0x2030  \n     tcp_v6_do_rcv+0x5f5/0x700  \n     release_sock+0x3a/0xf0  \n     tcp_sendmsg+0x33/0x40  \n     ____sys_sendmsg+0x2f2/0x490  \n     __sys_sendmsg+0x184/0x230  \n     do_syscall_64+0x3d/0x90  \n  \nAvoid calling __TCP_INC_STATS() with will touch per-cpu variables. Use  \nTCP_INC_STATS() which is safe to be called from context switch. \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:07:54.000000Z"}, {"uuid": "c2eb780f-11f2-4d7f-8330-016fddba9538", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53123", "type": "seen", "source": "https://t.me/cvedetector/24366", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-53123 - Linux Kernel PCI s390 Use-After-Free Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2023-53123 \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  \nPCI: s390: Fix use-after-free of PCI resources with per-function hotplug  \n  \nOn s390 PCI functions may be hotplugged individually even when they  \nbelong to a multi-function device. In particular on an SR-IOV device VFs  \nmay be removed and later re-added.  \n  \nIn commit a50297cf8235 (\"s390/pci: separate zbus creation from  \nscanning\") it was missed however that struct pci_bus and struct  \nzpci_bus's resource list retained a reference to the PCI functions MMIO  \nresources even though those resources are released and freed on  \nhot-unplug. These stale resources may subsequently be claimed when the  \nPCI function re-appears resulting in use-after-free.  \n  \nOne idea of fixing this use-after-free in s390 specific code that was  \ninvestigated was to simply keep resources around from the moment a PCI  \nfunction first appeared until the whole virtual PCI bus created for  \na multi-function device disappears. The problem with this however is  \nthat due to the requirement of artificial MMIO addreesses (address  \ncookies) extra logic is then needed to keep the address cookies  \ncompatible on re-plug. At the same time the MMIO resources semantically  \nbelong to the PCI function so tying their lifecycle to the function  \nseems more logical.  \n  \nInstead a simpler approach is to remove the resources of an individually  \nhot-unplugged PCI function from the PCI bus's resource list while  \nkeeping the resources of other PCI functions on the PCI bus untouched.  \n  \nThis is done by introducing pci_bus_remove_resource() to remove an  \nindividual resource. Similarly the resource also needs to be removed  \nfrom the struct zpci_bus's resource list. It turns out however, that  \nthere is really no need to add the MMIO resources to the struct  \nzpci_bus's resource list at all and instead we can simply use the  \nzpci_bar_struct's resource pointer directly. \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:07:55.000000Z"}, {"uuid": "bf8266be-709a-49e5-a1dd-eeb9c6843eda", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53122", "type": "seen", "source": "https://t.me/cvedetector/24367", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-53122 - RISC-V SiFive Errata Patching Mutex Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2023-53122 \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  \nRISC-V: fix taking the text_mutex twice during sifive errata patching  \n  \nChris pointed out that some bonehead, *cough* me *cough*, added two  \nmutex_locks() to the SiFive errata patching. The second was meant to  \nhave been a mutex_unlock().  \n  \nThis results in errors such as  \n  \nUnable to handle kernel NULL pointer dereference at virtual address 0000000000000030  \nOops [#1]  \nModules linked in:  \nCPU: 0 PID: 0 Comm: swapper Not tainted  \n6.2.0-rc1-starlight-00079-g9493e6f3ce02 #229  \nHardware name: BeagleV Starlight Beta (DT)  \nepc : __schedule+0x42/0x500  \n ra : schedule+0x46/0xce  \nepc : ffffffff8065957c ra : ffffffff80659a80 sp : ffffffff81203c80  \n gp : ffffffff812d50a0 tp : ffffffff8120db40 t0 : ffffffff81203d68  \n t1 : 0000000000000001 t2 : 4c45203a76637369 s0 : ffffffff81203cf0  \n s1 : ffffffff8120db40 a0 : 0000000000000000 a1 : ffffffff81213958  \n a2 : ffffffff81213958 a3 : 0000000000000000 a4 : 0000000000000000  \n a5 : ffffffff80a1bd00 a6 : 0000000000000000 a7 : 0000000052464e43  \n s2 : ffffffff8120db41 s3 : ffffffff80a1ad00 s4 : 0000000000000000  \n s5 : 0000000000000002 s6 : ffffffff81213938 s7 : 0000000000000000  \n s8 : 0000000000000000 s9 : 0000000000000001 s10: ffffffff812d7204  \n s11: ffffffff80d3c920 t3 : 0000000000000001 t4 : ffffffff812e6dd7  \n t5 : ffffffff812e6dd8 t6 : ffffffff81203bb8  \nstatus: 0000000200000100 badaddr: 0000000000000030 cause: 000000000000000d  \n[] schedule+0x46/0xce  \n[] schedule_preempt_disabled+0x16/0x28  \n[] __mutex_lock.constprop.0+0x3fe/0x652  \n[] __mutex_lock_slowpath+0xe/0x16  \n[] mutex_lock+0x42/0x4c  \n[] sifive_errata_patch_func+0xf6/0x18c  \n[] _apply_alternatives+0x74/0x76  \n[] apply_boot_alternatives+0x3c/0xfa  \n[] setup_arch+0x60c/0x640  \n[] start_kernel+0x8e/0x99c  \n---[ end trace 0000000000000000 ]---  \n  \n[Palmer: pick up Geert's bug report from the thread] \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:07:56.000000Z"}, {"uuid": "1d1bacf7-1686-4c16-938c-13805a93c618", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-53125", "type": "seen", "source": "https://t.me/cvedetector/24368", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-53125 - \"Linux Kernel SMSc75xx Network Stack Buffer Overflow\"\", \n  \"Content\": \"CVE ID : CVE-2023-53125 \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  \nnet: usb: smsc75xx: Limit packet length to skb->len  \n  \nPacket length retrieved from skb data may be larger than  \nthe actual socket buffer length (up to 9026 bytes). In such  \ncase the cloned skb passed up the network stack will leak  \nkernel memory contents. \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:32.000000Z"}]}