CVE-2026-23101

MEDIUMNVD 4.74.7—
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory published 2026-02-04. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.7Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

leds: led-class: Only Add LED to leds_list when it is fully ready

Before this change the LED was added to leds_list before led_init_core() gets called adding it the list before led_classdev.set_brightness_work gets initialized.

This leaves a window where led_trigger_register() of a LED's default trigger will call led_trigger_set() which calls led_set_brightness() which in turn will end up queueing the *uninitialized* led_classdev.set_brightness_work.

This race gets hit by the lenovo-thinkpad-t14s EC driver which registers 2 LEDs with a default trigger provided by snd_ctl_led.ko in quick succession. The first led_classdev_register() causes an async modprobe of snd_ctl_led to run and that async modprobe manages to exactly hit the window where the second LED is on the leds_list without led_init_core() being called for it, resulting in:

------------[ cut here ]------------ WARNING: CPU: 11 PID: 5608 at kernel/workqueue.c:4234 __flush_work+0x344/0x390 Hardware name: LENOVO 21N2S01F0B/21N2S01F0B, BIOS N42ET93W (2.23 ) 09/01/2025 ... Call trace: __flush_work+0x344/0x390 (P) flush_work+0x2c/0x50 led_trigger_set+0x1c8/0x340 led_trigger_register+0x17c/0x1c0 led_trigger_register_simple+0x84/0xe8 snd_ctl_led_init+0x40/0xf88 [snd_ctl_led] do_one_initcall+0x5c/0x318 do_init_module+0x9c/0x2b8 load_module+0x7e0/0x998

Close the race window by moving the adding of the LED to leds_list to after the led_init_core() call.

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
21(Track)
EG Risk 21/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity47% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

February 4, 2026

Last Modified

June 17, 2026

Advisory Details (7)

Auto-updated Aug 13, 2026
No patch confirmed yet.
generic

leds: led-class: Only Add LED to leds_list when it is fully ready - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f7a6df659af777058833802c29b3b7974db5e78a
generic

leds: led-class: Only Add LED to leds_list when it is fully ready - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e90c861411fc84629a240384b0a72830539d3386
generic

leds: led-class: Only Add LED to leds_list when it is fully ready - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/da565bf98c9ad0eabcb09fc97859e0b52f98b7c3
generic

leds: led-class: Only Add LED to leds_list when it is fully ready - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d1883cefd31752f0504b94c3bcfa1f6d511d6e87
generic

leds: led-class: Only Add LED to leds_list when it is fully ready - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d117fdcb21b05c0e0460261d017b92303cd9ba77
generic

leds: led-class: Only Add LED to leds_list when it is fully ready - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/78822628165f3d817382f67f91129161159ca234
generic

leds: led-class: Only Add LED to leds_list when it is fully ready - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2757f7748ce2d0fa44112024907bafb37e104d6e

Patch Availability(21)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1057.57~20.04.1) @ focal2026-06-07ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.176.186~20.04.1) @ focal2026-06-07ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.176.161) @ jammy2026-06-07ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1105.95) @ jammy2026-06-07ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1104.108) @ jammy2026-06-07ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1057.57) @ jammy2026-06-07ubuntu
ubuntulinux-tools-kvm-5.15 (5.15.0.1097.93) @ jammy2026-06-07ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1110.95) @ jammy2026-06-07ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1070 (5.15.0-1070.74) @ jammy2026-06-07ubuntu
ubuntulinux-tools-ibm-5.15 (5.15.0.1099.95) @ jammy2026-06-07ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1099.97) @ jammy2026-06-07ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-06-07ubuntu
ubuntulinux-virtual-6.8 (6.8.0-117.117) @ noble2026-06-07ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1054.57.1) @ noble2026-06-07ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-116.116+fips1) @ noble2026-06-07ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1106.115~20.04.1) @ focal2026-06-07ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1054.57~22.04.1) @ jammy2026-06-07ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1056.62) @ noble2026-06-07ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1024.24) @ noble2026-06-07ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1059.65+fips1) @ noble2026-06-07ubuntu
linuxKernel @ 5.10.249—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (48 versions)5.10.249-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.159-1~deb11u1 (14 versions)6.1.162-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (46 versions)6.1.162-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.69-1~bpo12+1 (10 versions)6.12.69-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (96 versions)6.18.8-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 167 total refreshes for this CVE.

  1. 2026-09-18 23:23 UTCOSV refresh
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 14:52 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:11 UTCEPSS rescore
  15. 2026-09-01 13:53 UTCEPSS rescore
  16. 2026-09-01 04:39 UTCEPSS rescore
  17. 2026-08-31 03:02 UTCOSV refresh
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 14:46 UTCEPSS rescore
  23. 2026-08-25 13:48 UTCEPSS rescore
  24. 2026-08-23 00:19 UTCEPSS rescore
  25. 2026-08-20 22:55 UTCEPSS rescore
