CVE-2026-23101 — leds: led-class: Only Add LED to leds_list when it is fully ready
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.1% (30-day exploitation probability)+0
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux | version 3.7≥ d23a22a74fded23a12434c9463fe66cec2b0afcd and < d1883cefd31752f0504b94c3bcfa1f6d511d6e87≥ d23a22a74fded23a12434c9463fe66cec2b0afcd and < 78822628165f3d817382f67f91129161159ca234≥ d23a22a74fded23a12434c9463fe66cec2b0afcd and < da565bf98c9ad0eabcb09fc97859e0b52f98b7c3≥ d23a22a74fded23a12434c9463fe66cec2b0afcd and < 2757f7748ce2d0fa44112024907bafb37e104d6e≥ d23a22a74fded23a12434c9463fe66cec2b0afcd and < e90c861411fc84629a240384b0a72830539d3386≥ d23a22a74fded23a12434c9463fe66cec2b0afcd and < d117fdcb21b05c0e0460261d017b92303cd9ba77≥ d23a22a74fded23a12434c9463fe66cec2b0afcd and < f7a6df659af777058833802c29b3b7974db5e78a | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel |
version 6.19-rc5version 6.19-rc6≥ 3.7 and < 5.10.249version 6.19-rc4version 6.19-rc3version 6.19-rc2version 6.19-rc1≥ 6.13 and < 6.18.8 and 4 more≥ 6.7 and < 6.12.68≥ 6.2 and < 6.6.122≥ 5.16 and < 6.1.162≥ 5.11 and < 5.15.199 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 4.7 | CVSS 3.1 | Medium | 1.0 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.14%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 4.7
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
7 on the record
- git.kernel.org/stable/c/2757f7748ce2d0fa44112024907bafb37e104d6e
- git.kernel.org/stable/c/e90c861411fc84629a240384b0a72830539d3386
- git.kernel.org/stable/c/d1883cefd31752f0504b94c3bcfa1f6d511d6e87
- git.kernel.org/stable/c/f7a6df659af777058833802c29b3b7974db5e78a
- git.kernel.org/stable/c/78822628165f3d817382f67f91129161159ca234
- git.kernel.org/stable/c/da565bf98c9ad0eabcb09fc97859e0b52f98b7c3
- git.kernel.org/stable/c/d117fdcb21b05c0e0460261d017b92303cd9ba77
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 10h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 10h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-23101 is "leds: led-class: Only Add LED to leds_list when it is fully ready", rated Medium. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.7 describes technical severity. EPSS 0.14% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.