Linux Kernel up to 7.1.9 synaptics-rmi4 rmi_f54_buffer_queue uninitialized pointer

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.1$0-$5k0.30+

Summaryinfo

A vulnerability labeled as problematic has been found in Linux Kernel up to 7.1.9. This vulnerability affects the function rmi_f54_buffer_queue of the component synaptics-rmi4. Executing a manipulation can lead to uninitialized pointer. This vulnerability is registered as CVE-2026-80567. The attack needs to be launched locally. No exploit is available.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 7.1.9 and classified as problematic. This vulnerability affects the function rmi_f54_buffer_queue of the component synaptics-rmi4. The manipulation with an unknown input leads to a uninitialized pointer vulnerability. The CWE definition for the vulnerability is CWE-824. The product accesses or uses a pointer that has not been initialized. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at git.kernel.org. This vulnerability was named CVE-2026-80567 since 08/26/2026. The exploitation appears to be easy. The attack needs to be approached locally. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 08/26/2026).

Upgrading to version 5.10.266, 5.15.217, 6.1.184, 6.6.153, 6.12.105, 6.18.46 or 7.1.10 eliminates this vulnerability. Applying the patch 305c24ee25b6e08ac9f4c5f697e823cc638c38da/7d33b752e0df385b285492b74699fc73b6becdfb/be56730b547737151f24357d832b04aaa93755d5/2b0403fb7e28f65883cd03814b62c9aa9bc7f04d/6741a8c21d98088b7f2d9f4f86a706d311ce34a2/70f9aad3943559af6f32cb303744f35c05ce9cf1/9bbd3682f8a3e064271547133c37fcb17668d860/8786d74bf50e6797b6f655eb381ef6b25451161f is able to eliminate this problem.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.1

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Uninitialized pointer
CWE: CWE-824 / CWE-908
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.266/5.15.217/6.1.184/6.6.153/6.12.105/6.18.46/7.1.10
Patch: 305c24ee25b6e08ac9f4c5f697e823cc638c38da/7d33b752e0df385b285492b74699fc73b6becdfb/be56730b547737151f24357d832b04aaa93755d5/2b0403fb7e28f65883cd03814b62c9aa9bc7f04d/6741a8c21d98088b7f2d9f4f86a706d311ce34a2/70f9aad3943559af6f32cb303744f35c05ce9cf1/9bbd3682f8a3e064271547133c37fcb17668d860/8786d74bf50e6797b6f655eb381ef6b25451161f

Timelineinfo

08/26/2026 Advisory disclosed
08/26/2026 +0 days CVE reserved
08/26/2026 +0 days VulDB entry created
08/26/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-80567 (🔒)
GCVE (CVE): GCVE-0-2026-80567
GCVE (VulDB): GCVE-100-395860

Entryinfo

Created: 08/26/2026 17:48
Changes: 08/26/2026 17:48 (59)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!