From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43382: batman-adv: Avoid double-rtnl_lock ELP metric worker
Date: Fri, 8 May 2026 16:21:51 +0200 [thread overview]
Message-ID: <2026050833-CVE-2026-43382-d102@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
batman-adv: Avoid double-rtnl_lock ELP metric worker
batadv_v_elp_get_throughput() might be called when the RTNL lock is already
held. This could be problematic when the work queue item is cancelled via
cancel_delayed_work_sync() in batadv_v_elp_iface_disable(). In this case,
an rtnl_lock() would cause a deadlock.
To avoid this, rtnl_trylock() was used in this function to skip the
retrieval of the ethtool information in case the RTNL lock was already
held.
But for cfg80211 interfaces, batadv_get_real_netdev() was called - which
also uses rtnl_lock(). The approach for __ethtool_get_link_ksettings() must
also be used instead and the lockless version __batadv_get_real_netdev()
has to be called.
The Linux kernel CVE team has assigned CVE-2026-43382 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.10.235 with commit a0019971f340ae02ba54cf1861f72da7e03e6b66 and fixed in 5.10.253 with commit 4c3ae249431b4fcb315d7dfb4c3a13f9e443fd9b
Issue introduced in 5.15.179 with commit 3c0e0aecb78cb2a2ca1dc701982d08fedb088dc6 and fixed in 5.15.203 with commit 192f40ad8a7dac58dae9199a065dbf7e6e67b75b
Issue introduced in 6.1.129 with commit 781a06fd265a8151f7601122d9c2e985663828ff and fixed in 6.1.167 with commit fa7b4edfbabdf9235b0ab4bea297fc12b3bec9ca
Issue introduced in 6.6.79 with commit a7aa2317285806640c844acd4cd2cd768e395264 and fixed in 6.6.130 with commit f3ca45673dab0514a887231de6f3243a699d5bfd
Issue introduced in 6.12.16 with commit 0fdc3c166ac17b26014313fa2b93696354511b24 and fixed in 6.12.78 with commit b7e5d8ddfdf1d6e9e0808d1adf7736a107372d77
Issue introduced in 6.14 with commit 8c8ecc98f5c65947b0070a24bac11e12e47cc65d and fixed in 6.18.19 with commit 2ab9f2531d37775cd79228c1f5d80e6bd08d11d3
Issue introduced in 6.14 with commit 8c8ecc98f5c65947b0070a24bac11e12e47cc65d and fixed in 6.19.9 with commit 77808fe7d03ad0062840b95f431869a8b3d88b24
Issue introduced in 6.14 with commit 8c8ecc98f5c65947b0070a24bac11e12e47cc65d and fixed in 7.0 with commit cfc83a3c71517b59c1047db57da31e26a9dc2f33
Issue introduced in 5.4.291 with commit 1c334629176c2d644befc31a20d4bf75542f7631
Issue introduced in 6.13.4 with commit af264c2a9adc37f4bdf88ca7f3affa15d8c7de9e
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-43382
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
net/batman-adv/bat_v_elp.c
net/batman-adv/hard-interface.c
net/batman-adv/hard-interface.h
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/4c3ae249431b4fcb315d7dfb4c3a13f9e443fd9b
https://git.kernel.org/stable/c/192f40ad8a7dac58dae9199a065dbf7e6e67b75b
https://git.kernel.org/stable/c/fa7b4edfbabdf9235b0ab4bea297fc12b3bec9ca
https://git.kernel.org/stable/c/f3ca45673dab0514a887231de6f3243a699d5bfd
https://git.kernel.org/stable/c/b7e5d8ddfdf1d6e9e0808d1adf7736a107372d77
https://git.kernel.org/stable/c/2ab9f2531d37775cd79228c1f5d80e6bd08d11d3
https://git.kernel.org/stable/c/77808fe7d03ad0062840b95f431869a8b3d88b24
https://git.kernel.org/stable/c/cfc83a3c71517b59c1047db57da31e26a9dc2f33
reply other threads:[~2026-05-08 14:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026050833-CVE-2026-43382-d102@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox