https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Tue, 05 May 2026 23:13:15 +0000 https://vulnerability.circl.lu/sighting/ef13fd60-55bd-4446-bdf9-cbcc608632e6/export {"uuid": "ef13fd60-55bd-4446-bdf9-cbcc608632e6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-22128", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/19689", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-22128\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath12k: Clear affinity hint before calling ath12k_pci_free_irq() in error path\n\nIf a shared IRQ is used by the driver due to platform limitation, then the\nIRQ affinity hint is set right after the allocation of IRQ vectors in\nath12k_pci_msi_alloc(). This does no harm unless one of the functions\nrequesting the IRQ fails and attempt to free the IRQ.\n\nThis may end up with a warning from the IRQ core that is expecting the\naffinity hint to be cleared before freeing the IRQ:\n\nkernel/irq/manage.c:\n\n /* make sure affinity_hint is cleaned up */\n if (WARN_ON_ONCE(desc->affinity_hint))\n desc->affinity_hint = NULL;\n\nSo to fix this issue, clear the IRQ affinity hint before calling\nath12k_pci_free_irq() in the error path. The affinity will be cleared once\nagain further down the error path due to code organization, but that does\nno harm.\n\ud83d\udccf Published: 2025-04-16T14:13:10.692Z\n\ud83d\udccf Modified: 2025-06-27T10:21:16.498Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/a69a594794fcad96d4cfce12aab6c5014a12b4c8\n2. https://git.kernel.org/stable/c/35b33ba76765ce9e72949d957f3cf1feafd2955c\n3. https://git.kernel.org/stable/c/b43b1e2c52db77c872bd60d30cdcc72c47df70c7", "creation_timestamp": "2025-06-27T10:49:55.000000Z"} {"uuid": "ef13fd60-55bd-4446-bdf9-cbcc608632e6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-22128", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/19689", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-22128\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath12k: Clear affinity hint before calling ath12k_pci_free_irq() in error path\n\nIf a shared IRQ is used by the driver due to platform limitation, then the\nIRQ affinity hint is set right after the allocation of IRQ vectors in\nath12k_pci_msi_alloc(). This does no harm unless one of the functions\nrequesting the IRQ fails and attempt to free the IRQ.\n\nThis may end up with a warning from the IRQ core that is expecting the\naffinity hint to be cleared before freeing the IRQ:\n\nkernel/irq/manage.c:\n\n /* make sure affinity_hint is cleaned up */\n if (WARN_ON_ONCE(desc->affinity_hint))\n desc->affinity_hint = NULL;\n\nSo to fix this issue, clear the IRQ affinity hint before calling\nath12k_pci_free_irq() in the error path. The affinity will be cleared once\nagain further down the error path due to code organization, but that does\nno harm.\n\ud83d\udccf Published: 2025-04-16T14:13:10.692Z\n\ud83d\udccf Modified: 2025-06-27T10:21:16.498Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/a69a594794fcad96d4cfce12aab6c5014a12b4c8\n2. https://git.kernel.org/stable/c/35b33ba76765ce9e72949d957f3cf1feafd2955c\n3. https://git.kernel.org/stable/c/b43b1e2c52db77c872bd60d30cdcc72c47df70c7", "creation_timestamp": "2025-06-27T10:49:55.000000Z"} https://vulnerability.circl.lu/sighting/ef13fd60-55bd-4446-bdf9-cbcc608632e6/export Fri, 27 Jun 2025 10:49:55 +0000