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 99E774E8DE4 for ; Fri, 4 Sep 2026 15:20:48 +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=1788535249; cv=none; b=j1e5FTzLETDnkRAehAfU0FbUutngDOS2gb05d5NO2iTjl0AgKjrzsuMeAUJQSSWn5ziCSLDW8eCXoO25Ji2FKL66wsQ7Oi8j14YUHHfKu7/mDF6hzL7+cHR25Gwmk53XO8I5W6Ocf3ZZZ3kokEAu5zqLc51p1/982uHcZoDWB/4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788535249; c=relaxed/simple; bh=LuZBB1P6N1Awiq9GIMNfz5L2jAkf/3bkuUD+a/99iH4=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=ZuZpfGneUGx5xt1zBQA9SxGaPHbIlrZbgvnIthUJgEOVDr0T7gZcEg/MO4KWCYpk6TN3knvY/XQifKaZ5QD+7P8zR7odML3KZ+y6ynDoomPl7L0REVHLYhQbY7jH0bl+Hz+UXtGtxyNIKiJ10xGisRsa7vBOzSoCTeiwMdAJyVo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=gxts+zVz; 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="gxts+zVz" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 96F221F00A3D; Fri, 4 Sep 2026 15:20:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1788535248; bh=C6tLMVYg+hjDmG30u5FedCMJ5+qQoo72QdyhlpSieVg=; h=From:To:Cc:Subject:Date:Reply-To; b=gxts+zVzJOvVd0tgI4jW9yS66vFUcqsQ2mKLyYVjUjRnAu3xloq+Z++bMUNjO1Izd BxM8KEx6UvtCHQ8I7C+82+iBCq8hPjEjqGv3TdaJTB8FoFtIXNEpZM3MhrdQ+7KI8T tpkC241o6hnFYqCxtIcmjGJm5Fw+pI6LZ7h2YOt4= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-80799: nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers Date: Fri, 4 Sep 2026 17:11:38 +0200 Message-ID: <2026090408-CVE-2026-80799-ac42@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=4593; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=VGw9QqjR6gJ68zzhJ2cZKt+LsV00iVBQFXNEV3Ysc5c=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmz7vfE+qxMFn6z6nk81zS/tG1Na3/scLGqDbzfyLH4w tVtf7xDOmJZGASZGGTFFFm+bOM5ur/ikKKXoe1pmDmsTCBDGLg4BWAis9gY5hfyhzfdmCtce+Tx 33LuiVvvr17mI84wP6tHx/XXrB339PWS5qvvvn/+Y/fKbgA= 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: nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers nfc_llcp_parse_gb_tlv() and nfc_llcp_parse_connection_tlv() contain three related bugs in their TLV parsing loops: 1. 'offset' is declared u8 but tlv_array_len is u16. When TLV data advances offset past 255 it silently wraps to zero, causing infinite loops or double-processing of buffer data. 2. Before reading tlv[0] (type) and tlv[1] (length) there is no check that offset+2 <= tlv_array_len. A truncated TLV causes an OOB read of one byte past the buffer end. 3. After reading the length field, the value bytes are accessed without checking offset+2+length <= tlv_array_len. A crafted length=0xFF on a short buffer causes up to 255 bytes of OOB read past the buffer end. Both functions are reachable without authentication via nfc_llcp_set_remote_gb() which feeds remote LLCP general bytes directly into nfc_llcp_parse_gb_tlv() with no additional validation. Fix all three issues by widening offset from u8 to u16 and adding bounds checks for both the TLV header and value field before each access. The Linux kernel CVE team has assigned CVE-2026-80799 to this issue. Affected and fixed versions =========================== Issue introduced in 5.10.188 with commit 0be9de2ea01e8d52646e7310a7eef5459cf07ea8 and fixed in 5.10.267 with commit 2c1456fe09ab1a5a9fe1d8339ca6d509589b56e1 Issue introduced in 5.15 with commit 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 and fixed in 5.15.218 with commit 7f6f3d087c67a4346189ef2c36481455bbc59a74 Issue introduced in 5.15 with commit 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 and fixed in 6.1.185 with commit 9c47d667963542c3cf8e3007b7f10c0904d08238 Issue introduced in 5.15 with commit 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 and fixed in 6.6.154 with commit a209334ed929941b20810c17c3a507445b0a7c85 Issue introduced in 5.15 with commit 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 and fixed in 6.12.106 with commit 382eaa770335acf4f16a5a55524500f2bb4207df Issue introduced in 5.15 with commit 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 and fixed in 6.18.47 with commit 2d239590d1845a706304833d40dd6d4fec20ad88 Issue introduced in 5.15 with commit 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 and fixed in 7.1.11 with commit e84cdfdc4a6c88e8b751144458f2e04e24415a28 Issue introduced in 5.15 with commit 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 and fixed in 7.2.1 with commit 875285a165fd3b402de2ab3be0deb355d6f4caf5 Issue introduced in 5.15 with commit 3df40eb3a2ea58bf404a38f15a7a2768e4762cb0 and fixed in 7.3-rc1 with commit 78b20c8eeacd2e44a2d8a4cb5316d3c521d90911 Issue introduced in 4.19.291 with commit 1deacb5e031e289ca5636f2db4fcae6612c05d34 Issue introduced in 5.4.251 with commit 66a1be74230bbe098e651766c9a0cf4038db8442 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-80799 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: net/nfc/llcp_commands.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/2c1456fe09ab1a5a9fe1d8339ca6d509589b56e1 https://git.kernel.org/stable/c/7f6f3d087c67a4346189ef2c36481455bbc59a74 https://git.kernel.org/stable/c/9c47d667963542c3cf8e3007b7f10c0904d08238 https://git.kernel.org/stable/c/a209334ed929941b20810c17c3a507445b0a7c85 https://git.kernel.org/stable/c/382eaa770335acf4f16a5a55524500f2bb4207df https://git.kernel.org/stable/c/2d239590d1845a706304833d40dd6d4fec20ad88 https://git.kernel.org/stable/c/e84cdfdc4a6c88e8b751144458f2e04e24415a28 https://git.kernel.org/stable/c/875285a165fd3b402de2ab3be0deb355d6f4caf5 https://git.kernel.org/stable/c/78b20c8eeacd2e44a2d8a4cb5316d3c521d90911