From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 19B16478875 for ; Wed, 13 May 2026 15:08:49 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778684930; cv=none; b=Qz09NXJy5lHezGPc0sBs72HB5smXfSdb2JjYdqeJbOntoxx8/A1na94Uz3ot/ygkF9YA3cudV+SWUXo8isGTXCuIH8lEfF6GqzYcQIrGE762dYpeCa0Y1o/u+fAf8kIIBVmx/qbxPfNancZppOTE5p65WBrN0eTJGiedcHcC068= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778684930; c=relaxed/simple; bh=XJnyLwY+oO/FSw6dmJQkuMDkE1nzIpvfD5NRTYC6pGk=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=YV1/Znj/YLniCVf5/uN/03JM6WzXk9UyPfvUsHYr3FON9sMd/LAp4aSCaHmz+tG6OpshOA8cDb7F5+RqpR7vLfebDKEwjYwsCD06JzLVSw5i79R7pWG/0kEcBEYNYfF5tstj/u4TiYxV+NAY9rP/I6Uk+nNrDQ1UYfKg06hBGUI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=vQhsI1cU; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="vQhsI1cU" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5140DC19425; Wed, 13 May 2026 15:08:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1778684929; bh=XJnyLwY+oO/FSw6dmJQkuMDkE1nzIpvfD5NRTYC6pGk=; h=From:To:Cc:Subject:Date:Reply-To:From; b=vQhsI1cU6qsNgQl2cKjEwxZahLBE9J0isL1XUh6oudlu3FMMhaypnFKtXgrF/mp76 nk/NBYDoOSpQdUF4zgXUAIJyY1DSRersGJDQEgFes78ZEYCq8BYYu3ms/IflQtYFX+ edJUv45NuWFQeFdEfk9mvJhLj5PyWYOtFHLSJCAg= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-43476: iio: chemical: sps30_i2c: fix buffer size in sps30_i2c_read_meas() Date: Wed, 13 May 2026 17:08:44 +0200 Message-ID: <2026051344-CVE-2026-43476-0f4f@gregkh> X-Mailer: git-send-email 2.54.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=3105; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=Kwo/EYNT2+5c2bV841kIBnkFOqU08AEAA4TL3jlFf3k=; b=owGbwMvMwCRo6H6F97bub03G02pJDFksk/8qpFzRX9pUOrGiiovFkCHeo5tVYMo9nwyli7MOi bQ4q13viGVhEGRikBVTZPmyjefo/opDil6Gtqdh5rAygQxh4OIUgInYr2WYX920+87DUAEZzbci Fjav1t8L2eazh2HBzOZrb0yFiqXWBLvmZLyx+OmkabMNAA== 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: iio: chemical: sps30_i2c: fix buffer size in sps30_i2c_read_meas() sizeof(num) evaluates to sizeof(size_t) (8 bytes on 64-bit) instead of the intended __be32 element size (4 bytes). Use sizeof(*meas) to correctly match the buffer element type. The Linux kernel CVE team has assigned CVE-2026-43476 to this issue. Affected and fixed versions =========================== Issue introduced in 5.14 with commit 8f3f130852785dac0759843835ca97c3bacc2b10 and fixed in 5.15.203 with commit 9aff2e9c2927ecd9652872a43a0725f101128104 Issue introduced in 5.14 with commit 8f3f130852785dac0759843835ca97c3bacc2b10 and fixed in 6.1.167 with commit 08881d82f94deaa51800360029908863e5c4c39d Issue introduced in 5.14 with commit 8f3f130852785dac0759843835ca97c3bacc2b10 and fixed in 6.6.130 with commit dcdf1e92674efb6692f4ebe189e0aa9fde23a541 Issue introduced in 5.14 with commit 8f3f130852785dac0759843835ca97c3bacc2b10 and fixed in 6.12.78 with commit 2a4d111a6a34afb8bb4f118009e7728ed2ec7e10 Issue introduced in 5.14 with commit 8f3f130852785dac0759843835ca97c3bacc2b10 and fixed in 6.18.19 with commit 90e978ace598567e6e30de79805bddf37cf892ac Issue introduced in 5.14 with commit 8f3f130852785dac0759843835ca97c3bacc2b10 and fixed in 6.19.9 with commit 165f12b40901c6a7aca15796da239726ddcdc5ad Issue introduced in 5.14 with commit 8f3f130852785dac0759843835ca97c3bacc2b10 and fixed in 7.0 with commit 216345f98cae7fcc84f49728c67478ac00321c87 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-43476 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/iio/chemical/sps30_i2c.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/9aff2e9c2927ecd9652872a43a0725f101128104 https://git.kernel.org/stable/c/08881d82f94deaa51800360029908863e5c4c39d https://git.kernel.org/stable/c/dcdf1e92674efb6692f4ebe189e0aa9fde23a541 https://git.kernel.org/stable/c/2a4d111a6a34afb8bb4f118009e7728ed2ec7e10 https://git.kernel.org/stable/c/90e978ace598567e6e30de79805bddf37cf892ac https://git.kernel.org/stable/c/165f12b40901c6a7aca15796da239726ddcdc5ad https://git.kernel.org/stable/c/216345f98cae7fcc84f49728c67478ac00321c87