https://vulnerability.circl.lu/sightings/feed 2026-05-28T08:55:46.719066+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/134673a3-c27f-4ccd-864f-88a712afba0d/export 2026-05-28T08:55:47.061129+00:00 Automation user https://vulnerability.circl.lu/user/automation {"uuid": "134673a3-c27f-4ccd-864f-88a712afba0d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-50192", "type": "seen", "source": "https://t.me/cvedetector/10181", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2024-50192 - \"GICv4: Affinity Changing Vulnerability in irqchip\"\", \n \"Content\": \"CVE ID : CVE-2024-50192 \nPublished : Nov. 8, 2024, 6:15 a.m. | 41\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nirqchip/gic-v4: Don't allow a VMOVP on a dying VPE \n \nKunkun Jiang reported that there is a small window of opportunity for \nuserspace to force a change of affinity for a VPE while the VPE has already \nbeen unmapped, but the corresponding doorbell interrupt still visible in \n/proc/irq/. \n \nPlug the race by checking the value of vmapp_count, which tracks whether \nthe VPE is mapped ot not, and returning an error in this case. \n \nThis involves making vmapp_count common to both GICv4.1 and its v4.0 \nancestor. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"08 Nov 2024\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-08T07:59:57.000000Z"} 2024-11-08T07:59:57+00:00