# siox: fix possible memory leak in siox_device_add()

CVE record · `CVE-2022-49836`

- **Identifiers:** `CVE-2022-49836`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 1 May 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 1 May 2025, 14:09 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `bbecb07fa0af9a41507ce06d4631fdb3b5059417 to before 0a5da069603ecc3d7aa09167450235462adaa295` (git)
  - affected: `bbecb07fa0af9a41507ce06d4631fdb3b5059417 to before f9fe7ba4ea5b24ffdf8e125f660aca3ba4a147fb` (git)
  - affected: `bbecb07fa0af9a41507ce06d4631fdb3b5059417 to before a4b5423f88a17a36550ae8c16c46779b1ee42f4b` (git)
  - affected: `bbecb07fa0af9a41507ce06d4631fdb3b5059417 to before 5d03c2911c529ea4d6ebfec53425f1091e8d402b` (git)
  - affected: `bbecb07fa0af9a41507ce06d4631fdb3b5059417 to before d9c31e728843259209fb530c59995e4fe262699f` (git)
  - affected: `bbecb07fa0af9a41507ce06d4631fdb3b5059417 to before 6e63153db50059fb78b8a8447b132664887d24e3` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `4.16`
  - unaffected: `before 4.16` (semver)
  - unaffected: `4.19.267 to 4.19.*, inclusive` (semver)
  - unaffected: `5.4.225 to 5.4.*, inclusive` (semver)
  - unaffected: `5.10.156 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.80 to 5.15.*, inclusive` (semver)
  - unaffected: `6.0.10 to 6.0.*, inclusive` (semver)
  - unaffected: `6.1 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0020, the 10th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 1 May 2025, 14:09 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2022-49836)
- 1 May 2025, 15:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2022-49836)

## Sources

- [CVE List: CVE-2022-49836](https://www.cve.org/CVERecord?id=CVE-2022-49836)
- [NVD: CVE-2022-49836](https://nvd.nist.gov/vuln/detail/CVE-2022-49836)

### References from the CNA

- <https://git.kernel.org/stable/c/0a5da069603ecc3d7aa09167450235462adaa295>
- <https://git.kernel.org/stable/c/f9fe7ba4ea5b24ffdf8e125f660aca3ba4a147fb>
- <https://git.kernel.org/stable/c/a4b5423f88a17a36550ae8c16c46779b1ee42f4b>
- <https://git.kernel.org/stable/c/5d03c2911c529ea4d6ebfec53425f1091e8d402b>
- <https://git.kernel.org/stable/c/d9c31e728843259209fb530c59995e4fe262699f>
- <https://git.kernel.org/stable/c/6e63153db50059fb78b8a8447b132664887d24e3>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2022-49836>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2022-49836/>. Everything for agents: <https://agentprime.io/llms.txt>.
