https://vulnerability.circl.lu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Wed, 27 May 2026 21:28:45 +0000 https://vulnerability.circl.lu/sighting/6ff577dd-8075-4b00-af98-017b24977764/export {"uuid": "6ff577dd-8075-4b00-af98-017b24977764", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-23129", "type": "seen", "source": "https://t.me/cvedetector/23119", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-23129 - \"Qualcomm Atheros WiFi Kernel IRQ Affinity Hint Clearing Vulnerability\"\", \n \"Content\": \"CVE ID : CVE-2025-23129 \nPublished : April 16, 2025, 3:16 p.m. | 23\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nwifi: ath11k: Clear affinity hint before calling ath11k_pcic_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 \nath11k_pci_alloc_msi(). This does no harm unless one of the functions \nrequesting the IRQ fails and attempt to free the IRQ. This results in the \nbelow warning: \n \nWARNING: CPU: 7 PID: 349 at kernel/irq/manage.c:1929 free_irq+0x278/0x29c \nCall trace: \n free_irq+0x278/0x29c \n ath11k_pcic_free_irq+0x70/0x10c [ath11k] \n ath11k_pci_probe+0x800/0x820 [ath11k_pci] \n local_pci_probe+0x40/0xbc \n \nThe warning is due to not clearing the affinity hint before freeing the \nIRQs. \n \nSo to fix this issue, clear the IRQ affinity hint before calling \nath11k_pcic_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 \nTested-on: QCA6390 hw2.0 PCI WLAN.HST.1.0.1-05266-QCAHSTSWPLZ_V2_TO_X86-1 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"16 Apr 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-16T17:43:43.000000Z"} {"uuid": "6ff577dd-8075-4b00-af98-017b24977764", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-23129", "type": "seen", "source": "https://t.me/cvedetector/23119", "content": "{\n \"Source\": \"CVE FEED\",\n \"Title\": \"CVE-2025-23129 - \"Qualcomm Atheros WiFi Kernel IRQ Affinity Hint Clearing Vulnerability\"\", \n \"Content\": \"CVE ID : CVE-2025-23129 \nPublished : April 16, 2025, 3:16 p.m. | 23\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nwifi: ath11k: Clear affinity hint before calling ath11k_pcic_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 \nath11k_pci_alloc_msi(). This does no harm unless one of the functions \nrequesting the IRQ fails and attempt to free the IRQ. This results in the \nbelow warning: \n \nWARNING: CPU: 7 PID: 349 at kernel/irq/manage.c:1929 free_irq+0x278/0x29c \nCall trace: \n free_irq+0x278/0x29c \n ath11k_pcic_free_irq+0x70/0x10c [ath11k] \n ath11k_pci_probe+0x800/0x820 [ath11k_pci] \n local_pci_probe+0x40/0xbc \n \nThe warning is due to not clearing the affinity hint before freeing the \nIRQs. \n \nSo to fix this issue, clear the IRQ affinity hint before calling \nath11k_pcic_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 \nTested-on: QCA6390 hw2.0 PCI WLAN.HST.1.0.1-05266-QCAHSTSWPLZ_V2_TO_X86-1 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n \"Detection Date\": \"16 Apr 2025\",\n \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-16T17:43:43.000000Z"} https://vulnerability.circl.lu/sighting/6ff577dd-8075-4b00-af98-017b24977764/export Wed, 16 Apr 2025 17:43:43 +0000 https://vulnerability.circl.lu/sighting/b0903072-5b76-4fd1-a4e7-c768c5350999/export {"uuid": "b0903072-5b76-4fd1-a4e7-c768c5350999", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-23129", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14802", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-23129\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath11k: Clear affinity hint before calling ath11k_pcic_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\nath11k_pci_alloc_msi(). This does no harm unless one of the functions\nrequesting the IRQ fails and attempt to free the IRQ. This results in the\nbelow warning:\n\nWARNING: CPU: 7 PID: 349 at kernel/irq/manage.c:1929 free_irq+0x278/0x29c\nCall trace:\n free_irq+0x278/0x29c\n ath11k_pcic_free_irq+0x70/0x10c [ath11k]\n ath11k_pci_probe+0x800/0x820 [ath11k_pci]\n local_pci_probe+0x40/0xbc\n\nThe warning is due to not clearing the affinity hint before freeing the\nIRQs.\n\nSo to fix this issue, clear the IRQ affinity hint before calling\nath11k_pcic_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\nTested-on: QCA6390 hw2.0 PCI WLAN.HST.1.0.1-05266-QCAHSTSWPLZ_V2_TO_X86-1\n\ud83d\udccf Published: 2025-04-16T14:13:11.663Z\n\ud83d\udccf Modified: 2025-05-04T13:07:05.587Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/3fc42cfcc6e336f25dee79b34e57c4a63cd652a5\n2. https://git.kernel.org/stable/c/68410c5bd381a81bcc92b808e7dc4e6b9ed25d11", "creation_timestamp": "2025-05-04T13:18:45.000000Z"} {"uuid": "b0903072-5b76-4fd1-a4e7-c768c5350999", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-23129", "type": "seen", "source": "https://t.me/DarkWebInformer_CVEAlerts/14802", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-23129\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath11k: Clear affinity hint before calling ath11k_pcic_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\nath11k_pci_alloc_msi(). This does no harm unless one of the functions\nrequesting the IRQ fails and attempt to free the IRQ. This results in the\nbelow warning:\n\nWARNING: CPU: 7 PID: 349 at kernel/irq/manage.c:1929 free_irq+0x278/0x29c\nCall trace:\n free_irq+0x278/0x29c\n ath11k_pcic_free_irq+0x70/0x10c [ath11k]\n ath11k_pci_probe+0x800/0x820 [ath11k_pci]\n local_pci_probe+0x40/0xbc\n\nThe warning is due to not clearing the affinity hint before freeing the\nIRQs.\n\nSo to fix this issue, clear the IRQ affinity hint before calling\nath11k_pcic_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\nTested-on: QCA6390 hw2.0 PCI WLAN.HST.1.0.1-05266-QCAHSTSWPLZ_V2_TO_X86-1\n\ud83d\udccf Published: 2025-04-16T14:13:11.663Z\n\ud83d\udccf Modified: 2025-05-04T13:07:05.587Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/3fc42cfcc6e336f25dee79b34e57c4a63cd652a5\n2. https://git.kernel.org/stable/c/68410c5bd381a81bcc92b808e7dc4e6b9ed25d11", "creation_timestamp": "2025-05-04T13:18:45.000000Z"} https://vulnerability.circl.lu/sighting/b0903072-5b76-4fd1-a4e7-c768c5350999/export Sun, 04 May 2025 13:18:45 +0000 https://vulnerability.circl.lu/sighting/30d82cd6-5469-4f81-8ec4-38d5d563504e/export {"uuid": "30d82cd6-5469-4f81-8ec4-38d5d563504e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-23129", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0397/", "content": "", "creation_timestamp": "2026-04-02T17:00:00.000000Z"} {"uuid": "30d82cd6-5469-4f81-8ec4-38d5d563504e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-23129", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0397/", "content": "", "creation_timestamp": "2026-04-02T17:00:00.000000Z"} https://vulnerability.circl.lu/sighting/30d82cd6-5469-4f81-8ec4-38d5d563504e/export Thu, 02 Apr 2026 17:00:00 +0000 https://vulnerability.circl.lu/sighting/048eef2d-c383-46ff-994f-4991af6d195f/export {"uuid": "048eef2d-c383-46ff-994f-4991af6d195f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-23129", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/ubuntu-linux-kernel-multiple-vulnerabilities_20260408", "content": "", "creation_timestamp": "2026-04-07T18:00:00.000000Z"} {"uuid": "048eef2d-c383-46ff-994f-4991af6d195f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-23129", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/ubuntu-linux-kernel-multiple-vulnerabilities_20260408", "content": "", "creation_timestamp": "2026-04-07T18:00:00.000000Z"} https://vulnerability.circl.lu/sighting/048eef2d-c383-46ff-994f-4991af6d195f/export Tue, 07 Apr 2026 18:00:00 +0000 https://vulnerability.circl.lu/sighting/bc26dffb-9c0d-4780-889b-64c8c28805e4/export {"uuid": "bc26dffb-9c0d-4780-889b-64c8c28805e4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-23129", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/ubuntu-linux-kernel-multiple-vulnerabilities_20260511", "content": "", "creation_timestamp": "2026-05-10T18:00:00.000000Z"} {"uuid": "bc26dffb-9c0d-4780-889b-64c8c28805e4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "86ecb4e1-bb32-44d5-9f39-8a4673af8385", "vulnerability": "CVE-2025-23129", "type": "seen", "source": "https://www.hkcert.org/security-bulletin/ubuntu-linux-kernel-multiple-vulnerabilities_20260511", "content": "", "creation_timestamp": "2026-05-10T18:00:00.000000Z"} https://vulnerability.circl.lu/sighting/bc26dffb-9c0d-4780-889b-64c8c28805e4/export Sun, 10 May 2026 18:00:00 +0000