LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50312: drivers: serial: jsm: fix some leaks in probe

In the Linux kernel, the following vulnerability has been resolved: drivers: serial: jsm: fix some leaks in probe This error path needs to unwind instead of just returning directly.

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-50312 is a Linux kernel issue in the JSM serial driver. The public record describes resource leaks during driver probe error handling. The available sources do not provide CVSS, confirmed impact, or exploitation details, so business urgency should be based on kernel exposure and vendor patch status.

Executive priority

Treat this as routine kernel hygiene unless local exposure to the JSM serial driver is confirmed. There is no cited active exploitation or CVSS score, but kernel fixes should still enter normal patch cycles.

Technical view

The flaw is in drivers/serial/jsm probe error paths. When probe failed, the code returned directly instead of unwinding allocated resources. Linux stable commits are referenced as fixes. The record does not specify a CWE, privilege requirement, crash condition, or security impact beyond the leak behavior.

Likely exposure

Exposure is limited to Linux systems using affected kernels where the JSM serial driver is present and relevant probe paths can execute. Distro backports may change exposure, so asset validation should use package and kernel vendor advisories rather than upstream version strings alone.

Exploitation context

The bundle does not show CISA KEV listing, active exploitation, public exploit availability, or weaponized use. The described issue appears tied to local kernel driver initialization behavior, but the sources do not prove exploitability or impact severity.

Researcher notes

Focus analysis on the jsm probe unwind path and affected stable backports. The public CVE data is sparse: no CVSS, CWE, exploit status, or detailed impact is provided. Avoid overstating risk without distro-specific or kernel-config evidence.

Mitigation direction

  • Apply kernel updates containing the linked stable fixes.
  • Check Linux distribution advisories for backported fixes.
  • Prioritize systems with the JSM serial driver enabled or loaded.
  • Disable unused JSM serial driver support where operationally safe.
  • Track vendor guidance because no standalone workaround is named.

Validation and detection

  • Inventory running kernel versions across Linux assets.
  • Check whether the JSM serial driver is built, available, or loaded.
  • Compare vendor kernel packages against advisory-fixed versions.
  • Review distro changelogs for CVE-2022-50312 or linked commits.
  • Confirm updates in staging before production rollout.
Prepared
Confidence
medium
Sources
11

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-50312 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
10Source 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
LinuxLinux03a8482c17dd0ae3251451d54cbbc03f930f21d5, 03a8482c17dd0ae3251451d54cbbc03f930f21d5, 03a8482c17dd0ae3251451d54cbbc03f930f21d5, 03a8482c17dd0ae3251451d54cbbc03f930f21d5, 03a8482c17dd0ae3251451d54cbbc03f930f21d5, 03a8482c17dd0ae3251451d54cbbc03f930f21d5, 03a8482c17dd0ae3251451d54cbbc03f930f21d5, 03a8482c17dd0ae3251451d54cbbc03f930f21d5, 03a8482c17dd0ae3251451d54cbbc03f930f21d5unaffected
LinuxLinux3.19, 0, 4.9.331, 4.14.296, 4.19.262, 5.4.220, 5.10.150, 5.15.75, 5.19.17, 6.0.3, 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.