CVE-2022-49836

siox: fix possible memory leak in siox_device_add()

MEDIUM
5.5
CVSS Score
Published: May 1, 2025 at 02:09 PM UTC
Updated: June 17, 2026 at 05:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.16 ≤ v < 4.19.2674.16 ≤ v < 5.10.1564.16 ≤ v < 5.15.804.16 ≤ v < 5.4.2254.16 ≤ v < 6.0.104.16 ≤ v < 6.14.20 ≤ v < 5.4.2255.11 ≤ v < 5.15.805.16 ≤ v < 6.0.105.5 ≤ v < 5.10.1564.166.1 rc16.1 rc26.1 rc36.1 rc46.1 rc5bbecb07fa0af9a41507ce06d4631fdb3b5059417
Vendor states this is fixed in 0a5da069603ecc3d7aa09167450235462adaa295 (fixed)
Vendor states this is fixed in 5d03c2911c529ea4d6ebfec53425f1091e8d402b (fixed)
Vendor states this is fixed in 6e63153db50059fb78b8a8447b132664887d24e3 (fixed)
Vendor states this is fixed in a4b5423f88a17a36550ae8c16c46779b1ee42f4b (fixed)
Vendor states this is fixed in d9c31e728843259209fb530c59995e4fe262699f (fixed)
Vendor states this is fixed in f9fe7ba4ea5b24ffdf8e125f660aca3ba4a147fb (fixed)
Vendor states this is fixed in 4.16 (unaffected)
Vendor states this is fixed in 4.19.267 (unaffected)
Vendor states this is fixed in 5.10.156 (unaffected)
Vendor states this is fixed in 5.15.80 (unaffected)
Vendor states this is fixed in 5.4.225 (unaffected)
Vendor states this is fixed in 6.0.10 (unaffected)
Vendor states this is fixed in 6.1 (unaffected)

References (6)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/0a5da069603ecc3d7aa09167450235462adaa295
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/5d03c2911c529ea4d6ebfec53425f1091e8d402b
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/6e63153db50059fb78b8a8447b132664887d24e3
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/a4b5423f88a17a36550ae8c16c46779b1ee42f4b
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/d9c31e728843259209fb530c59995e4fe262699f
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/f9fe7ba4ea5b24ffdf8e125f660aca3ba4a147fb

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-401

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card