CVE-2026-80559

Input: sur40 - fix input device registration ordering

HIGH
7.8
CVSS Score
Published: August 26, 2026 at 02:37 PM UTC
Updated: August 27, 2026 at 06:30 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: Input: sur40 - fix input device registration ordering In sur40_probe(), input_register_device() was previously called early before the V4L2 video device and vb2_queue components were fully initialized. If userspace opened the input device immediately upon registration, sur40_open() would trigger and start the sur40_poll() worker thread. This worker thread invokes sur40_process_video() and accesses the uninitialized vb2_queue structure, leading to a data race and potential system crash. Furthermore, if V4L2 or video registration failed after input_register_device() succeeded, the error path fell through to calling input_free_device() on a successfully registered device instead of input_unregister_device(), corrupting input core state. Move input_register_device() to the very end of sur40_probe(). This ensures the V4L2 and video queue structures are fully initialized before polling can start, and naturally resolves the error path bug since input_free_device() is now only called when input registration has not yet occurred. To maintain strict LIFO (Last-In, First-Out) teardown ordering, also move input_unregister_device() to the very beginning of sur40_disconnect(). This guarantees that the input polling worker thread is stopped before V4L2 video components or control handlers are unregistered.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.1 ≤ v < 5.10.2664.1 ≤ v < 5.15.2174.1 ≤ v < 6.1.1844.1 ≤ v < 6.12.1054.1 ≤ v < 6.18.464.1 ≤ v < 6.6.1534.1 ≤ v < 7.1.104.1 ≤ v < 7.24.1e831cd251fb91d6c25352d322743db0d17ea11dd
Vendor states this is fixed in 3e8ed76a4f3572e637653f0654cccdf617903231 (fixed)
Vendor states this is fixed in 5c1c5227c93f18cd329dd754b4df5e0e2daece1e (fixed)
Vendor states this is fixed in 764b507be7b51787e1f577ca3bf0bab7efe81ff8 (fixed)
Vendor states this is fixed in 83aa12f9f2468a4fbef027c09224dc1011850fb0 (fixed)
Vendor states this is fixed in 9da976eb649c9e2f588a4499410e4d8af687925f (fixed)
Vendor states this is fixed in beb9b0bd6e6e23f5e9e42b7ef890a50f57f1f3aa (fixed)
Vendor states this is fixed in cd4ecce2fd87760c0ad9a9d28c9fc62ea1dbfd3d (fixed)
Vendor states this is fixed in dab741c9da72102a37cc1020a929051b7c45f9fb (fixed)
Vendor states this is fixed in 4.1 (unaffected)
Vendor states this is fixed in 5.10.266 (unaffected)
Vendor states this is fixed in 5.15.217 (unaffected)
Vendor states this is fixed in 6.1.184 (unaffected)
Vendor states this is fixed in 6.12.105 (unaffected)
Vendor states this is fixed in 6.18.46 (unaffected)
Vendor states this is fixed in 6.6.153 (unaffected)
Vendor states this is fixed in 7.1.10 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card