LiveActive security incident?Get immediate response
CVE Record

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a possible memory leak in the siox device registration error path. The source does not provide a CVSS score, concrete impact rating, or evidence of real-world exploitation. Treat it as a kernel maintenance item unless your Linux vendor assigns higher urgency.

Executive priority

Handle through normal kernel patch governance. There is not enough source evidence to justify emergency treatment, but kernel memory leaks should not be ignored on long-lived or embedded systems.

Technical view

In siox_device_add(), dev_set_name() allocates a name before device_register(). If device_register() fails, the old error path did not release the device reference correctly. The fix calls put_device(), allowing kobject cleanup and siox_device_release() to free related memory.

Likely exposure

Exposure is limited to Linux systems running affected kernel code with the siox subsystem present. Actual fleet risk depends on distribution backports, kernel configuration, and whether the relevant siox device path can be reached.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. The described issue is a memory leak on an error path, not a documented privilege escalation or remote code execution path.

Researcher notes

The useful review focus is the failed device_register() path after dev_set_name(). Validate patch presence by commit lineage or vendor backport notes, not only upstream version numbers.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Check Linux distribution advisories for backported fixes and package versions.
  • Prioritize systems where custom kernels or siox support are present.
  • Track vendor severity updates because no CVSS score is provided.

Validation and detection

  • Inventory Linux kernel versions and distribution package build levels.
  • Confirm whether vendor changelogs include the referenced stable commits.
  • Review kernel configuration for siox subsystem presence.
  • Check vulnerability scanner results against vendor-patched kernel packages.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-49836 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
7Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxbbecb07fa0af9a41507ce06d4631fdb3b5059417, bbecb07fa0af9a41507ce06d4631fdb3b5059417, bbecb07fa0af9a41507ce06d4631fdb3b5059417, bbecb07fa0af9a41507ce06d4631fdb3b5059417, bbecb07fa0af9a41507ce06d4631fdb3b5059417, bbecb07fa0af9a41507ce06d4631fdb3b5059417unaffected
LinuxLinux4.16, 0, 4.19.267, 5.4.225, 5.10.156, 5.15.80, 6.0.10, 6.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.