From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74423: accel/amdxdna: Fix leak when pinning ubuf pages
Date: Sat, 15 Aug 2026 15:12:30 +0900 [thread overview]
Message-ID: <2026081513-CVE-2026-74423-8ed6@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
accel/amdxdna: Fix leak when pinning ubuf pages
When pin_user_pages_fast() returns fewer pages than requested, the pages
that were successfully pinned are not released, leading to a leak.
Fix this by unpinning any partially pinned pages before returning failure.
The Linux kernel CVE team has assigned CVE-2026-74423 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.18 with commit bd72d4acda1069579b35123e3cc0b21ec1193a21 and fixed in 6.18.40 with commit 68dc52f308a17c3103a349f722dd5dea32c50a88
Issue introduced in 6.18 with commit bd72d4acda1069579b35123e3cc0b21ec1193a21 and fixed in 7.1.5 with commit 5b24e0903c58cdfd8ebfecb6ac5c5bacfd06e4e7
Issue introduced in 6.18 with commit bd72d4acda1069579b35123e3cc0b21ec1193a21 and fixed in 7.2-rc1 with commit d946347edc4f0a7b846325323d77e936a4c90d0f
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-74423
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_ubuf.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/68dc52f308a17c3103a349f722dd5dea32c50a88
https://git.kernel.org/stable/c/5b24e0903c58cdfd8ebfecb6ac5c5bacfd06e4e7
https://git.kernel.org/stable/c/d946347edc4f0a7b846325323d77e936a4c90d0f
reply other threads:[~2026-08-15 6:40 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=2026081513-CVE-2026-74423-8ed6@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.