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 601F93ED3CF for ; Fri, 4 Sep 2026 15:17:10 +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=1788535031; cv=none; b=OyMy2gfjUYOixb5ntJ1Quf+NRknNOqzAcG0hwV1Js+9d1NHkxobgVLm4/Sjr+Rr77l/Xw1KkFXHNTCEk/I5qX/Keb9UguYTS3ZnO42/NQoH/nBA0Gs5B9GRsWMwmoQ7HSYlKFgVYth4lmanDQcTT/BZesCYiElwTKeJICs7SNW4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788535031; c=relaxed/simple; bh=4HpW/F65F6wMIhrR5Z2LgnUek4kzB/ICrevPkzkAuw0=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=kr06eFrmi3ZqoZvIChSJG1hMCV4k0wduZrG3XTKbDzQs+Zfj9FY9FxAqX94LCQJrfOl7yIcnVZNWvUK7r9CNxxkj+2nVOdDmU4cjSfqMC1DKREsw5VesXjt3OifcBiocLsXWndUvvow/OqMjf3Jxt5DgjtgooE9leNnic6EIgiM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=pRxI7tHC; 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="pRxI7tHC" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7EAE81F00A3D; Fri, 4 Sep 2026 15:17:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1788535030; bh=hC1wV/TD2ADP39MEQahYps82RndYjum/94JKE0KKKPk=; h=From:To:Cc:Subject:Date:Reply-To; b=pRxI7tHCG3rVT21rCIcx80P3rdy3JLr42mwEaH5Rvr/ItzyA46vx42eZmGcPHQK3D DaKBlkWlrtXvaB21rLeMfo2XlyTAEmOaVls6RcwTDXN0byyjevnOJMAtz5Z9lGQhQM Q5QyOGDPv0g1Gpynwgc3NlY9GsjP2AwP7Cw9EKP0= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-80766: HID: uclogic: fix use-after-free of inrange_timer on remove Date: Fri, 4 Sep 2026 17:11:05 +0200 Message-ID: <2026090400-CVE-2026-80766-b157@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=4778; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=YgdahcoC+KvdsOoTeRRWwW3dwK40OqzD2jX+3eA+OjM=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmz7rc8/B6Q5ThrIsv5jXsuGh052tx1z3vzUsaCFa82W W95pJoj0BHLwiDIxCArpsjyZRvP0f0VhxS9DG1Pw8xhZQIZwsDFKQATmXWKYcGBb0s3ZcasWVNW MPXnVbPP7eUNCbkMc8X45iXsmbnH91b8Bz7PQwz36pf9XQEA 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: HID: uclogic: fix use-after-free of inrange_timer on remove uclogic_remove() cancels the pen in-range timer and then stops the device: timer_delete_sync(&drvdata->inrange_timer); hid_hw_stop(hdev); timer_delete_sync() only guarantees the timer is idle at that instant. uclogic_raw_event_pen() keeps delivering pen reports until hid_hw_stop() stops the transport several lines later, and every report with pen->inrange == UCLOGIC_PARAMS_PEN_INRANGE_NONE re-arms the timer: mod_timer(&drvdata->inrange_timer, jiffies + msecs_to_jiffies(100)); A report landing between the timer_delete_sync() call and the transport teardown in hid_hw_stop() re-arms inrange_timer after it was cancelled. uclogic_remove() then returns and the devm drvdata is freed, while hid_hw_stop() has already freed the input device drvdata->pen_input points at, so when the timer fires ~100 ms later uclogic_inrange_timeout() dereferences freed memory -- a use-after-free in timer-softirq context. Swapping the two calls is not a fix: stopping the device first frees drvdata->pen_input via hidinput_disconnect() while the timer may still be pending, so a timer already armed before removal fires on the freed input device in the window before timer_delete_sync() runs. Use timer_shutdown_sync() before hid_hw_stop() instead. It cancels the timer, waits for a running callback while pen_input is still valid, and prevents any further re-arming -- a later mod_timer() from an in-flight report is silently ignored -- so the timer is provably dead before hid_hw_stop() frees the inputs. This is the ordering the timer core documents for this "timer re-armed from another path" teardown case. The Linux kernel CVE team has assigned CVE-2026-80766 to this issue. Affected and fixed versions =========================== Issue introduced in 5.1 with commit 01309e29eb95c16bd48984f2589fad0cbf5e27d1 and fixed in 5.15.220 with commit f40243358b407aec362fe305fabfcdc94a3abd89 Issue introduced in 5.1 with commit 01309e29eb95c16bd48984f2589fad0cbf5e27d1 and fixed in 6.1.187 with commit dc5108f18f58870a8dd4203a02a47e571a2be7f0 Issue introduced in 5.1 with commit 01309e29eb95c16bd48984f2589fad0cbf5e27d1 and fixed in 6.6.156 with commit 9d77ac82e57ead056cf3f71d347083ed9244ad90 Issue introduced in 5.1 with commit 01309e29eb95c16bd48984f2589fad0cbf5e27d1 and fixed in 6.12.108 with commit e750cdb6de009aace3c77f37fe2173f96175e8e4 Issue introduced in 5.1 with commit 01309e29eb95c16bd48984f2589fad0cbf5e27d1 and fixed in 6.18.47 with commit 849e537160bbb77fe419ecc3944bfe125dcd441b Issue introduced in 5.1 with commit 01309e29eb95c16bd48984f2589fad0cbf5e27d1 and fixed in 7.1.11 with commit f1b3ca06380531f49f988f4721d3ed30b0d7a5d2 Issue introduced in 5.1 with commit 01309e29eb95c16bd48984f2589fad0cbf5e27d1 and fixed in 7.2.1 with commit f13d0a00204b05e62336da0ab72ea0d87b56690c Issue introduced in 5.1 with commit 01309e29eb95c16bd48984f2589fad0cbf5e27d1 and fixed in 7.3-rc1 with commit 506fd50a9027340f0e9dcc587d10ccb03312dba6 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-80766 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/hid/hid-uclogic-core.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/f40243358b407aec362fe305fabfcdc94a3abd89 https://git.kernel.org/stable/c/dc5108f18f58870a8dd4203a02a47e571a2be7f0 https://git.kernel.org/stable/c/9d77ac82e57ead056cf3f71d347083ed9244ad90 https://git.kernel.org/stable/c/e750cdb6de009aace3c77f37fe2173f96175e8e4 https://git.kernel.org/stable/c/849e537160bbb77fe419ecc3944bfe125dcd441b https://git.kernel.org/stable/c/f1b3ca06380531f49f988f4721d3ed30b0d7a5d2 https://git.kernel.org/stable/c/f13d0a00204b05e62336da0ab72ea0d87b56690c https://git.kernel.org/stable/c/506fd50a9027340f0e9dcc587d10ccb03312dba6