CVE-2022-49915: mISDN: fix possible memory leak in mISDN_register_device()
In the Linux kernel, the following vulnerability has been resolved:
mISDN: fix possible memory leak in mISDN_register_device()
Afer commit 1fa5ae857bb1 ("driver core: get rid of struct device's
bus_id string array"), the name of device is allocated dynamically,
add put_device() to give up the reference, so that the name can be
freed in kobject_cleanup() when the refcount is 0.
Set device class before put_device() to avoid null release() function
WARN message in device_release().
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory leak in the mISDN device registration path. A local user with low privileges may be able to trigger availability impact, but the sources do not show remote exploitation or data theft. Treat it as a stability and patch hygiene issue for systems using affected Linux kernels.
Executive priority
Patch through normal kernel maintenance, with higher priority on multi-user Linux hosts and shared environments. This is not presented as remotely exploitable or actively exploited, but it can affect availability and should not remain untracked.
Technical view
CVE-2022-49915 fixes a missing device reference release in mISDN_register_device(). After dynamic device-name allocation, put_device() was needed so kobject cleanup can free memory when the refcount reaches zero. The CVSS vector is local, low complexity, low privileges, no user interaction, and high availability impact.
Likely exposure
Exposure is most likely on Linux systems running affected kernel versions from 2.6.30 through listed fixed stable ranges, especially where mISDN code is built or loadable. The source bundle does not provide distribution package mappings, default configuration status, or evidence that internet-facing services are directly exposed.
Exploitation context
The provided data marks KEV as false and gives no cited evidence of active exploitation. The CVSS vector requires local access with low privileges. The described impact is availability through memory leakage, not confidentiality or integrity compromise.
Researcher notes
Focus validation on kernel lineage and the mISDN_register_device() fix. The key remediation signal is the added put_device() handling and class assignment before release. The bundle lacks distro-specific fixed package versions, runtime prerequisites, and exploit evidence.
Mitigation direction
Apply a vendor Linux kernel update containing the referenced stable fixes.
Prioritize systems where untrusted local users can execute code.
Check distribution advisories for package names and backport status.
Where unused, review vendor guidance for disabling mISDN support.
Reboot or otherwise activate the fixed kernel after updating.
Validation and detection
Inventory running kernel versions against the affected version list.
Confirm vendor packages include a backport for CVE-2022-49915.
Check whether mISDN support is built, available, or loaded.
Verify the active kernel changed after patching.
Record exceptions where vendor mapping is unavailable.
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.
cwe · low confidence lookup
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-401 · source CWE mapping
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.