From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43460: spi: rockchip-sfc: Fix double-free in remove() callback
Date: Fri, 8 May 2026 16:23:09 +0200 [thread overview]
Message-ID: <2026050801-CVE-2026-43460-5893@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
spi: rockchip-sfc: Fix double-free in remove() callback
The driver uses devm_spi_register_controller() for registration, which
automatically unregisters the controller via devm cleanup when the
device is removed. The manual call to spi_unregister_controller() in
the remove() callback can lead to a double-free.
And to make sure controller is unregistered before DMA buffer is
unmapped, switch to use spi_register_controller() in probe().
The Linux kernel CVE team has assigned CVE-2026-43460 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.14 with commit 8011709906d0d6ff1ba9589de5a906bf6e430782 and fixed in 6.18.19 with commit b6051f2bdd4bd3dde85b68558edd3a6843489221
Issue introduced in 6.14 with commit 8011709906d0d6ff1ba9589de5a906bf6e430782 and fixed in 6.19.9 with commit 85fb53351e6a3b921357a2178671e847a087e400
Issue introduced in 6.14 with commit 8011709906d0d6ff1ba9589de5a906bf6e430782 and fixed in 7.0 with commit 111e2863372c322e836e0c896f6dd9cf4ee08c71
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-43460
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:
drivers/spi/spi-rockchip-sfc.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/b6051f2bdd4bd3dde85b68558edd3a6843489221
https://git.kernel.org/stable/c/85fb53351e6a3b921357a2178671e847a087e400
https://git.kernel.org/stable/c/111e2863372c322e836e0c896f6dd9cf4ee08c71
reply other threads:[~2026-05-08 14:27 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=2026050801-CVE-2026-43460-5893@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