siox: fix possible memory leak in siox_device_add()
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 4.19.267, 5.10.156, 5.15.80, 5.4.225, 6.0.10
- CVEs
- CVE-2022-49836
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 02:15 UTC · Revision 1
Source evidence
siox: fix possible memory leak in siox_device_add()
core-osv · Original sourcePublished 1 May 2025, 14:09 UTC
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.
osv:CVE-2022-49836
Kernel
Fixed versions: 4.19.267, 5.4.225, 5.10.156, 5.15.80, 6.0.10
Complete source record
{
"id": "b254d8f91c86bcb3a5476feb65c30cfcf5ad4d4bb3fbe445555c46a24ee96c47",
"url": "https://osv.dev/vulnerability/CVE-2022-49836",
"method": "structured",
"payload": {
"kind": "advisory",
"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 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.",
"evidence": "osv:CVE-2022-49836",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "4.19.267",
"evidence": "/affected/1/ranges"
},
{
"value": "5.4.225",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.156",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.80",
"evidence": "/affected/1/ranges"
},
{
"value": "6.0.10",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2022-49836",
"aliases": [
"CVE-2022-49836"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "bbecb07fa0af9a41507ce06d4631fdb3b5059417"
},
{
"fixed": "0a5da069603ecc3d7aa09167450235462adaa295"
},
{
"fixed": "f9fe7ba4ea5b24ffdf8e125f660aca3ba4a147fb"
},
{
"fixed": "a4b5423f88a17a36550ae8c16c46779b1ee42f4b"
},
{
"fixed": "5d03c2911c529ea4d6ebfec53425f1091e8d402b"
},
{
"fixed": "d9c31e728843259209fb530c59995e4fe262699f"
},
{
"fixed": "6e63153db50059fb78b8a8447b132664887d24e3"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49836.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.16.0"
},
{
"fixed": "4.19.267"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.20.0"
},
{
"fixed": "5.4.225"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.156"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.80"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.0.10"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49836.json"
}
}
],
"modified": "2026-10-28T02:30:49.295123024Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/0a5da069603ecc3d7aa09167450235462adaa295",
"https://git.kernel.org/stable/c/5d03c2911c529ea4d6ebfec53425f1091e8d402b",
"https://git.kernel.org/stable/c/6e63153db50059fb78b8a8447b132664887d24e3",
"https://git.kernel.org/stable/c/a4b5423f88a17a36550ae8c16c46779b1ee42f4b",
"https://git.kernel.org/stable/c/d9c31e728843259209fb530c59995e4fe262699f",
"https://git.kernel.org/stable/c/f9fe7ba4ea5b24ffdf8e125f660aca3ba4a147fb",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49836.json",
"https://nvd.nist.gov/vuln/detail/CVE-2022-49836",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49836.json"
}
},
"related_cves": [
{
"value": "CVE-2022-49836",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 517281,
"published_at": "2025-05-01T14:09:53.454+00:00"
}