Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 1 day later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-80559, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected e831cd251fb91d6c25352d322743db0d17ea11dd – < cd4ecce2fd87760c0ad9a9d28c9fc62ea1dbfd3d
    • affected e831cd251fb91d6c25352d322743db0d17ea11dd – < dab741c9da72102a37cc1020a929051b7c45f9fb
    • affected e831cd251fb91d6c25352d322743db0d17ea11dd – < 764b507be7b51787e1f577ca3bf0bab7efe81ff8
    • affected e831cd251fb91d6c25352d322743db0d17ea11dd – < 3e8ed76a4f3572e637653f0654cccdf617903231
    • affected e831cd251fb91d6c25352d322743db0d17ea11dd – < 83aa12f9f2468a4fbef027c09224dc1011850fb0
    • affected e831cd251fb91d6c25352d322743db0d17ea11dd – < 5c1c5227c93f18cd329dd754b4df5e0e2daece1e
    • affected e831cd251fb91d6c25352d322743db0d17ea11dd – < beb9b0bd6e6e23f5e9e42b7ef890a50f57f1f3aa
    • affected e831cd251fb91d6c25352d322743db0d17ea11dd – < 9da976eb649c9e2f588a4499410e4d8af687925f
  • Linux · Linux

    • affected 4.1
    • unaffected < 4.1
    • unaffected 5.10.266 – ≤ 5.10.*
    • unaffected 5.15.217 – ≤ 5.15.*
    • unaffected 6.1.184 – ≤ 6.1.*
    • unaffected 6.6.153 – ≤ 6.6.*
    • unaffected 6.12.105 – ≤ 6.12.*
    • unaffected 6.18.46 – ≤ 6.18.*
    • unaffected 7.1.10 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80559 badge
[![CVE-2026-80559](https://cveledger.app/badge/CVE-2026-80559.svg)](https://cveledger.app/cve/CVE-2026-80559)

Record last updated .