LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49854: mctp: Fix an error handling path in mctp_init()

In the Linux kernel, the following vulnerability has been resolved: mctp: Fix an error handling path in mctp_init() If mctp_neigh_init() return error, the routes resources should be released in the error handling path. Otherwise some resources leak.

MediumCVSS 5.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-49854 is a Linux kernel resource-leak bug in MCTP initialization. If one setup step fails, route resources may not be released. The main business impact is local availability risk, not data theft or tampering, based on the supplied CVSS vector.

Executive priority

Treat as a moderate-priority Linux kernel maintenance issue. It is not documented as actively exploited, but local availability impact can matter on shared or operationally sensitive systems.

Technical view

The flaw is in the Linux kernel mctp_init() error handling path. When mctp_neigh_init() returns an error, MCTP route resources should be released but are not. The CVSS vector requires local access and low privileges, with high availability impact and no confidentiality or integrity impact stated.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel versions listed in the CVE metadata, especially where the MCTP component is present and initialized. The sources do not establish remote exposure.

Exploitation context

The source bundle does not report active exploitation, and KEV is false. The CVSS vector indicates local, low-complexity exploitation requiring low privileges, with availability impact only. No public exploit status is provided in the supplied sources.

Researcher notes

Evidence is limited to the CVE record and Linux stable commit references. The affected version data is terse and should be mapped through distribution advisories before final exposure decisions. Do not infer remote reachability or data compromise from the supplied sources.

Mitigation direction

  • Identify Linux assets running affected kernel versions from the CVE metadata.
  • Apply vendor or distribution kernel updates containing the referenced stable fixes.
  • Prioritize shared, multi-user, embedded, or infrastructure systems where local denial of service matters.
  • If patching is delayed, monitor affected hosts for resource exhaustion or unusual kernel instability.
  • Check vendor advisories before disabling MCTP, because operational impact is environment-specific.

Validation and detection

  • Confirm each host kernel version against vendor fixed-package information.
  • Verify the referenced stable kernel commits are included in deployed kernel builds.
  • Review kernel configuration or inventory data for MCTP component presence.
  • Confirm post-update systems rebooted into the remediated kernel.
  • Track exceptions where vendor guidance is unavailable or patching is deferred.
Prepared
Confidence
medium
Sources
5

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-49854 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
4Source 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-49854Attack 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4d8b9319282ae84f5a17b28d8b5b5d1e7e537312, 4d8b9319282ae84f5a17b28d8b5b5d1e7e537312, 4d8b9319282ae84f5a17b28d8b5b5d1e7e537312unaffected
LinuxLinux5.15, 0, 5.15.79, 6.0.9, 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.