CVE-2026-80559 Input: sur40 - fix input device registration ordering

High 7.8 Published Updated

A race condition in the Linux kernel sur40 driver allows a local attacker to cause a system crash by accessing uninitialized memory during device registration.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-80559?

CVE-2026-80559 is a high-severity vulnerability in Linux, published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official 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.

Which versions are affected by CVE-2026-80559?

How do I fix CVE-2026-80559?

Apply the vendor's patch.

Is CVE-2026-80559 being exploited?

There is no known exploitation of CVE-2026-80559 in the wild and no public exploit code.

Sources

Also known as AZL-97836, BELL-CVE-2026-80559, DEBIAN-CVE-2026-80559, GHSA-7345-535v-r8v7, UBUNTU-CVE-2026-80559.

Is CVE-2026-80559 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free