Linux Kernel up to 7.1.9 iforce iforce_process_packet buffer 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.6$5k-$25k1.22-

Summaryinfo

A vulnerability has been found in Linux Kernel up to 7.1.9 and classified as very critical. The impacted element is the function iforce_process_packet of the component iforce. Performing a manipulation results in buffer overflow. This vulnerability was named CVE-2026-80573. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in Linux Kernel up to 7.1.9. It has been classified as very critical. This affects the function iforce_process_packet of the component iforce. The manipulation with an unknown input leads to a buffer overflow vulnerability. CWE is classifying the issue as CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: Input: iforce - validate input packet lengths iforce_process_packet() reads fixed fields from joystick, wheel and status packets without first checking their lengths. In particular, the shared hats-and-buttons helper unconditionally reads data[6]. The status tail is a sequence of 16-bit effect addresses, but an incomplete final address is also consumed. A successful zero-length USB URB additionally reads the packet ID before the common parser is called. Reject the zero-length USB transfer, require the seven-byte joystick and wheel prefixes and the two-byte status prefix, and consume only complete status-tail addresses.

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-80573 since 08/26/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k 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 0ec411167655ef3ff3e84f6af685e962aff9a75b/609be40988898a4d75225ade0ea5c1734757dd33/e73d7a7d913d89141321f5f3f16343ecc200d152/5232529eaf57f08fe37484e301579a1915b93d14/2c083ab16e33fbff3ab8c752fbf8118ed3dd31ce/a64a8b6b31cd669f0449138e53cc2592d454ccf1/84e5cb517f445dadbd5f8bf4ec513540e51f9c36/5751c781d3c97ab6ce0e2a966156ed882152c415 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: 9.0
VulDB Meta Temp Score: 8.6

VulDB Base Score: 9.0
VulDB Temp Score: 8.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Buffer overflow
CWE: CWE-120 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

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: 0ec411167655ef3ff3e84f6af685e962aff9a75b/609be40988898a4d75225ade0ea5c1734757dd33/e73d7a7d913d89141321f5f3f16343ecc200d152/5232529eaf57f08fe37484e301579a1915b93d14/2c083ab16e33fbff3ab8c752fbf8118ed3dd31ce/a64a8b6b31cd669f0449138e53cc2592d454ccf1/84e5cb517f445dadbd5f8bf4ec513540e51f9c36/5751c781d3c97ab6ce0e2a966156ed882152c415

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

Entryinfo

Created: 08/26/2026 17:44
Changes: 08/26/2026 17:44 (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 ▸

Do you know our Splunk app?

Download it now for free!