Linux Kernel up to 7.1.9 synaptics-rmi4 VIDIOC_S_INPUT heap-based overflow

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.
8.4$0-$5k0.91-

Summaryinfo

A vulnerability marked as very critical has been reported in Linux Kernel up to 7.1.9. This issue affects the function VIDIOC_S_INPUT of the component synaptics-rmi4. The manipulation leads to heap-based overflow. This vulnerability is documented as CVE-2026-80568. The attack needs to be performed locally. There is not any exploit available.

Detailsinfo

A vulnerability was found in Linux Kernel up to 7.1.9 and classified as very critical. This issue affects the function VIDIOC_S_INPUT of the component synaptics-rmi4. The manipulation with an unknown input leads to a heap-based overflow vulnerability. Using CWE to declare the problem leads to CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). Impacted is confidentiality, integrity, and availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: Input: synaptics-rmi4 - block s_input when F54 queue is busy Changing the input (diagnostic report type) mid-stream changes the report size. Since V4L2 buffers are allocated based on the size at stream start, changing the input while streaming could lead to a heap buffer overflow if the new size is larger than the allocated buffers. Prevent this by blocking VIDIOC_S_INPUT with -EBUSY if the V4L2 queue is busy (streaming).

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2026-80568 since 08/26/2026. The exploitation is known to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (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 7e994a9ecc0b49ad2fe63da9c92a8aca8a6614af/fa69f93015becf3729716de2199b58540aa99672/493ba8e794729649689438edba72337111303cc4/1d718f1461766e9f00a8dbeb4f13f1b1c19d90ac/cae79513f9115c350561b16f36adcb47c9bfff12/ff0849705d29277fd1f6fc6596674b9308724fb2/ddd9a53faf3b65e5920cb802cb1db6f4615bdfef/fbfd76746adc16d64be29ff113f673b70bc3f5c2 is able to eliminate this problem.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.8
VulDB Meta Temp Score: 8.4

VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Heap-based overflow
CWE: CWE-122 / CWE-119
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: 7e994a9ecc0b49ad2fe63da9c92a8aca8a6614af/fa69f93015becf3729716de2199b58540aa99672/493ba8e794729649689438edba72337111303cc4/1d718f1461766e9f00a8dbeb4f13f1b1c19d90ac/cae79513f9115c350561b16f36adcb47c9bfff12/ff0849705d29277fd1f6fc6596674b9308724fb2/ddd9a53faf3b65e5920cb802cb1db6f4615bdfef/fbfd76746adc16d64be29ff113f673b70bc3f5c2

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-80568 (🔒)
GCVE (CVE): GCVE-0-2026-80568
GCVE (VulDB): GCVE-100-395861

Entryinfo

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

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!