From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id EFB903A7F4B for ; Sun, 19 Jul 2026 15:43:15 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784475797; cv=none; b=CCBcyP9w1NG+jkMsToh6Q98h89qhm/oLYTJlbLBz3GTGozTRZJJOkJKXRx5mxqqbGRUjA4OXMQFRsEuxp1PhoW1XfWMZprbpIev0NiBf/YE4pgPFhYdUFrn+INKUidBx2WIyGAlgyES8wL5cvX1TkFn1+twedfovDiQxrx8SuF8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784475797; c=relaxed/simple; bh=q/uLQ+ZEx23rSyzHATsrvrj6eJMIbndy+2tBAsJvLtE=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=ggjr061qRRnNe0RtRxjSUVAmJloqCLqFNvfQP7mw/65Oq53QbIznavt5MX6rfmMm6c4F6FqcXbNfjYZtsqM/E2mQVt23PQKvQ1iCB4IdmneMElINH8ZIP62+G156df6h6i5rRiJWszz0B6BmcCRmeXL24JD+LSpEOgtJe29qjrc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=wXlKQT0G; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="wXlKQT0G" Received: by smtp.kernel.org (Postfix) with ESMTPSA id EE44A1F000E9; Sun, 19 Jul 2026 15:43:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1784475795; bh=XEMtao1BkR+ru5jH9uAJ2R6i19VL/ea19a5MW+zwP7A=; h=From:To:Cc:Subject:Date:Reply-To; b=wXlKQT0G2zafRBtNEhT+bHcuno2IYaWVXxql4vq0ZRxH9lI9jfnWhJOhHHJUFvFvb QP1LRSIir+aELdyX46rOzzhkUnEcvAwqH8LRAlO4yfEZqfLDGM9WnsUpvZbMtef3ko N62jaaGjYbDdyzUlolU7wtNZPrZm43ggud9LrJaA= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-64051: accel/qaic: Add overflow check to remap_pfn_range during mmap Date: Sun, 19 Jul 2026 17:38:33 +0200 Message-ID: <2026071908-CVE-2026-64051-c665@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2871; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=qIAsUEh4RuhshvEMABOap7iTY9l7z+biBizBciU1ym8=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkx7xOqGhJ/G0X8ZtC32nZA7NL33/OzmtZ0r3pucF5Zy manufeZjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZhIogDDggVea2rsbPf911Nf KO5v/lzw6jRGS4YF89n9PPUce1OmbxNgnHA+eeqNOQx/AA== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman 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