In the Linux kernel, the following vulnerability has been resolved:
mctp: fix use after free
Clang static analysis reports this problem
route.c:425:4: warning: Use of memory after it is freed
trace_mctp_key_acquire(key);
^~~~~~~~~~~~~~~~~~~~~~~~~~~
When mctp_key_add() fails, key is freed but then is later
used in trace_mctp_key_acquire(). Add an else statement
to use the key only when mctp_key_add() is successful.
Security readout for executives and security teams
Plain-English summary
CVE-2022-48782 is a Linux kernel memory-safety bug in the MCTP networking code. A failed internal operation can free a key and then still reference it. The source bundle provides fixes but no severity score or exploitation evidence, so urgency depends on whether affected kernel versions are present in your environment.
Executive priority
Treat this as a patch-management item, not an emergency, unless asset inventory shows affected kernels in sensitive or exposed roles. The lack of severity and exploitation data prevents a stronger risk claim from the supplied evidence.
Technical view
The issue is a use-after-free in Linux kernel MCTP route handling. When mctp_key_add() fails, key is freed and later passed to trace_mctp_key_acquire(). The upstream fix adds control flow so the trace call only uses the key after mctp_key_add() succeeds.
Likely exposure
Exposure appears limited to systems running affected Linux kernel versions with the relevant MCTP code present. The bundle identifies Linux 5.16-era versions and stable fixes, but does not provide distribution package mappings or configuration prerequisites.
Exploitation context
The bundle does not show active exploitation, and KEV status is false. The description says Clang static analysis reported the issue. No public exploit status, attack vector, privilege requirement, or real-world abuse evidence is provided.
Researcher notes
Key facts are source-limited: use-after-free, MCTP route.c, static-analysis finding, and two stable commit references. The bundle lacks CVSS, CWE, exploitability detail, distro mappings, and configuration conditions, so validation should focus on kernel provenance and backport evidence.
Mitigation direction
Update affected Linux kernels through the normal vendor or distribution channel.
Confirm the update includes one of the referenced stable kernel fixes.
Check Linux distribution advisories for package-specific fixed versions.
If patching is delayed, follow vendor guidance for temporary risk reduction.
Validation and detection
Inventory Linux kernel versions across servers, appliances, and embedded systems.
Compare running kernels against vendor advisories and the referenced stable commits.
Verify patched systems boot into the updated kernel, not only install it.
Review kernel build or package notes for MCTP-related backports.
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-48782 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.