---
id: CVE-2022-49836
title: 'siox: fix possible memory leak in siox_device_add()'
summary: |-
  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
  com…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= bbecb07fa0af9a41507ce06d4631fdb3b5059417 <
    0a5da069603ecc3d7aa09167450235462adaa295
  - >-
    Linux >= bbecb07fa0af9a41507ce06d4631fdb3b5059417 <
    f9fe7ba4ea5b24ffdf8e125f660aca3ba4a147fb
  - >-
    Linux >= bbecb07fa0af9a41507ce06d4631fdb3b5059417 <
    a4b5423f88a17a36550ae8c16c46779b1ee42f4b
  - >-
    Linux >= bbecb07fa0af9a41507ce06d4631fdb3b5059417 <
    5d03c2911c529ea4d6ebfec53425f1091e8d402b
  - >-
    Linux >= bbecb07fa0af9a41507ce06d4631fdb3b5059417 <
    d9c31e728843259209fb530c59995e4fe262699f
  - >-
    Linux >= bbecb07fa0af9a41507ce06d4631fdb3b5059417 <
    6e63153db50059fb78b8a8447b132664887d24e3
  - Linux 4.16
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-11-05T19:50:31.324631Z'
published: '2025-05-01'
updated: '2026-11-05'
sourceUpdated: '2026-11-05T20:00:09.305Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2022-49836'
references:
  - url: 'https://git.kernel.org/stable/c/0a5da069603ecc3d7aa09167450235462adaa295'
  - url: 'https://git.kernel.org/stable/c/f9fe7ba4ea5b24ffdf8e125f660aca3ba4a147fb'
  - url: 'https://git.kernel.org/stable/c/a4b5423f88a17a36550ae8c16c46779b1ee42f4b'
  - url: 'https://git.kernel.org/stable/c/5d03c2911c529ea4d6ebfec53425f1091e8d402b'
  - url: 'https://git.kernel.org/stable/c/d9c31e728843259209fb530c59995e4fe262699f'
  - url: 'https://git.kernel.org/stable/c/6e63153db50059fb78b8a8447b132664887d24e3'
tags:
  - cve.org
epss: 0.00202
epssPercentile: 0.1026
ingestedAt: '2026-11-05T22:38:31.618Z'
---

## Overview

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

- `Linux >= bbecb07fa0af9a41507ce06d4631fdb3b5059417 < 0a5da069603ecc3d7aa09167450235462adaa295`
- `Linux >= bbecb07fa0af9a41507ce06d4631fdb3b5059417 < f9fe7ba4ea5b24ffdf8e125f660aca3ba4a147fb`
- `Linux >= bbecb07fa0af9a41507ce06d4631fdb3b5059417 < a4b5423f88a17a36550ae8c16c46779b1ee42f4b`
- `Linux >= bbecb07fa0af9a41507ce06d4631fdb3b5059417 < 5d03c2911c529ea4d6ebfec53425f1091e8d402b`
- `Linux >= bbecb07fa0af9a41507ce06d4631fdb3b5059417 < d9c31e728843259209fb530c59995e4fe262699f`
- `Linux >= bbecb07fa0af9a41507ce06d4631fdb3b5059417 < 6e63153db50059fb78b8a8447b132664887d24e3`
- `Linux 4.16`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.