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

Published Feb 9, 2025
·
Updated

gpio: xilinx: Convert gpiolock to raw spinlock

Affected Software

17 affected componentsFixes available
Linux Linux kernel>=6.13.0-rc5
Linux Linux kernel>=5.12<6.6.74
Linux Linux kernel>=6.7<6.12.11
Linux Linux kernel=6.13-rc1
Linux Linux kernel=6.13-rc2
Linux Linux kernel=6.13-rc3
Linux Linux kernel=6.13-rc4
Linux Linux kernel=6.13-rc5
Linux Linux kernel=6.13-rc6
Linux Linux kernel=6.13-rc7
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1
Microsoft cbl2 kernel 5.15.182.1-1
Microsoft azl3 kernel 6.6.64.2-9<6.6.76.1-1
6.6.76.1-1
Microsoft azl3 kernel 6.6.76.1-1<6.6.76.1-1
6.6.76.1-1
Microsoft cbl2 kernel 5.15.182.1-1<5.15.179.1-1
5.15.179.1-1
Microsoft cbl2 kernel 5.15.179.1-1<5.15.179.1-1
5.15.179.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.27-1
  2. Upgrade

    Upgrade debian/linux-6.1 to a version that resolves this vulnerability.

    Fixed in 6.1.129-1~deb11u1
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.76.1-1
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 5.15.179.1-1
  5. Upgrade

    Upgrade Linux kernel gpio: xilinx to a version that resolves this vulnerability.

    Fixed in 6.13.0-rc5+Patch Last updated 25 April 2025
  6. Configuration

    In the Linux kernel (gpio: xilinx), convert gpio_lock to a raw spinlock so irq_chip functions may be called in raw spinlock context, and ensure any of the driver’s internal locking uses a raw spinlock as well (to fix the lockdep splat showing kworker locking &chip->gpio_lock in xgpio_irq_unmask at drivers/gpio/gpio-xilinx.c:433).

    gpio-xilinx.c gpio_lock locking type = raw spinlock

Event History

Feb 9, 2025
CVE Published
via MITRE·11:37 AM
Data Sourced
via MITRE·11:37 AM
Description
Data Sourced
via NVD·12:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Mar 14, 2025
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Updated
via Microsoft·07:00 AM
SeverityAffected Software
Updated
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
Severity
May 5, 2025
Data Sourced
via Ubuntu·02:34 PM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-21684?

CVE-2025-21684 has been classified with a severity that necessitates attention due to potential impact on system stability.

2

How do I fix CVE-2025-21684?

To fix CVE-2025-21684, update the Linux kernel to the latest version where this vulnerability has been addressed.

3

Which versions of the Linux kernel are affected by CVE-2025-21684?

CVE-2025-21684 affects Linux kernel versions starting from 6.13.0-rc5.

4

What are the potential risks of CVE-2025-21684?

The risks associated with CVE-2025-21684 include potential system instability and security implications related to improper lock handling.

5

Is there a workaround for CVE-2025-21684?

Currently, updating to the patched versions is the recommended approach, as no effective workaround is known.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203