Linux Kernel up to 5.4.224/5.10.155/5.15.79/6.0.9 iforce_init_device 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.4$0-$5k0.00

Summaryinfo

A vulnerability labeled as problematic has been found in Linux Kernel up to 5.4.224/5.10.155/5.15.79/6.0.9. This affects the function iforce_init_device. Executing a manipulation can lead to uninitialized pointer. This vulnerability is handled as CVE-2022-49790. There is not any exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability classified as problematic was found in Linux Kernel up to 5.4.224/5.10.155/5.15.79/6.0.9. This vulnerability affects the function iforce_init_device. 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. The impact remains unknown. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: Input: iforce - invert valid length check when fetching device IDs syzbot is reporting uninitialized value at iforce_init_device() [1], for commit 6ac0aec6b0a6 ("Input: iforce - allow callers supply data buffer when fetching device IDs") is checking that valid length is shorter than bytes to read. Since iforce_get_id_packet() stores valid length when returning 0, the caller needs to check that valid length is longer than or equals to bytes to read.

The advisory is available at git.kernel.org. This vulnerability was named CVE-2022-49790 since 05/01/2025. Technical details are known, but there is no available exploit.

Upgrading to version 5.4.225, 5.10.156, 5.15.80 or 6.0.10 eliminates this vulnerability. Applying the patch 5d53797ce7ce8fb1d95a5bebc5efa9418c4217a3/24cc679abbf31477d0cc6106ec83c2fbae6b3cdf/fdd57c20d4408cac3c3c535c120d244e083406c9/6365569d62a75ddf53fb0c2936c16587a365984c/b8ebf250997c5fb253582f42bfe98673801ebebd is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-12986). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.4

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔍

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: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

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.4.225/5.10.156/5.15.80/6.0.10
Patch: 5d53797ce7ce8fb1d95a5bebc5efa9418c4217a3/24cc679abbf31477d0cc6106ec83c2fbae6b3cdf/fdd57c20d4408cac3c3c535c120d244e083406c9/6365569d62a75ddf53fb0c2936c16587a365984c/b8ebf250997c5fb253582f42bfe98673801ebebd

Timelineinfo

05/01/2025 🔍
05/01/2025 +0 days 🔍
05/01/2025 +0 days 🔍
11/07/2025 +190 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2022-49790 (🔍)
GCVE (CVE): GCVE-0-2022-49790
GCVE (VulDB): GCVE-100-306946
EUVD: 🔍

Entryinfo

Created: 05/01/2025 17:27
Updated: 11/07/2025 13:14
Changes: 05/01/2025 17:27 (57), 11/05/2025 23:32 (1), 11/07/2025 13:14 (11)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!