Unknown

CVE-2026-80766 — HID: uclogic: fix use-after-free of inrange_timer on remove

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.

Published Sep 4, 2026 · Updated Oct 19, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+1

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.18%

ahead of 7% of scored CVEs · Oct 26, 2026

Affects

Linux

CVSS base

—

Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	≥ 01309e29eb95c16bd48984f2589fad0cbf5e27d1 and < f40243358b407aec362fe305fabfcdc94a3abd89≥ 01309e29eb95c16bd48984f2589fad0cbf5e27d1 and < dc5108f18f58870a8dd4203a02a47e571a2be7f0≥ 01309e29eb95c16bd48984f2589fad0cbf5e27d1 and < 9d77ac82e57ead056cf3f71d347083ed9244ad90≥ 01309e29eb95c16bd48984f2589fad0cbf5e27d1 and < e750cdb6de009aace3c77f37fe2173f96175e8e4≥ 01309e29eb95c16bd48984f2589fad0cbf5e27d1 and < 849e537160bbb77fe419ecc3944bfe125dcd441b≥ 01309e29eb95c16bd48984f2589fad0cbf5e27d1 and < f1b3ca06380531f49f988f4721d3ed30b0d7a5d2≥ 01309e29eb95c16bd48984f2589fad0cbf5e27d1 and < f13d0a00204b05e62336da0ab72ea0d87b56690c≥ 01309e29eb95c16bd48984f2589fad0cbf5e27d1 and < 506fd50a9027340f0e9dcc587d10ccb03312dba6 and 1 more version 5.1	Vulnerable	CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 15, 2026 → Oct 26, 2026 · 11 reading(s) · max 0.18%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Not enough vector or weakness data: use the affected application’s logs as a starting point.

application logs

Timeline

What happened to this CVE, newest first.

2026
Record published
Oct 15, 2026
Affected products added · linux/linux
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Sep 4, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 19, 2026 – Oct 19, 2026
1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

10 on the record

git.kernel.org/stable/c/f13d0a00204b05e62336da0ab72ea0d87b56690c
NIST National Vulnerability Database
git.kernel.org/stable/c/849e537160bbb77fe419ecc3944bfe125dcd441b
NIST National Vulnerability Database
git.kernel.org/stable/c/9d77ac82e57ead056cf3f71d347083ed9244ad90
NIST National Vulnerability Database
git.kernel.org/stable/c/f1b3ca06380531f49f988f4721d3ed30b0d7a5d2
NIST National Vulnerability Database
git.kernel.org/stable/c/f40243358b407aec362fe305fabfcdc94a3abd89
NIST National Vulnerability Database
git.kernel.org/stable/c/506fd50a9027340f0e9dcc587d10ccb03312dba6
NIST National Vulnerability Database
git.kernel.org/stable/c/dc5108f18f58870a8dd4203a02a47e571a2be7f0
NIST National Vulnerability Database
git.kernel.org/stable/c/e750cdb6de009aace3c77f37fe2173f96175e8e4
NIST National Vulnerability Database
github.com/advisories/GHSA-xc7g-5f4m-53h6
GitHub Security Advisories
nvd.nist.gov/vuln/detail/CVE-2026-80766
GitHub Security Advisories

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Unknown CVE-2026-99092 riscv: patch: fix handling of bpf-jit execmem addresses 17h
Unknown CVE-2026-99093 mm: don't schedule deferred kernel page table freeing while booting 17h
Unknown CVE-2026-99095 drm/vc4: drain the hangcheck timer and works on V3D unbind 17h
Unknown CVE-2026-99096 io_uring/register: don't exempt disabled rings from task restrictions 17h
Unknown CVE-2026-99097 tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper() 17h
Unknown CVE-2026-99098 dm-integrity: fix buffer overflow in inline mode with large tag size 17h

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CVSS score published by NVD, the CNA, CISA or GitHub so far.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-80766 is "HID: uclogic: fix use-after-free of inrange_timer on remove", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.