Answer in brief
CVE-2026-43115 records a Unknown severity vulnerability in srcu: Use irq_work to start GP in tiny SRCU. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d8be81735aa89413b333de488251f0e64e2be591 <28768bc7ea0b13f558a70f63cc3cfcd32d55d488 || >=d8be81735aa89413b333de488251f0e64e2be591 <bb37286db65368cb72ba8757ad86299c4e4a73fc || >=d8be81735aa89413b333de488251f0e64e2be591 <a6fc88b22bc8d12ad52e8412c667ec0f5bf055af | 28768bc7ea0b13f558a70f63cc3cfcd32d55d488, bb37286db65368cb72ba8757ad86299c4e4a73fc, a6fc88b22bc8d12ad52e8412c667ec0f5bf055af |
| Linux/Linuxgeneric | 4.12 | Not reported |
Published upstream
May 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 15, 2026
In the Linux kernel, the following vulnerability has been resolved: srcu: Use irq_work to start GP in tiny SRCU Tiny SRCU's srcu_gp_start_if_needed() directly calls schedule_work(), which acquires the workqueue pool->lock. This causes a lockdep splat when call_srcu() is called with a scheduler lock held, due to: call_srcu() [holding pi_lock] srcu_gp_start_if_needed() schedule_work() -> pool->lock workqueue_init() / create_worker() [holding pool->lock] wake_up_process() -> try_to_wake_up() -> pi_lock Also add irq_work_sync() to cleanup_srcu_struct() to prevent a use-after-free if a queued irq_work fires after cleanup begins. Tested with rcutorture SRCU-T and no lockdep warnings. [ Thanks to Boqun for similar fix in patch "rcu: Use an intermediate irq_work to start process_srcu()" ]
Quoted source text, attributed separately from HOL analysis.