CVE-2026-80559

Input: sur40 - fix input device registration ordering

State
Published
Severity
7.8 High
Published
Aug 26, 2026
Updated
Aug 27, 2026
Reserved
Aug 26, 2026

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.17.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • e831cd251fb91d6c25352d322743db0d17ea11dd to before cd4ecce2fd87760c0ad9a9d28c9fc62ea1dbfd3dAffected
  • e831cd251fb91d6c25352d322743db0d17ea11dd to before dab741c9da72102a37cc1020a929051b7c45f9fbAffected
  • e831cd251fb91d6c25352d322743db0d17ea11dd to before 764b507be7b51787e1f577ca3bf0bab7efe81ff8Affected
  • e831cd251fb91d6c25352d322743db0d17ea11dd to before 3e8ed76a4f3572e637653f0654cccdf617903231Affected
  • e831cd251fb91d6c25352d322743db0d17ea11dd to before 83aa12f9f2468a4fbef027c09224dc1011850fb0Affected
  • e831cd251fb91d6c25352d322743db0d17ea11dd to before 5c1c5227c93f18cd329dd754b4df5e0e2daece1eAffected
  • e831cd251fb91d6c25352d322743db0d17ea11dd to before beb9b0bd6e6e23f5e9e42b7ef890a50f57f1f3aaAffected
  • e831cd251fb91d6c25352d322743db0d17ea11dd to before 9da976eb649c9e2f588a4499410e4d8af687925fAffected
LinuxLinux
  • 4.1Affected
  • before 4.1Not affected
  • 5.10.266 through 5.10.*Not affected
  • 5.15.217 through 5.15.*Not affected
  • 6.1.184 through 6.1.*Not affected
  • 6.6.153 through 6.6.*Not affected
  • 6.12.105 through 6.12.*Not affected
  • 6.18.46 through 6.18.*Not affected
  • 7.1.10 through 7.1.*Not affected
  • 7.2 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.