Linux Kernel up to 6.0.9 siox siox_device_add memory leak

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

Summaryinfo

A vulnerability was found in Linux Kernel up to 4.19.266/5.4.224/5.10.155/5.15.79/6.0.9 and classified as critical. Affected by this vulnerability is the function siox_device_add of the component siox. Such manipulation leads to memory leak. This vulnerability is referenced as CVE-2022-49836. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 4.19.266/5.4.224/5.10.155/5.15.79/6.0.9. Affected by this issue is the function siox_device_add of the component siox. The manipulation with an unknown input leads to a memory leak vulnerability. Using CWE to declare the problem leads to CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. Impacted is availability. CVE summarizes:

In the Linux kernel, the following vulnerability has been resolved: siox: fix possible memory leak in siox_device_add() If device_register() returns error in siox_device_add(), the name allocated by dev_set_name() need be freed. As comment of device_register() says, it should use put_device() to give up the reference in the error path. So fix this by calling put_device(), then the name can be freed in kobject_cleanup(), and sdevice is freed in siox_device_release(), set it to null in error path.

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

Upgrading to version 4.19.267, 5.4.225, 5.10.156, 5.15.80 or 6.0.10 eliminates this vulnerability. Applying the patch 0a5da069603ecc3d7aa09167450235462adaa295/f9fe7ba4ea5b24ffdf8e125f660aca3ba4a147fb/a4b5423f88a17a36550ae8c16c46779b1ee42f4b/5d03c2911c529ea4d6ebfec53425f1091e8d402b/d9c31e728843259209fb530c59995e4fe262699f/6e63153db50059fb78b8a8447b132664887d24e3 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.

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.6
VulDB Meta Temp Score: 5.5

VulDB Base Score: 5.7
VulDB Temp Score: 5.5
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: Memory leak
CWE: CWE-401 / CWE-404
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 4.19.267/5.4.225/5.10.156/5.15.80/6.0.10
Patch: 0a5da069603ecc3d7aa09167450235462adaa295/f9fe7ba4ea5b24ffdf8e125f660aca3ba4a147fb/a4b5423f88a17a36550ae8c16c46779b1ee42f4b/5d03c2911c529ea4d6ebfec53425f1091e8d402b/d9c31e728843259209fb530c59995e4fe262699f/6e63153db50059fb78b8a8447b132664887d24e3

Timelineinfo

05/01/2025 🔍
05/01/2025 +0 days 🔍
05/01/2025 +0 days 🔍
11/10/2025 +193 days 🔍

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2022-49836 (🔍)
GCVE (CVE): GCVE-0-2022-49836
GCVE (VulDB): GCVE-100-307010

Entryinfo

Created: 05/01/2025 17:39
Updated: 11/10/2025 23:28
Changes: 05/01/2025 17:39 (59), 11/10/2025 23:28 (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 know our Splunk app?

Download it now for free!