Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 22 days later

    Published

  3. · 9 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-23101, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.11% · top 99% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.7.

Affected products

  • Linux · Linux

    • affected d23a22a74fded23a12434c9463fe66cec2b0afcd – < f7a6df659af777058833802c29b3b7974db5e78a
    • affected d23a22a74fded23a12434c9463fe66cec2b0afcd – < d117fdcb21b05c0e0460261d017b92303cd9ba77
    • affected d23a22a74fded23a12434c9463fe66cec2b0afcd – < e90c861411fc84629a240384b0a72830539d3386
    • affected d23a22a74fded23a12434c9463fe66cec2b0afcd – < 2757f7748ce2d0fa44112024907bafb37e104d6e
    • affected d23a22a74fded23a12434c9463fe66cec2b0afcd – < da565bf98c9ad0eabcb09fc97859e0b52f98b7c3
    • affected d23a22a74fded23a12434c9463fe66cec2b0afcd – < 78822628165f3d817382f67f91129161159ca234
    • affected d23a22a74fded23a12434c9463fe66cec2b0afcd – < d1883cefd31752f0504b94c3bcfa1f6d511d6e87
  • Linux · Linux

    • affected 3.7
    • unaffected < 3.7
    • unaffected 5.10.249 – ≤ 5.10.*
    • unaffected 5.15.199 – ≤ 5.15.*
    • unaffected 6.1.162 – ≤ 6.1.*
    • unaffected 6.6.122 – ≤ 6.6.*
    • unaffected 6.12.68 – ≤ 6.12.*
    • unaffected 6.18.8 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-23101 badge
[![CVE-2026-23101](https://cveledger.app/badge/CVE-2026-23101.svg)](https://cveledger.app/cve/CVE-2026-23101)

Record last updated .