Input: byd - synchronize timer deletion before freeing private data
Summary
| CVE | CVE-2026-80572 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-26 15:17:13 UTC |
| Updated | 2026-08-27 13:18:40 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: Input: byd - synchronize timer deletion before freeing private data byd_disconnect() uses timer_delete() before freeing the driver's private data. This does not wait for a running byd_clear_touch() callback, which dereferences the private data and its psmouse pointer. A callback racing with disconnect can therefore access the private data after it has been freed. The timer can also still be re-armed by byd_process_byte() while the disconnect is in progress. Use timer_shutdown_sync() before freeing the private data: it waits for a running callback and turns any later re-arm attempt into a no-op. |
Risk And Classification
Primary CVSS: v3.1 7.8 HIGH from 416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | Secondary | 7.8 | HIGH | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| 3.1 | CNA | DECLARED | 7.8 | HIGH | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
LowPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
HighIntegrity
HighAvailability
HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 2d5f5611dd0de52e9a52b56391a7049a52184e72 84b205297fa15f97510342221d8c9a0119711478 git | Not specified |
| CNA | Linux | Linux | affected 2d5f5611dd0de52e9a52b56391a7049a52184e72 28d984a66b9e14be74986167b6ad40b5e0daf19a git | Not specified |
| CNA | Linux | Linux | affected 2d5f5611dd0de52e9a52b56391a7049a52184e72 ee944a706a18322b4a2599eebe8040a2994e928f git | Not specified |
| CNA | Linux | Linux | affected 2d5f5611dd0de52e9a52b56391a7049a52184e72 8dbfd8e32a13e116790780ed0be82b5a05eb9916 git | Not specified |
| CNA | Linux | Linux | affected 2d5f5611dd0de52e9a52b56391a7049a52184e72 2e509ef60ee41a2da0deb062c262bb530143fb37 git | Not specified |
| CNA | Linux | Linux | affected 2d5f5611dd0de52e9a52b56391a7049a52184e72 c83e79c0842ed29860648bcce5022ef0ba5001c6 git | Not specified |
| CNA | Linux | Linux | affected 4.6 | Not specified |
| CNA | Linux | Linux | unaffected 4.6 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.185 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.154 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.106 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.46 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1.10 7.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/84b205297fa15f97510342221d8c9a0119711478 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/c83e79c0842ed29860648bcce5022ef0ba5001c6 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/2e509ef60ee41a2da0deb062c262bb530143fb37 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/28d984a66b9e14be74986167b6ad40b5e0daf19a | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/8dbfd8e32a13e116790780ed0be82b5a05eb9916 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/ee944a706a18322b4a2599eebe8040a2994e928f | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.