From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-93103: RDMA/hfi1: Preserve unit 0 on allocation failure
Date: Thu, 17 Sep 2026 17:16:20 +0100 [thread overview]
Message-ID: <2026091745-CVE-2026-93103-fb4e@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
RDMA/hfi1: Preserve unit 0 on allocation failure
hfi1_free_devdata() assumes that the device was inserted into the unit
table and unconditionally erases dd->unit. If xa_alloc_irq() fails, the
zero-initialized unit remains zero, so full cleanup can remove an
unrelated device from index 0.
Release only the rdmavt allocation and return immediately while the unit
table has not acquired the device.
The Linux kernel CVE team has assigned CVE-2026-93103 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.2 with commit 03b92789e5cfdac66805c1a98f1ec67336199d56 and fixed in 5.10.270 with commit 852637d3ee56aed8ea3ee8948eda21eca406c051
Issue introduced in 5.2 with commit 03b92789e5cfdac66805c1a98f1ec67336199d56 and fixed in 5.15.221 with commit 3d0e5252b8d0345ef494763ca31e3ddd666e02cb
Issue introduced in 5.2 with commit 03b92789e5cfdac66805c1a98f1ec67336199d56 and fixed in 6.1.188 with commit 0feb29d434e6cc0ebefec4f77be014c85ad751b0
Issue introduced in 5.2 with commit 03b92789e5cfdac66805c1a98f1ec67336199d56 and fixed in 6.6.157 with commit 3f1e196eb66b8cd3882e373794d6cea46f150a20
Issue introduced in 5.2 with commit 03b92789e5cfdac66805c1a98f1ec67336199d56 and fixed in 6.12.110 with commit 4ff9d58d34758e9633078b37e8d5289b513ff80e
Issue introduced in 5.2 with commit 03b92789e5cfdac66805c1a98f1ec67336199d56 and fixed in 6.18.52 with commit fd4d3ad5f244a867166d1e2da7ece3d82878ec81
Issue introduced in 5.2 with commit 03b92789e5cfdac66805c1a98f1ec67336199d56 and fixed in 7.2.6 with commit 4204f5c0312ba136181a6e148ffa0bfaf95a4cc1
Issue introduced in 5.2 with commit 03b92789e5cfdac66805c1a98f1ec67336199d56 and fixed in 7.3-rc1 with commit 2e3809ad8911f5d5581b3f046bd628417bface76
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-93103
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/infiniband/hw/hfi1/init.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/852637d3ee56aed8ea3ee8948eda21eca406c051
https://git.kernel.org/stable/c/3d0e5252b8d0345ef494763ca31e3ddd666e02cb
https://git.kernel.org/stable/c/0feb29d434e6cc0ebefec4f77be014c85ad751b0
https://git.kernel.org/stable/c/3f1e196eb66b8cd3882e373794d6cea46f150a20
https://git.kernel.org/stable/c/4ff9d58d34758e9633078b37e8d5289b513ff80e
https://git.kernel.org/stable/c/fd4d3ad5f244a867166d1e2da7ece3d82878ec81
https://git.kernel.org/stable/c/4204f5c0312ba136181a6e148ffa0bfaf95a4cc1
https://git.kernel.org/stable/c/2e3809ad8911f5d5581b3f046bd628417bface76
reply other threads:[~2026-09-17 16:37 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=2026091745-CVE-2026-93103-fb4e@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.