CVE-2022-49836
published 2025-05-01CVE-2022-49836: 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…
PriorityP415medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.19%
8.8th percentile
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
18 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.0.10-1 (bookworm) | linux 6.0.10-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= bbecb07fa0af9a41507ce06d4631fdb3b5059417 < 0a5da069603ecc3d7aa09167450235462adaa295 | 0a5da069603ecc3d7aa09167450235462adaa295 |
| linux | linux | >= bbecb07fa0af9a41507ce06d4631fdb3b5059417 < f9fe7ba4ea5b24ffdf8e125f660aca3ba4a147fb | f9fe7ba4ea5b24ffdf8e125f660aca3ba4a147fb |
| linux | linux | >= bbecb07fa0af9a41507ce06d4631fdb3b5059417 < a4b5423f88a17a36550ae8c16c46779b1ee42f4b | a4b5423f88a17a36550ae8c16c46779b1ee42f4b |
| linux | linux | >= bbecb07fa0af9a41507ce06d4631fdb3b5059417 < 5d03c2911c529ea4d6ebfec53425f1091e8d402b | 5d03c2911c529ea4d6ebfec53425f1091e8d402b |
| linux | linux | >= bbecb07fa0af9a41507ce06d4631fdb3b5059417 < d9c31e728843259209fb530c59995e4fe262699f | d9c31e728843259209fb530c59995e4fe262699f |
| linux | linux | >= bbecb07fa0af9a41507ce06d4631fdb3b5059417 < 6e63153db50059fb78b8a8447b132664887d24e3 | 6e63153db50059fb78b8a8447b132664887d24e3 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.158-1 | 5.10.158-1 |
| linux | linux_kernel | >= 0 < 6.0.10-1 | 6.0.10-1 |
| linux | linux_kernel | >= 0 < 6.0.10-1 | 6.0.10-1 |
| linux | linux_kernel | >= 0 < 6.0.10-1 | 6.0.10-1 |
| linux | linux_kernel | >= 4.16 < 4.19.267 | 4.19.267 |
| linux | linux_kernel | >= 4.20 < 5.4.225 | 5.4.225 |
| linux | linux_kernel | >= 5.11 < 5.15.80 | 5.15.80 |
| linux | linux_kernel | >= 5.16 < 6.0.10 | 6.0.10 |
| linux | linux_kernel | >= 5.5 < 5.10.156 | 5.10.156 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
CVE-2022-49836: In the Linux kernel, the following vulnerability has been resolved: siox: fix possible memory leak in siox_device_add() If device_register() returns e
osv·2025-05-01·CVSS 5.5
CVE-2022-49836 [MEDIUM] CVE-2022-49836: In the Linux kernel, the following vulnerability has been resolved: siox: fix possible memory leak in siox_device_add() If device_register() returns e
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.
GHSA
GHSA-4jq9-rx3w-p8vg: In the Linux kernel, the following vulnerability has been resolved:
siox: fix possible memory leak in siox_device_add()
If device_register() returns
ghsa_unreviewed·2025-05-01
CVE-2022-49836 [MEDIUM] CWE-401 GHSA-4jq9-rx3w-p8vg: In the Linux kernel, the following vulnerability has been resolved:
siox: fix possible memory leak in siox_device_add()
If device_register() returns
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.
Red Hat
kernel: siox: fix possible memory leak in siox_device_add()
vendor_redhat·2025-05-01·CVSS 5.5
CVE-2022-49836 [MEDIUM] CWE-401 kernel: siox: fix possible memory leak in siox_device_add()
kernel: 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.
Package: kernel (Red Hat Enterprise Linux 10) - Not affected
Package: kernel (Red Hat Enterprise Linux 6) - Not affected
Package: kernel (Red Hat Enterprise Linux 7) - Not affected
Package: kernel-rt (Red Hat Enterprise Linux 7) - Not
Debian
CVE-2022-49836: linux - In the Linux kernel, the following vulnerability has been resolved: siox: fix p...
vendor_debian·2022·CVSS 5.5
CVE-2022-49836 [MEDIUM] CVE-2022-49836: linux - In the Linux kernel, the following vulnerability has been resolved: siox: fix p...
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.
Scope: local
bookworm: resolved (fixed in 6.0.10-1)
bullseye: resolved (fixed in 5.10.158-1)
forky: resolved (fixed in 6.0.10-1)
sid: resolved (fixed in 6.0.10-1)
trixie: resolved (fixed in 6.0.10-1)
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/0a5da069603ecc3d7aa09167450235462adaa295https://git.kernel.org/stable/c/5d03c2911c529ea4d6ebfec53425f1091e8d402bhttps://git.kernel.org/stable/c/6e63153db50059fb78b8a8447b132664887d24e3https://git.kernel.org/stable/c/a4b5423f88a17a36550ae8c16c46779b1ee42f4bhttps://git.kernel.org/stable/c/d9c31e728843259209fb530c59995e4fe262699fhttps://git.kernel.org/stable/c/f9fe7ba4ea5b24ffdf8e125f660aca3ba4a147fb
2025-05-01
Published