CVE-2022-49836
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.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ bbecb07fa0af9a41507ce06d4631fdb3b5059417; < 0a5da069603ecc3d7aa09167450235462adaa295 (affected, git) ≥ bbecb07fa0af9a41507ce06d4631fdb3b5059417; < f9fe7ba4ea5b24ffdf8e125f660aca3ba4a147fb (affected, git) ≥ bbecb07fa0af9a41507ce06d4631fdb3b5059417; < a4b5423f88a17a36550ae8c16c46779b1ee42f4b (affected, git) ≥ bbecb07fa0af9a41507ce06d4631fdb3b5059417; < 5d03c2911c529ea4d6ebfec53425f1091e8d402b (affected, git) ≥ bbecb07fa0af9a41507ce06d4631fdb3b5059417; < d9c31e728843259209fb530c59995e4fe262699f (affected, git) ≥ bbecb07fa0af9a41507ce06d4631fdb3b5059417; < 6e63153db50059fb78b8a8447b132664887d24e3 (affected, git) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
4.16 (affected) ≥ 0; < 4.16 (unaffected, semver) ≥ 4.19.267; ≤ 4.19.* (unaffected, semver) ≥ 5.4.225; ≤ 5.4.* (unaffected, semver) ≥ 5.10.156; ≤ 5.10.* (unaffected, semver) ≥ 5.15.80; ≤ 5.15.* (unaffected, semver) ≥ 6.0.10; ≤ 6.0.* (unaffected, semver) ≥ 6.1; ≤ * (unaffected, original_commit_for_fix) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
No CVSS assessment reported. An unscored record is not a low-severity determination.
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/0a5da069603ecc3d7aa09167450235462adaa295CNA: Linux
- https://git.kernel.org/stable/c/f9fe7ba4ea5b24ffdf8e125f660aca3ba4a147fbCNA: Linux
- https://git.kernel.org/stable/c/a4b5423f88a17a36550ae8c16c46779b1ee42f4bCNA: Linux
- https://git.kernel.org/stable/c/5d03c2911c529ea4d6ebfec53425f1091e8d402bCNA: Linux
- https://git.kernel.org/stable/c/d9c31e728843259209fb530c59995e4fe262699fCNA: Linux
- https://git.kernel.org/stable/c/6e63153db50059fb78b8a8447b132664887d24e3CNA: Linux
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.