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 8CAA8352005 for ; Sat, 15 Aug 2026 06:10:40 +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=1786774241; cv=none; b=gluoz+E1Bw5KKpKI6quHv4G/6YVuKZkw6A9s4UPAbrqQQXHoaw6qrjMKFjgwEWLDdb9oNVLJG8S9iOWS62sdwBNzzQqy8ryhvSrzmW+MtdbG5kHL5MEG/+906kBgGYP7yZJQfBRsoZGD8hgeeOa0PA98opiIa5lYXy0PhaMR/Uc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786774241; c=relaxed/simple; bh=EMDMEpjy8aw1Nr349RFFBOZcAWl9w1mIdr2eI6k6Ajs=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=E3QKJTGAfk/Fy4VpuwpOpPT8g8TaKsVhyCrkKUvOTEHcMBJwDNMIrczN+nJeo5CDl19oBTjaFslZ1JkO5F1+ORZv0+zQPUg11cWe1WovcTDnx81i+8Cb1vtqS0zgIdcNJG+pThvfChIf9epOiFpXeIhwxoIpZ9RTBLHNT2FGLc0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=ExHkKL7c; 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="ExHkKL7c" Received: by smtp.kernel.org (Postfix) with ESMTPSA id E154C1F000E9; Sat, 15 Aug 2026 06:10:39 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1786774240; bh=y/849AO2sddeHW8MrWX3/Qfu86ZBAexBU+Si8+AEQWU=; h=From:To:Cc:Subject:Date:Reply-To; b=ExHkKL7cCFXCGDX+soZr8wGFSpJd6ERUrURkSPHSUGKV9T5Pcm2FO9NOvFUKft7Nx EXrsLLAtfCh3qT5wgbZ62P1j2CbrdxoE2VMAuR7lx+266xueNqLzcD0rf+qf1siz3B 1bRrC1HinVsgqWfx5sircs9aNvasa+KFPtY8IdHY= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-72047: ieee802154: ca8210: fix pointer truncation in kfifo on 64-bit Date: Sat, 15 Aug 2026 15:02:06 +0900 Message-ID: <2026081514-CVE-2026-72047-64f9@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=4212; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=qEG320mrHwtF7fhBCXd30cDVfeHSduxb9+Ykw8SOPKg=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkNDKt23eE8JTVh+peJsz9H5X5hV6zdVPjo/PTmQOulk TfTyyzcO2JZGASZGGTFFFm+bOM5ur/ikKKXoe1pmDmsTCBDGLg4BWAiD6wYFlzM2J/4+FZ14YyT J/S2rREMkLPf/pRhftrvuTNTW9bsXGLXumL3jHcr9Cfe6gEA 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: ieee802154: ca8210: fix pointer truncation in kfifo on 64-bit ca8210_test_int_driver_write() and ca8210_test_int_user_read() exchange a kmalloc'd buffer pointer through a struct kfifo, but pass a literal '4' as the byte count to kfifo_in()/kfifo_out(). This is correct on 32-bit (pointer = 4 bytes), but on 64-bit only the low 4 bytes of the 8-byte pointer are written into the FIFO. The reader then reads back 4 bytes into an 8-byte local pointer variable, leaving the upper 4 bytes uninitialized stack data. The first dereference of the reconstructed pointer (fifo_buffer[1]) accesses an arbitrary kernel address and generally results in an oops. Use sizeof(fifo_buffer) so the byte count matches pointer width on every architecture. The driver has no architecture restriction in Kconfig, so any 64-bit build with CONFIG_IEEE802154_CA8210_DEBUGFS=y is exposed. Issue has been latent since the driver was added in 2017 because it is most commonly deployed on 32-bit MCUs. Found via a custom Coccinelle semantic patch hunting for short-byte kfifo I/O on byte-mode kfifos used to shuttle pointers. The Linux kernel CVE team has assigned CVE-2026-72047 to this issue. Affected and fixed versions =========================== Issue introduced in 4.12 with commit ded845a781a578dfb0b5b2c138e5a067aa3b1242 and fixed in 5.10.261 with commit 2c1664ccfae653979b38788211240b5a1ee317ed Issue introduced in 4.12 with commit ded845a781a578dfb0b5b2c138e5a067aa3b1242 and fixed in 5.15.212 with commit 093aacb0c56d5c693e3169a0224062e77c3fd0c0 Issue introduced in 4.12 with commit ded845a781a578dfb0b5b2c138e5a067aa3b1242 and fixed in 6.1.178 with commit 87dab14a4f68895d6f4d798e6ee3556cd64e8c72 Issue introduced in 4.12 with commit ded845a781a578dfb0b5b2c138e5a067aa3b1242 and fixed in 6.6.145 with commit 1fe2643d0b24ca3cdd61a31a45c2d3233dc6cbfe Issue introduced in 4.12 with commit ded845a781a578dfb0b5b2c138e5a067aa3b1242 and fixed in 6.12.97 with commit 65dc342274a01616f5c17105f7360a3b4bfd7a3d Issue introduced in 4.12 with commit ded845a781a578dfb0b5b2c138e5a067aa3b1242 and fixed in 6.18.40 with commit 2059c28bd725beded01277cdf1f67be33e714323 Issue introduced in 4.12 with commit ded845a781a578dfb0b5b2c138e5a067aa3b1242 and fixed in 7.1.5 with commit d8ce67fa6a5e6929f5414e933ff9665176c2bce6 Issue introduced in 4.12 with commit ded845a781a578dfb0b5b2c138e5a067aa3b1242 and fixed in 7.2-rc1 with commit 6d7f7bcf225b2d566176bf6229dbd1252940cb3c 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-72047 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/net/ieee802154/ca8210.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/2c1664ccfae653979b38788211240b5a1ee317ed https://git.kernel.org/stable/c/093aacb0c56d5c693e3169a0224062e77c3fd0c0 https://git.kernel.org/stable/c/87dab14a4f68895d6f4d798e6ee3556cd64e8c72 https://git.kernel.org/stable/c/1fe2643d0b24ca3cdd61a31a45c2d3233dc6cbfe https://git.kernel.org/stable/c/65dc342274a01616f5c17105f7360a3b4bfd7a3d https://git.kernel.org/stable/c/2059c28bd725beded01277cdf1f67be33e714323 https://git.kernel.org/stable/c/d8ce67fa6a5e6929f5414e933ff9665176c2bce6 https://git.kernel.org/stable/c/6d7f7bcf225b2d566176bf6229dbd1252940cb3c