CVE-2026-80559

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-27. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 26, 2026

Last Modified

August 27, 2026

Advisory Details (8)

Auto-updated Aug 27, 2026
No patch confirmed yet.
generic

Input: sur40 - fix input device registration ordering - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dab741c9da72102a37cc1020a929051b7c45f9fb
generic

Input: sur40 - fix input device registration ordering - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cd4ecce2fd87760c0ad9a9d28c9fc62ea1dbfd3d
generic

Input: sur40 - fix input device registration ordering - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/beb9b0bd6e6e23f5e9e42b7ef890a50f57f1f3aa
generic

Input: sur40 - fix input device registration ordering - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9da976eb649c9e2f588a4499410e4d8af687925f
generic

Input: sur40 - fix input device registration ordering - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/83aa12f9f2468a4fbef027c09224dc1011850fb0
generic

Input: sur40 - fix input device registration ordering - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/764b507be7b51787e1f577ca3bf0bab7efe81ff8
generic

Input: sur40 - fix input device registration ordering - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5c1c5227c93f18cd329dd754b4df5e0e2daece1e
generic

Input: sur40 - fix input device registration ordering - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3e8ed76a4f3572e637653f0654cccdf617903231

Vendor Advisories for CVE-2026-80559(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 16× in last 7d / 16× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:36 UTCEG score recompute
  2. 2026-08-30 01:36 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 12:47 UTCGHSA enrichment
  5. 2026-08-28 23:57 UTCEG score recompute
  6. 2026-08-28 23:57 UTCGHSA enrichment
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-28 07:59 UTCGHSA enrichment
  9. 2026-08-27 19:08 UTCEG score recompute
  10. 2026-08-27 19:07 UTCGHSA enrichment
  11. 2026-08-27 14:25 UTCEPSS rescore
  12. 2026-08-27 06:19 UTCEG score recompute 7.80
  13. 2026-08-27 06:11 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  14. 2026-08-26 15:43 UTCNVD update
  15. 2026-08-26 14:42 UTCEG score recompute
  16. 2026-08-26 14:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80559?
CVE-2026-80559 is a high vulnerability published on August 26, 2026. In the Linux kernel, the following vulnerability has been resolved: Input: sur40 - fix input device registration ordering In sur40probe(), inputregister_device() was previously called early before the V4L2 video device and vb2_queue components were fully initialized. If userspace opened the input…
When was CVE-2026-80559 disclosed?
CVE-2026-80559 was first published in the National Vulnerability Database on August 26, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80559 actively exploited?
CVE-2026-80559 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-80559?
CVE-2026-80559 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-80559?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80559, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-80559

Explore →

Is Your Infrastructure Affected by CVE-2026-80559?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.