From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43481: net-shapers: don't free reply skb after genlmsg_reply()
Date: Wed, 13 May 2026 17:08:49 +0200 [thread overview]
Message-ID: <2026051348-CVE-2026-43481-6f80@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net-shapers: don't free reply skb after genlmsg_reply()
genlmsg_reply() hands the reply skb to netlink, and
netlink_unicast() consumes it on all return paths, whether the
skb is queued successfully or freed on an error path.
net_shaper_nl_get_doit() and net_shaper_nl_cap_get_doit()
currently jump to free_msg after genlmsg_reply() fails and call
nlmsg_free(msg), which can hit the same skb twice.
Return the genlmsg_reply() error directly and keep free_msg
only for pre-reply failures.
The Linux kernel CVE team has assigned CVE-2026-43481 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.13 with commit 4b623f9f0f59652ea71fcb27d60b4c3b65126dbb and fixed in 6.18.19 with commit 8738dcc844fff7d0157ee775230e95df3b1884d7
Issue introduced in 6.13 with commit 4b623f9f0f59652ea71fcb27d60b4c3b65126dbb and fixed in 6.19.9 with commit 83f7b54242d0abbfce35a55c01322f50962ed3ee
Issue introduced in 6.13 with commit 4b623f9f0f59652ea71fcb27d60b4c3b65126dbb and fixed in 7.0 with commit 57885276cc16a2e2b76282c808a4e84cbecb3aae
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-43481
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/shaper/shaper.c
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/8738dcc844fff7d0157ee775230e95df3b1884d7
https://git.kernel.org/stable/c/83f7b54242d0abbfce35a55c01322f50962ed3ee
https://git.kernel.org/stable/c/57885276cc16a2e2b76282c808a4e84cbecb3aae
reply other threads:[~2026-05-13 15:09 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=2026051348-CVE-2026-43481-6f80@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