data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-43115 in the interactive tracker

CVE-2026-43115

srcu: Use irq_work to start GP in tiny SRCU

EPSS 0.2%

Published 2026-05-06 (5 months ago) by the Linux kernel CNA. Subsystem include/linux. Debian urgency: not yet assigned.

What to do, per Debian release

Debian's own status for CVE-2026-43115 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormvulnerable6.1.190-1No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication.
Debian 13trixievulnerable6.12.113-1No fix published anywhere yet, neither in Debian nor upstream for the series trixie tracks. Watch the Debian tracker page for this CVE. Advisories for trixie have historically landed a median of 11 days after publication.
Debian 14forkyfixed6.19.14-1Update the kernel and reboot. Fixed in 6.19.14-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed6.19.14-1Update the kernel and reboot. Fixed in 6.19.14-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

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()" ]

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

include/linux/srcutiny.h
kernel/rcu/srcutiny.c

What this is
SLEEPABLE READ-COPY UPDATE (SRCU)MAINTAINERS section matched on include/linux/srcu*.h · rcu@vger.kernel.org · Supported

Check it on the machine

grep -w CONFIG_TINY_SRCU /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

Show whether Debian builds this, per release

Debian does not build this code in 3 releases. It does build it in 1 release, so the answer depends on which release the machine runs.

  • bookwormn
  • trixieYnot built on amd64/amd64, amd64/cloud-amd64, amd64/rt/amd64, arm64/arm64, arm64/arm64-16k, arm64/cloud-arm64, arm64/rt/arm64, armhf/armmp, armhf/armmp-lpae, armhf/rt/armmp, ppc64el/powerpc64le, ppc64el/powerpc64le-64k, riscv64/riscv64, s390x/s390x
  • forky, sidn
n
not enabled on any flavour - this release does not build the code
Y
built in where it is built at all; some flavours do not build it
Build switch
CONFIG_TINY_SRCU

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published
2026-05-06 (5 months ago)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
0.15%, higher than 4.3% of all CVEssource
CISA KEV
not listedthe KEV catalogue
Debian urgency
not yet assignedsource
Subsystem
include/linux

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
4.126.18.5728768bc7ea0b
4.126.19.14bb37286db653
4.127.0a6fc88b22bc8

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2026-43115, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.