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 0ED1755820F for ; Fri, 11 Sep 2026 19:48:53 +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=1789156154; cv=none; b=rYFw5TD+D6sKV9MVubzZv85b1DdBRt+htEZva+oQBuKcEKNZ8W6WocwmNEbG4bxJpAwAKF5zNe6Bc+z1iTZX8pAxK/gDvwDEWXtDU1maw1aLN2WFvcVMXfwOlPMJGyXGy+ZLh2g/sTiRiNvG02Z7AbU9ym6HW/cFHMiSat0wHJI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789156154; c=relaxed/simple; bh=OZcRrzyair82IbrR9m0ZF8Ikhp45IaIPhFMiQ0/kWlA=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=g0ALLvWduax7Tws0cZ73xuFYAZMIhUwouZxec2wVxY/8ofLVHrtu2kQl3bHzyiO+aUJdJFBue5hTBHLS/NvrXrfKLOnrODXuy5qM7wZ2b1UVevThZtMZr/A3tCdqWTRJcZB6MATzXkoZyz+JHtd/gn3M5bZ0udCagpSOOatNOh4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=MsRQYCMm; 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="MsRQYCMm" Received: by smtp.kernel.org (Postfix) with ESMTPSA id CF1FA1F00898; Fri, 11 Sep 2026 19:48:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789156133; bh=Xc+zaAT9cTWqxXQVTNG0+0EP2p/g/QPEg0+wby+8K78=; h=From:To:Cc:Subject:Date:Reply-To; b=MsRQYCMm+Jf7ZZWdAHOReA02seILmRCCTqH82cmOFTPUx/ZYJAVlPBWPJsESIQov7 /Y/26tgBVjSi5uVz0nFxdIFGFtphHox8+hw6jDFkV2D7dA0PdJ9f0aPqSMbKDgFawC IONMwAJ6Uo+pXy7HvRCa7iVjbqg+MCiva3JCMlxs= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-80999: net: dsa: realtek: use gpiod_set_value_cansleep for reset GPIO Date: Fri, 11 Sep 2026 21:41:45 +0200 Message-ID: <2026091150-CVE-2026-80999-a9cb@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=3978; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=KkaFo48FzIUleqf5JyyXz+DDt96l+ViE3u5/XlAraGc=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlLIp3yhAvPC23ck5PGZ7Iuhr9pSb3rkoaZazYcev9xP d/i05MkOmJZGASZGGTFFFm+bOM5ur/ikKKXoe1pmDmsTCBDGLg4BWAiV1wY5nDeF2w9+aFv8lJX +4wah0T519PmHGaYw+8fsWt6jEjc/ic8nF84YuODbHwdAA== 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: net: dsa: realtek: use gpiod_set_value_cansleep for reset GPIO rtl83xx_reset_assert() and rtl83xx_reset_deassert() are only called from the probe path, which may sleep and is not timing-critical. When the reset GPIO is provided by a sleeping controller such as an I2C I/O expander, gpiod_set_value() warns: WARNING: drivers/gpio/gpiolib.c:4030 at gpiod_set_value+0x44/0x80, CPU#1: kworker/u16:4/61 Hardware name: B&O MAP CA33 Rev f (UNKNOWN) (DT) Workqueue: events_unbound deferred_probe_work_func pc : gpiod_set_value+0x44/0x80 lr : rtl83xx_probe+0x1d8/0x3a0 Call trace: gpiod_set_value+0x44/0x80 (P) rtl83xx_probe+0x1d8/0x3a0 realtek_mdio_probe+0x24/0xa0 mdio_probe+0x38/0x78 really_probe+0xc4/0x3e0 __driver_probe_device+0x15c/0x1b8 driver_probe_device+0xb4/0x120 __device_attach_driver+0xb8/0x1a0 bus_for_each_drv+0x88/0xf0 __device_attach+0xa0/0x1d8 device_initial_probe+0x54/0x68 bus_probe_device+0x38/0xa0 deferred_probe_work_func+0xb8/0x120 process_one_work+0x184/0x4e8 worker_thread+0x188/0x308 kthread+0x130/0x150 ret_from_fork+0x10/0x20 Switch both helpers to gpiod_set_value_cansleep() so such a reset GPIO can be used without triggering the warning. The reset GPIO has been driven with the non-sleeping gpiod_set_value() since the driver was added in v4.19. The call has since been refactored across several files - from realtek-smi.c / realtek-mdio.c into the common rtl83xx.c module and then into the rtl83xx_reset_assert() and rtl83xx_reset_deassert() helpers (both in v6.9). This patch therefore applies as-is only to kernels that carry those helpers (v6.9+); older stable kernels need the same gpiod_set_value_cansleep() conversion at the corresponding open-coded call sites. The Linux kernel CVE team has assigned CVE-2026-80999 to this issue. Affected and fixed versions =========================== Issue introduced in 4.19 with commit d8652956cf37c5caa8c19e0b99ce5ca235c6d5de and fixed in 6.12.109 with commit c32cf5292a0dd70c4afc138b4dc45743a190cd5a Issue introduced in 4.19 with commit d8652956cf37c5caa8c19e0b99ce5ca235c6d5de and fixed in 6.18.50 with commit f71087e7c63aa3e99bf65d7ddf91eb4fd3545778 Issue introduced in 4.19 with commit d8652956cf37c5caa8c19e0b99ce5ca235c6d5de and fixed in 7.2.4 with commit 1610a8c2b93e815e3dc8643a2a69ab1c37975a6a Issue introduced in 4.19 with commit d8652956cf37c5caa8c19e0b99ce5ca235c6d5de and fixed in 7.3-rc1 with commit fb58b6a696b30bcbfbe0cfc0a91b19c816a955fc 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-80999 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/dsa/realtek/rtl83xx.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/c32cf5292a0dd70c4afc138b4dc45743a190cd5a https://git.kernel.org/stable/c/f71087e7c63aa3e99bf65d7ddf91eb4fd3545778 https://git.kernel.org/stable/c/1610a8c2b93e815e3dc8643a2a69ab1c37975a6a https://git.kernel.org/stable/c/fb58b6a696b30bcbfbe0cfc0a91b19c816a955fc