From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-64051: accel/qaic: Add overflow check to remap_pfn_range during mmap
Date: Sun, 19 Jul 2026 17:38:33 +0200 [thread overview]
Message-ID: <2026071908-CVE-2026-64051-c665@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
accel/qaic: Add overflow check to remap_pfn_range during mmap
The call to remap_pfn_range in qaic_gem_object_mmap is susceptible to
(re)mapping beyond the VMA if the BO is too large. This can cause use
after free issues when munmap() unmaps only the VMA region and not the
additional mappings. To prevent this, check the remaining size of the
VMA before remapping and truncate the remapped length if sg->length is
too large.
[jhugo: fix braces from checkpatch --strict]
The Linux kernel CVE team has assigned CVE-2026-64051 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.4 with commit ff13be8303336ead5621712f2c55012d738878b5 and fixed in 6.6.142 with commit 9baafc2fea096279e75480f93fd5942e8336b510
Issue introduced in 6.4 with commit ff13be8303336ead5621712f2c55012d738878b5 and fixed in 6.12.92 with commit 8dd6edbe26770df147136c3f2ac976c873b82650
Issue introduced in 6.4 with commit ff13be8303336ead5621712f2c55012d738878b5 and fixed in 6.18.34 with commit 97a8e89cdef36207a8776edc03d6931763a06ad0
Issue introduced in 6.4 with commit ff13be8303336ead5621712f2c55012d738878b5 and fixed in 7.0.11 with commit 8c795012d0e06b7740e40319b86ff8d2a435098d
Issue introduced in 6.4 with commit ff13be8303336ead5621712f2c55012d738878b5 and fixed in 7.1 with commit aa16b2bc0f02709919e2435f531406531e5bcc69
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-64051
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/qaic/qaic_data.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/9baafc2fea096279e75480f93fd5942e8336b510
https://git.kernel.org/stable/c/8dd6edbe26770df147136c3f2ac976c873b82650
https://git.kernel.org/stable/c/97a8e89cdef36207a8776edc03d6931763a06ad0
https://git.kernel.org/stable/c/8c795012d0e06b7740e40319b86ff8d2a435098d
https://git.kernel.org/stable/c/aa16b2bc0f02709919e2435f531406531e5bcc69
reply other threads:[~2026-07-19 15:43 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=2026071908-CVE-2026-64051-c665@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.