Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-80567: Input: synaptics-rmi4 - propagate F54 worker errors to V4L2 queue

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Fixed version: Linux Linux 2b0403fb7e28f65883cd03814b62c9aa9bc7f04d, 305c24ee25b6e08ac9f4c5f697e823cc638c38da, 6741a8c21d98088b7f2d9f4f86a706d311ce34a2; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 2b0403fb7e28f65883cd03814b62c9aa9bc7f04d, 305c24ee25b6e08ac9f4c5f697e823cc638c38da, 6741a8c21d98088b7f2d9f4f86a706d311ce34a2; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Aug 26, 2026
Updated
Aug 26, 2026
EPSS
0.1% · 5th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-80567

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.9affected
    • 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and later · before 305c24ee25b6e08ac9f4c5f697e823cc638c38daaffected · git
    • 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and later · before 7d33b752e0df385b285492b74699fc73b6becdfbaffected · git
    • 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and later · before be56730b547737151f24357d832b04aaa93755d5affected · git
    • 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and later · before 2b0403fb7e28f65883cd03814b62c9aa9bc7f04daffected · git
    • 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and later · before 6741a8c21d98088b7f2d9f4f86a706d311ce34a2affected · git
    • 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and later · before 70f9aad3943559af6f32cb303744f35c05ce9cf1affected · git
    • 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and later · before 9bbd3682f8a3e064271547133c37fcb17668d860affected · git
    • 3a762dbd5347514c3cb2ac756a92a3d1c7646a2d and later · before 8786d74bf50e6797b6f655eb381ef6b25451161faffected · git
    • before 4.9not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.187-16.1.187-1
Debian:12linux-6.12before 6.12.107-1~deb12u16.12.107-1~deb12u1
Debian:13linuxbefore 6.12.105-16.12.105-1
Debian:14linuxbefore 7.1.10-17.1.10-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-80565Aug 26, 2026 · crypto: qce - fix error path in devm_qce_register_algs
    31Monitor
  • ← EarlierCVE-2026-80566Aug 26, 2026 · Input: hynitron_cstxxx - validate touch count and finger IDs
    0Monitor
  • Later →CVE-2026-80568Aug 26, 2026 · Input: synaptics-rmi4 - block s_input when F54 queue is busy
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux2b0403fb7e28f65883cd03814b62c9aa9bc7f04dVendor (CNA)
Linux Linux305c24ee25b6e08ac9f4c5f697e823cc638c38daVendor (CNA)
Linux Linux6741a8c21d98088b7f2d9f4f86a706d311ce34a2Vendor (CNA)
Linux Linux70f9aad3943559af6f32cb303744f35c05ce9cf1Vendor (CNA)
Linux Linux7d33b752e0df385b285492b74699fc73b6becdfbVendor (CNA)
Linux Linux8786d74bf50e6797b6f655eb381ef6b25451161fVendor (CNA)
Linux Linux9bbd3682f8a3e064271547133c37fcb17668d860Vendor (CNA)
Linux Linuxbe56730b547737151f24357d832b04aaa93755d5Vendor (CNA)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.06.6.157.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.107-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records