{"vulnerability": "CVE-2025-21644", "sightings": [{"uuid": "e4563682-a315-488d-bf9a-8c30de21d446", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21644", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/2322", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21644\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/xe: Fix tlb invalidation when wedging\n\nIf GuC fails to load, the driver wedges, but in the process it tries to\ndo stuff that may not be initialized yet. This moves the\nxe_gt_tlb_invalidation_init() to be done earlier: as its own doc says,\nit's a software-only initialization and should had been named with the\n_early() suffix.\n\nMove it to be called by xe_gt_init_early(), so the locks and seqno are\ninitialized, avoiding a NULL ptr deref when wedging:\n\n xe 0000:03:00.0: [drm] *ERROR* GT0: load failed: status: Reset = 0, BootROM = 0x50, UKernel = 0x00, MIA = 0x00, Auth = 0x01\n xe 0000:03:00.0: [drm] *ERROR* GT0: firmware signature verification failed\n xe 0000:03:00.0: [drm] *ERROR* CRITICAL: Xe has declared device 0000:03:00.0 as wedged.\n ...\n BUG: kernel NULL pointer dereference, address: 0000000000000000\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\n PGD 0 P4D 0\n Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI\n CPU: 9 UID: 0 PID: 3908 Comm: modprobe Tainted: G     U  W          6.13.0-rc4-xe+ #3\n Tainted: [U]=USER, [W]=WARN\n Hardware name: Intel Corporation Alder Lake Client Platform/AlderLake-S ADP-S DDR5 UDIMM CRB, BIOS ADLSFWI1.R00.3275.A00.2207010640 07/01/2022\n RIP: 0010:xe_gt_tlb_invalidation_reset+0x75/0x110 [xe]\n\nThis can be easily triggered by poking the GuC binary to force a\nsignature failure. There will still be an extra message,\n\n xe 0000:03:00.0: [drm] *ERROR* GT0: GuC mmio request 0x4100: no reply 0x4100\n\nbut that's better than a NULL ptr deref.\n\n(cherry picked from commit 5001ef3af8f2c972d6fd9c5221a8457556f8bea6)\n\ud83d\udccf Published: 2025-01-19T10:18:00.752Z\n\ud83d\udccf Modified: 2025-01-19T10:18:00.752Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/09b94ddc58c6640cbbc7775a61a5387b8be71488\n2. https://git.kernel.org/stable/c/9ab4981552930a9c45682d62424ba610edc3992d", "creation_timestamp": "2025-01-19T10:58:26.000000Z"}, {"uuid": "259146a1-985c-4c7a-b9d1-849c58e3c2c1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21644", "type": "seen", "source": "https://t.me/cvedetector/15837", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21644 - \"Intel Xeon DRM GuC Firmware Wedge Null Pointer Dereference Vulnerability\"\", \n  \"Content\": \"CVE ID : CVE-2025-21644 \nPublished : Jan. 19, 2025, 11:15 a.m. | 35\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ndrm/xe: Fix tlb invalidation when wedging  \n  \nIf GuC fails to load, the driver wedges, but in the process it tries to  \ndo stuff that may not be initialized yet. This moves the  \nxe_gt_tlb_invalidation_init() to be done earlier: as its own doc says,  \nit's a software-only initialization and should had been named with the  \n_early() suffix.  \n  \nMove it to be called by xe_gt_init_early(), so the locks and seqno are  \ninitialized, avoiding a NULL ptr deref when wedging:  \n  \n xe 0000:03:00.0: [drm] *ERROR* GT0: load failed: status: Reset = 0, BootROM = 0x50, UKernel = 0x00, MIA = 0x00, Auth = 0x01  \n xe 0000:03:00.0: [drm] *ERROR* GT0: firmware signature verification failed  \n xe 0000:03:00.0: [drm] *ERROR* CRITICAL: Xe has declared device 0000:03:00.0 as wedged.  \n ...  \n BUG: kernel NULL pointer dereference, address: 0000000000000000  \n #PF: supervisor read access in kernel mode  \n #PF: error_code(0x0000) - not-present page  \n PGD 0 P4D 0  \n Oops: Oops: 0000 [#1] PREEMPT SMP NOPTI  \n CPU: 9 UID: 0 PID: 3908 Comm: modprobe Tainted: G     U  W          6.13.0-rc4-xe+ #3  \n Tainted: [U]=USER, [W]=WARN  \n Hardware name: Intel Corporation Alder Lake Client Platform/AlderLake-S ADP-S DDR5 UDIMM CRB, BIOS ADLSFWI1.R00.3275.A00.2207010640 07/01/2022  \n RIP: 0010:xe_gt_tlb_invalidation_reset+0x75/0x110 [xe]  \n  \nThis can be easily triggered by poking the GuC binary to force a  \nsignature failure. There will still be an extra message,  \n  \n xe 0000:03:00.0: [drm] *ERROR* GT0: GuC mmio request 0x4100: no reply 0x4100  \n  \nbut that's better than a NULL ptr deref.  \n  \n(cherry picked from commit 5001ef3af8f2c972d6fd9c5221a8457556f8bea6) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"19 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-19T13:07:26.000000Z"}, {"uuid": "5c1a8e6d-2d95-4753-80f7-d1751a69508b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21644", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113854718111133051", "content": "", "creation_timestamp": "2025-01-19T11:12:08.124875Z"}, {"uuid": "35ed81c1-fc16-4486-936c-71178a7c18f4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21644", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lg3p4b24lo2t", "content": "", "creation_timestamp": "2025-01-19T11:15:55.589397Z"}]}