LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50349: misc: tifm: fix possible memory leak in tifm_7xx1_switch_media()

In the Linux kernel, the following vulnerability has been resolved: misc: tifm: fix possible memory leak in tifm_7xx1_switch_media() If device_register() returns error in tifm_7xx1_switch_media(), name of kobject which is allocated in dev_set_name() called in device_add() is leaked. Never directly free @dev after calling device_register(), even if it returned an error! Always use put_device() to give up the reference initialized.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-50349 is a Linux kernel memory leak in the tifm 7xx1 media-switch path. A local low-privileged user may be able to cause availability impact on affected systems using this driver. The provided sources show no KEV listing and no cited active exploitation.

Executive priority

Treat this as routine-to-priority kernel maintenance, not an emergency. It has local availability impact and no sourced active exploitation, but it can matter on multi-user or high-availability Linux systems.

Technical view

In tifm_7xx1_switch_media(), a device_register() failure can leak the kobject name allocated through dev_set_name()/device_add(). The resolved behavior is to release the initialized device reference with put_device(). The issue is CWE-401 with CVSS 3.1 score 5.5 and local availability impact.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions with the tifm 7xx1 driver present or loadable. Distribution kernels may have backported fixes, so version strings alone are insufficient for final exposure decisions.

Exploitation context

The CVSS vector requires local access, low privileges, no user interaction, and affects availability only. The bundle does not identify public exploitation, weaponized details, or inclusion in CISA KEV.

Researcher notes

The source evidence is narrow: a kernel memory leak fixed in stable commits. The affected-version data is branch-oriented and may not match downstream distributions. Avoid claiming confidentiality, integrity, remote attack, or active exploitation without additional vendor evidence.

Mitigation direction

  • Apply vendor or distribution kernel updates containing the stable tifm fix.
  • Check vendor advisories for backported fixes before relying on upstream version numbers.
  • Reduce exposure to untrusted local users on affected systems where patching is delayed.
  • Review whether tifm 7xx1 support is needed on critical systems.

Validation and detection

  • Inventory Linux kernel versions and distribution patch levels across managed systems.
  • Confirm whether the tifm 7xx1 driver is present, built, or loadable.
  • Map systems against vendor advisories and the referenced stable kernel commits.
  • Prioritize validation on shared hosts or systems with untrusted local shell users.
Prepared
Confidence
high
Sources
11

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-50349 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
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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.

1CVSS vectors
3Timeline events
1ADP providers
10Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2022-50349Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux2428a8fe2261e901e058d9ea8b6ed7e1b4268b79, 2428a8fe2261e901e058d9ea8b6ed7e1b4268b79, 2428a8fe2261e901e058d9ea8b6ed7e1b4268b79, 2428a8fe2261e901e058d9ea8b6ed7e1b4268b79, 2428a8fe2261e901e058d9ea8b6ed7e1b4268b79, 2428a8fe2261e901e058d9ea8b6ed7e1b4268b79, 2428a8fe2261e901e058d9ea8b6ed7e1b4268b79, 2428a8fe2261e901e058d9ea8b6ed7e1b4268b79, 2428a8fe2261e901e058d9ea8b6ed7e1b4268b79unaffected
LinuxLinux2.6.22, 0, 4.9.337, 4.14.303, 4.19.270, 5.4.229, 5.10.163, 5.15.86, 6.0.16, 6.1.2, 6.2affected
Weakness

CWE details

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