Skip to main content
VulnerabilityPublished Updated

CVE-2025-21684: Linux kernel · gpio: xilinx: Convert gpio_lock to raw spinlock

Source GCVE Database

0
Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 30 Oct 2026, 01:10 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Feb 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

AI-suggested

A fix is available that converts gpio_lock to a raw spinlock in the Linux kernel's Xilinx GPIO driver. Users should update their Linux kernel to a version that includes this fix. No other mitigation is indicated.

Description

CVE-2025-21684 is a medium severity vulnerability in the Linux kernel's Xilinx GPIO driver. The issue arises because irq_chip functions may be called in raw spinlock context, but the driver used a regular spinlock instead of a raw spinlock for internal locking. This mismatch can cause lockdep warnings and invalid wait context bugs, potentially leading to kernel instability or crashes. The vulnerability has been fixed by converting gpio_lock to a raw spinlock to match the irq_chip context requirements.

References

Community reviews

Loading reviews…