Show 75 more
  1. 2026-08-19 17:03 UTCEPSS rescore
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 02:14 UTCEPSS rescore
  5. 2026-08-15 01:30 UTCEPSS rescore
  6. 2026-08-14 11:13 UTCEG score recompute
  7. 2026-08-14 11:13 UTCVendor advisory
  8. 2026-08-14 11:13 UTCGHSA enrichment
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-13 03:32 UTCEG score recompute
  11. 2026-08-13 03:32 UTCVendor advisory
  12. 2026-08-13 03:32 UTCGHSA enrichment
  13. 2026-08-12 13:50 UTCEPSS rescore
  14. 2026-08-11 13:42 UTCEPSS rescore
  15. 2026-08-11 00:00 UTCEPSS rescore
  16. 2026-08-09 15:52 UTCEG score recompute
  17. 2026-08-09 15:52 UTCVendor advisory
  18. 2026-08-09 15:52 UTCGHSA enrichment
  19. 2026-08-09 13:46 UTCEPSS rescore
  20. 2026-08-08 16:37 UTCEPSS rescore
  21. 2026-08-07 22:47 UTCEG score recompute
  22. 2026-08-07 22:47 UTCVendor advisory
  23. 2026-08-07 22:47 UTCGHSA enrichment
  24. 2026-08-06 13:46 UTCEPSS rescore
  25. 2026-08-06 04:23 UTCEG score recompute
  26. 2026-08-06 04:23 UTCVendor advisory
  27. 2026-08-06 04:23 UTCGHSA enrichment
  28. 2026-08-05 19:17 UTCEPSS rescore
  29. 2026-08-04 10:38 UTCEPSS rescore
  30. 2026-08-03 10:35 UTCEPSS rescore
  31. 2026-08-02 21:26 UTCEG score recompute
  32. 2026-08-02 21:26 UTCVendor advisory
  33. 2026-08-02 21:26 UTCGHSA enrichment
  34. 2026-08-02 02:26 UTCEPSS rescore
  35. 2026-08-01 04:15 UTCEPSS rescore
  36. 2026-07-30 22:51 UTCOSV refresh
  37. 2026-07-30 01:30 UTCEPSS rescore
  38. 2026-07-27 14:13 UTCEPSS rescore
  39. 2026-07-26 14:54 UTCEPSS rescore
  40. 2026-07-26 14:54 UTCEPSS rescore
  41. 2026-07-25 14:17 UTCEPSS rescore
  42. 2026-07-25 14:17 UTCEPSS rescore
  43. 2026-07-24 14:17 UTCEPSS rescore
  44. 2026-07-23 14:18 UTCEPSS rescore
  45. 2026-07-23 14:18 UTCEPSS rescore
  46. 2026-07-23 03:06 UTCEG score recompute
  47. 2026-07-22 14:08 UTCEPSS rescore
  48. 2026-07-21 15:24 UTCEPSS rescore
  49. 2026-07-21 15:24 UTCEPSS rescore
  50. 2026-07-20 17:08 UTCEPSS rescore
  51. 2026-07-19 14:31 UTCEPSS rescore
  52. 2026-07-19 14:31 UTCEPSS rescore
  53. 2026-07-18 10:04 UTCEPSS rescore
  54. 2026-07-18 10:04 UTCEPSS rescore
  55. 2026-07-16 17:03 UTCEPSS rescore
  56. 2026-07-16 17:03 UTCEPSS rescore
  57. 2026-07-15 16:57 UTCEPSS rescore
  58. 2026-07-15 16:57 UTCEPSS rescore
  59. 2026-07-15 02:00 UTCEPSS rescore
  60. 2026-07-15 02:00 UTCEPSS rescore
  61. 2026-07-13 22:30 UTCEPSS rescore
  62. 2026-07-13 08:07 UTCOSV refresh
  63. 2026-07-13 06:13 UTCEPSS rescore
  64. 2026-07-13 06:13 UTCEPSS rescore
  65. 2026-07-11 08:27 UTCEPSS rescore
  66. 2026-07-09 19:10 UTCEPSS rescore
  67. 2026-07-08 15:15 UTCEPSS rescore
  68. 2026-07-08 15:15 UTCEPSS rescore
  69. 2026-07-07 13:46 UTCEPSS rescore
  70. 2026-07-06 16:27 UTCEPSS rescore
  71. 2026-07-06 16:27 UTCEPSS rescore
  72. 2026-07-05 02:30 UTCEPSS rescore
  73. 2026-07-04 06:31 UTCEPSS rescore
  74. 2026-07-04 06:31 UTCEPSS rescore
  75. 2026-07-01 15:06 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-23101?
CVE-2026-23101 is a medium vulnerability published on February 4, 2026. In the Linux kernel, the following vulnerability has been resolved: leds: led-class: Only Add LED to leds_list when it is fully ready Before this change the LED was added to ledslist before ledinit_core() gets called adding it the list before ledclassdev.setbrightness_work gets initialized. This…
When was CVE-2026-23101 disclosed?
CVE-2026-23101 was first published in the National Vulnerability Database on February 4, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23101 actively exploited?
CVE-2026-23101 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.5% of all scored CVEs.
What is the CVSS score of CVE-2026-23101?
CVE-2026-23101 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2026-23101?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23101, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-23101

Explore →

Is Your Infrastructure Affected by CVE-2026-23101?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs