https://vulnerability.circl.lu/sightings/feed 2026-06-05T22:55:29.301331+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/bf8266be-709a-49e5-a1dd-eeb9c6843eda/export 2026-06-05T22:55:29.741117+00:00 Automation user https://vulnerability.circl.lu/user/automation {"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"} 2025-05-02T20:07:56+00:00