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-80567Input: synaptics-rmi4 - propagate F54 worker errors to V4L2 queue

Description

In the Linux kernel, the following vulnerability has been resolved: Input: synaptics-rmi4 - propagate F54 worker errors to V4L2 queue Previously, rmi_f54_buffer_queue() waited for the worker thread to finish but ignored whether it succeeded. If the worker failed (e.g., due to a timeout or register read failure), the queue thread would silently return success, delivering stale or uninitialized memory to userspace. Add a 'report_error' field to struct f54_data to store the worker's exit status. Check this field in rmi_f54_buffer_queue() after the worker finishes, and mark the buffer as VB2_BUF_STATE_ERROR if an error occurred.

Timeline

  1. ID reserved

    By Linux

  2. Published

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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d – < 305c24ee25b6e08ac9f4c5f697e823cc638c38da
    • affected 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d – < 7d33b752e0df385b285492b74699fc73b6becdfb
    • affected 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d – < be56730b547737151f24357d832b04aaa93755d5
    • affected 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d – < 2b0403fb7e28f65883cd03814b62c9aa9bc7f04d
    • affected 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d – < 6741a8c21d98088b7f2d9f4f86a706d311ce34a2
    • affected 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d – < 70f9aad3943559af6f32cb303744f35c05ce9cf1
    • affected 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d – < 9bbd3682f8a3e064271547133c37fcb17668d860
    • affected 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d – < 8786d74bf50e6797b6f655eb381ef6b25451161f
  • Linux · Linux

    • affected 4.9
    • unaffected < 4.9
    • 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-80567 badge
[![CVE-2026-80567](https://cveledger.app/badge/CVE-2026-80567.svg)](https://cveledger.app/cve/CVE-2026-80567)

Record last updated .