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 67E705867EF for ; Fri, 11 Sep 2026 19:59:41 +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=1789156789; cv=none; b=FM5jSEgzuJx3uO59RCpPCFNQ4mNQsaVCWm0PxFa2xwVpLGVGfNdjmS/kJAs1xyMVxSfnPtWI2X3tBVk6I+lMr/QPsemQSyQqPqu00t/gM3HgnWTv4/0Ri0azgeMeK7A7gxx/p0DXkO7Um+LqW2/UiDgsS7erKbysimM2R24hUBE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789156789; c=relaxed/simple; bh=pzehcUxNb8gB5znMFrobOgoV6fMwYoRegy4CTpjbohg=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=FVS3mzudjl7d8UHb0j9t/VKXOc7LQMvv1q39dyA4m8x4FjyykQSbrkiTNXOBbO55dCiLSEpktQojoDFpDEw0QG2DsNp0c/i9gAlRN5ODA5WNRWiYh+woJGrNSarISd4ftZ3nNACeYFRvwFCeMMpxkajXZE7hlIABiqmf9o4PgJQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=xTmuI154; 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="xTmuI154" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 374A51F000FF; Fri, 11 Sep 2026 19:59:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789156780; bh=t/rBWljDA0Z7YjL8C9VspnuDJWYtUDLRhqcNbdgiTac=; h=From:To:Cc:Subject:Date:Reply-To; b=xTmuI154fF41jZBO6tMV8exjaslgcovpVOKDojjHcA2Fpl3ObZZ2iUO8cEFkjW3SQ pdHlrjP0ajsRulENOKBvgOVIpDAKgpTZUkMJM/Jhz8J8hip7mLu+c2NOjd9gUuxh3K slrf2+gcVzQx1slLkkUg5pM8hRiWMclNdLKpGCgw= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-89587: ACPI: pfr_update: fix stack buffer overflow in query_capability() Date: Fri, 11 Sep 2026 21:44:36 +0200 Message-ID: <2026091129-CVE-2026-89587-1c31@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=3264; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=I+6b+loMGsoWO9tHlwg44pH2TNvj1vU7pEWjamRYM1o=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlLIjOTD5/3UC2zXOanvJptVhu7+vHszivT3kjPFPy88 /Wp7qDAjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZhI8RmGBQtW1Fx+9S60LCLM r9Ih4y0DY9RzO4bZbH+Fp5UWubDtK95x61psm9ShHew9AA== 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: ACPI: pfr_update: fix stack buffer overflow in query_capability() query_capability() copies four ACPI buffer objects returned by the firmware _DSM into fixed-size u8[16] fields in struct pfru_update_cap_info using memcpy with the firmware-supplied length: memcpy(&cap_hdr->code_type, elements[CAP_CODE_TYPE_IDX].buffer.pointer, elements[CAP_CODE_TYPE_IDX].buffer.length); The same pattern repeats for drv_type, platform_id, and oem_id. If the firmware returns buffer.length > 16 for any of these fields, memcpy writes past the destination array. struct pfru_update_cap_info is stack-allocated in pfru_ioctl(). Confirmed with KASAN on 7.2-rc6: three stack-out-of-bounds reports are generated when a DSM returns 64-byte buffers, with writes reaching 44 bytes past the end of cap_hdr's [64, 156) frame window into adjacent stack redzones. Introduce a helper pointer to out_obj->package.elements and use it to validate each buffer length against its destination field size before copying, returning -EINVAL if the firmware supplies an oversized buffer. The Linux kernel CVE team has assigned CVE-2026-89587 to this issue. Affected and fixed versions =========================== Issue introduced in 5.17 with commit 0db89fa243e5edc5de38c88b369e4c3755c5fb74 and fixed in 6.12.109 with commit a2151624b55029dad0ca7efd17fb83a0461c8843 Issue introduced in 5.17 with commit 0db89fa243e5edc5de38c88b369e4c3755c5fb74 and fixed in 6.18.50 with commit 6d4ed2fd022bc862b156e53aae163b61259e1caa Issue introduced in 5.17 with commit 0db89fa243e5edc5de38c88b369e4c3755c5fb74 and fixed in 7.2.4 with commit 15d2b7f38f95d28652170344f39ee492c55e567c Issue introduced in 5.17 with commit 0db89fa243e5edc5de38c88b369e4c3755c5fb74 and fixed in 7.3-rc1 with commit ced45be0073a8a31b30b4a7f68cd3a15734515de 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-89587 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/acpi/pfr_update.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/a2151624b55029dad0ca7efd17fb83a0461c8843 https://git.kernel.org/stable/c/6d4ed2fd022bc862b156e53aae163b61259e1caa https://git.kernel.org/stable/c/15d2b7f38f95d28652170344f39ee492c55e567c https://git.kernel.org/stable/c/ced45be0073a8a31b30b4a7f68cd3a15734515de