From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-45931: accel/amdxdna: Hold mm structure across iommu_sva_unbind_device()
Date: Wed, 27 May 2026 14:19:33 +0200 [thread overview]
Message-ID: <2026052727-CVE-2026-45931-e8b8@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
accel/amdxdna: Hold mm structure across iommu_sva_unbind_device()
Some tests trigger a crash in iommu_sva_unbind_device() due to
accessing iommu_mm after the associated mm structure has been
freed.
Fix this by taking an explicit reference to the mm structure
after successfully binding the device, and releasing it only
after the device is unbound. This ensures the mm remains valid
for the entire SVA bind/unbind lifetime.
The Linux kernel CVE team has assigned CVE-2026-45931 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.14 with commit be462c97b7dfd24999babe39cce3de224ebe1f80 and fixed in 6.18.14 with commit f6b4c1d98a7b8040d4d02e89425b3942016a2c2c
Issue introduced in 6.14 with commit be462c97b7dfd24999babe39cce3de224ebe1f80 and fixed in 6.19.4 with commit f31ccf6278132a35a652fe5eeac3941e1e912398
Issue introduced in 6.14 with commit be462c97b7dfd24999babe39cce3de224ebe1f80 and fixed in 7.0 with commit a9162439ad792afcddc04718408ec1380b7a5f63
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-45931
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/accel/amdxdna/amdxdna_pci_drv.c
drivers/accel/amdxdna/amdxdna_pci_drv.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/f6b4c1d98a7b8040d4d02e89425b3942016a2c2c
https://git.kernel.org/stable/c/f31ccf6278132a35a652fe5eeac3941e1e912398
https://git.kernel.org/stable/c/a9162439ad792afcddc04718408ec1380b7a5f63
reply other threads:[~2026-05-27 12:24 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=2026052727-CVE-2026-45931-e8b8@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.