https://vulnerability.circl.lu/sightings/feed 2026-05-31T15:37:47.231409+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/d1f144f4-0ebf-432f-b37d-9f2abb4cac53/export 2026-05-31T15:37:47.627002+00:00 Automation user https://cve.circl.lu/user/automation {"uuid": "d1f144f4-0ebf-432f-b37d-9f2abb4cac53", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-43862", "type": "seen", "source": "https://t.me/cvedetector/3700", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-43862 - FSL QMC HDSL HLC Linux Kernel Deadlock Vulnerability\", \n \"Content\": \"CVE ID : CVE-2024-43862 \nPublished : Aug. 21, 2024, 12:15 a.m. | 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nnet: wan: fsl_qmc_hdlc: Convert carrier_lock spinlock to a mutex \n \nThe carrier_lock spinlock protects the carrier detection. While it is \nheld, framer_get_status() is called which in turn takes a mutex. \nThis is not correct and can lead to a deadlock. \n \nA run with PROVE_LOCKING enabled detected the issue: \n [ BUG: Invalid wait context ] \n ... \n c204ddbc (&framer->mutex){+.+.}-{3:3}, at: framer_get_status+0x40/0x78 \n other info that might help us debug this: \n context-{4:4} \n 2 locks held by ifconfig/146: \n #0: c0926a38 (rtnl_mutex){+.+.}-{3:3}, at: devinet_ioctl+0x12c/0x664 \n #1: c2006a40 (&qmc_hdlc->carrier_lock){....}-{2:2}, at: qmc_hdlc_framer_set_carrier+0x30/0x98 \n \nAvoid the spinlock usage and convert carrier_lock to a mutex. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"21 Aug 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-21T03:10:18.000000Z"} 2024-08-21T03:10:18+00:00