{"vulnerability": "CVE-2025-21684", "sightings": [{"uuid": "06a81dff-14fe-46a0-b799-2b3121226406", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21684", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/4891", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-21684\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ngpio: xilinx: Convert gpio_lock to raw spinlock\n\nirq_chip functions may be called in raw spinlock context. Therefore, we\nmust also use a raw spinlock for our own internal locking.\n\nThis fixes the following lockdep splat:\n\n[    5.349336] =============================\n[    5.353349] [ BUG: Invalid wait context ]\n[    5.357361] 6.13.0-rc5+ #69 Tainted: G        W\n[    5.363031] -----------------------------\n[    5.367045] kworker/u17:1/44 is trying to lock:\n[    5.371587] ffffff88018b02c0 (&amp;chip-&gt;gpio_lock){....}-{3:3}, at: xgpio_irq_unmask (drivers/gpio/gpio-xilinx.c:433 (discriminator 8))\n[    5.380079] other info that might help us debug this:\n[    5.385138] context-{5:5}\n[    5.387762] 5 locks held by kworker/u17:1/44:\n[    5.392123] #0: ffffff8800014958 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work (kernel/workqueue.c:3204)\n[    5.402260] #1: ffffffc082fcbdd8 (deferred_probe_work){+.+.}-{0:0}, at: process_one_work (kernel/workqueue.c:3205)\n[    5.411528] #2: ffffff880172c900 (&amp;dev-&gt;mutex){....}-{4:4}, at: __device_attach (drivers/base/dd.c:1006)\n[    5.419929] #3: ffffff88039c8268 (request_class#2){+.+.}-{4:4}, at: __setup_irq (kernel/irq/internals.h:156 kernel/irq/manage.c:1596)\n[    5.428331] #4: ffffff88039c80c8 (lock_class#2){....}-{2:2}, at: __setup_irq (kernel/irq/manage.c:1614)\n[    5.436472] stack backtrace:\n[    5.439359] CPU: 2 UID: 0 PID: 44 Comm: kworker/u17:1 Tainted: G        W          6.13.0-rc5+ #69\n[    5.448690] Tainted: [W]=WARN\n[    5.451656] Hardware name: xlnx,zynqmp (DT)\n[    5.455845] Workqueue: events_unbound deferred_probe_work_func\n[    5.461699] Call trace:\n[    5.464147] show_stack+0x18/0x24 C\n[    5.467821] dump_stack_lvl (lib/dump_stack.c:123)\n[    5.471501] dump_stack (lib/dump_stack.c:130)\n[    5.474824] __lock_acquire (kernel/locking/lockdep.c:4828 kernel/locking/lockdep.c:4898 kernel/locking/lockdep.c:5176)\n[    5.478758] lock_acquire (arch/arm64/include/asm/percpu.h:40 kernel/locking/lockdep.c:467 kernel/locking/lockdep.c:5851 kernel/locking/lockdep.c:5814)\n[    5.482429] _raw_spin_lock_irqsave (include/linux/spinlock_api_smp.h:111 kernel/locking/spinlock.c:162)\n[    5.486797] xgpio_irq_unmask (drivers/gpio/gpio-xilinx.c:433 (discriminator 8))\n[    5.490737] irq_enable (kernel/irq/internals.h:236 kernel/irq/chip.c:170 kernel/irq/chip.c:439 kernel/irq/chip.c:432 kernel/irq/chip.c:345)\n[    5.494060] __irq_startup (kernel/irq/internals.h:241 kernel/irq/chip.c:180 kernel/irq/chip.c:250)\n[    5.497645] irq_startup (kernel/irq/chip.c:270)\n[    5.501143] __setup_irq (kernel/irq/manage.c:1807)\n[    5.504728] request_threaded_irq (kernel/irq/manage.c:2208)\n\ud83d\udccf Published: 2025-02-09T11:37:24.610Z\n\ud83d\udccf Modified: 2025-02-21T13:45:17.838Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/f0ed2d0abc021f56fa27dc6d0770535c1851a43b\n2. https://git.kernel.org/stable/c/b0111650ee596219bb5defa0ce1a1308e6e77ccf\n3. https://git.kernel.org/stable/c/9c035105c5537d2ecad6b9415e9417a1ffbd0a62\n4. https://git.kernel.org/stable/c/9860370c2172704b6b4f0075a0c2a29fd84af96a", "creation_timestamp": "2025-02-21T14:18:30.000000Z"}, {"uuid": "29252a41-9584-4d5d-bb56-b400a995a7f5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21684", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113973737079192703", "content": "", "creation_timestamp": "2025-02-09T11:40:13.344458Z"}, {"uuid": "31a38605-2dbe-4396-8465-bac84458db14", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21684", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lhqmawn3wx27", "content": "", "creation_timestamp": "2025-02-09T12:15:57.112240Z"}, {"uuid": "33d06589-9000-4075-867a-bf86e0791bea", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21684", "type": "seen", "source": "https://infosec.exchange/users/vuldb/statuses/113974127645069539", "content": "", "creation_timestamp": "2025-02-09T13:19:32.760782Z"}, {"uuid": "3ba7163b-1c05-47e1-9618-611dac34971f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21684", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lhqyhw4okf2d", "content": "", "creation_timestamp": "2025-02-09T15:54:37.657716Z"}, {"uuid": "eda32767-1ed9-40ac-923c-d0ec1a158f1e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-21684", "type": "seen", "source": "https://t.me/cvedetector/17547", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-21684 - Xilinx GPIO Lock Violation Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-21684 \nPublished : Feb. 9, 2025, 12:15 p.m. | 22\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ngpio: xilinx: Convert gpio_lock to raw spinlock  \n  \nirq_chip functions may be called in raw spinlock context. Therefore, we  \nmust also use a raw spinlock for our own internal locking.  \n  \nThis fixes the following lockdep splat:  \n  \n[    5.349336] =============================  \n[    5.353349] [ BUG: Invalid wait context ]  \n[    5.357361] 6.13.0-rc5+ #69 Tainted: G        W  \n[    5.363031] -----------------------------  \n[    5.367045] kworker/u17:1/44 is trying to lock:  \n[    5.371587] ffffff88018b02c0 (&amp;chip-&gt;gpio_lock){....}-{3:3}, at: xgpio_irq_unmask (drivers/gpio/gpio-xilinx.c:433 (discriminator 8))  \n[    5.380079] other info that might help us debug this:  \n[    5.385138] context-{5:5}  \n[    5.387762] 5 locks held by kworker/u17:1/44:  \n[    5.392123] #0: ffffff8800014958 ((wq_completion)events_unbound){+.+.}-{0:0}, at: process_one_work (kernel/workqueue.c:3204)  \n[    5.402260] #1: ffffffc082fcbdd8 (deferred_probe_work){+.+.}-{0:0}, at: process_one_work (kernel/workqueue.c:3205)  \n[    5.411528] #2: ffffff880172c900 (&amp;dev-&gt;mutex){....}-{4:4}, at: __device_attach (drivers/base/dd.c:1006)  \n[    5.419929] #3: ffffff88039c8268 (request_class#2){+.+.}-{4:4}, at: __setup_irq (kernel/irq/internals.h:156 kernel/irq/manage.c:1596)  \n[    5.428331] #4: ffffff88039c80c8 (lock_class#2){....}-{2:2}, at: __setup_irq (kernel/irq/manage.c:1614)  \n[    5.436472] stack backtrace:  \n[    5.439359] CPU: 2 UID: 0 PID: 44 Comm: kworker/u17:1 Tainted: G        W          6.13.0-rc5+ #69  \n[    5.448690] Tainted: [W]=WARN  \n[    5.451656] Hardware name: xlnx,zynqmp (DT)  \n[    5.455845] Workqueue: events_unbound deferred_probe_work_func  \n[    5.461699] Call trace:  \n[    5.464147] show_stack+0x18/0x24 C  \n[    5.467821] dump_stack_lvl (lib/dump_stack.c:123)  \n[    5.471501] dump_stack (lib/dump_stack.c:130)  \n[    5.474824] __lock_acquire (kernel/locking/lockdep.c:4828 kernel/locking/lockdep.c:4898 kernel/locking/lockdep.c:5176)  \n[    5.478758] lock_acquire (arch/arm64/include/asm/percpu.h:40 kernel/locking/lockdep.c:467 kernel/locking/lockdep.c:5851 kernel/locking/lockdep.c:5814)  \n[    5.482429] _raw_spin_lock_irqsave (include/linux/spinlock_api_smp.h:111 kernel/locking/spinlock.c:162)  \n[    5.486797] xgpio_irq_unmask (drivers/gpio/gpio-xilinx.c:433 (discriminator 8))  \n[    5.490737] irq_enable (kernel/irq/internals.h:236 kernel/irq/chip.c:170 kernel/irq/chip.c:439 kernel/irq/chip.c:432 kernel/irq/chip.c:345)  \n[    5.494060] __irq_startup (kernel/irq/internals.h:241 kernel/irq/chip.c:180 kernel/irq/chip.c:250)  \n[    5.497645] irq_startup (kernel/irq/chip.c:270)  \n[    5.501143] __setup_irq (kernel/irq/manage.c:1807)  \n[    5.504728] request_threaded_irq (kernel/irq/manage.c:2208) \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"09 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-09T14:19:35.000000Z"}]}