LiveActive security incident?Get immediate response
CVE Record

CVE-2022-48768: tracing/histogram: Fix a potential memory leak for kstrdup()

In the Linux kernel, the following vulnerability has been resolved: tracing/histogram: Fix a potential memory leak for kstrdup() kfree() is missing on an error path to free the memory allocated by kstrdup(): p = param = kstrdup(data->params[i], GFP_KERNEL); So it is better to free it via kfree(p).

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-48768 is a Linux kernel tracing histogram memory leak. On one error path, memory allocated with kstrdup() was not freed. The public record does not provide CVSS, observed exploitation, business impact, or workaround details, so urgency should be based on kernel exposure and vendor patch status.

Executive priority

Medium operational priority until vendor impact is confirmed. This is a kernel memory leak with incomplete severity data, no KEV listing, and no sourced exploitation evidence, but kernel flaws should not be left unmanaged on critical systems.

Technical view

The flaw is in Linux kernel tracing/histogram handling. The resolved issue adds missing kfree() cleanup for memory allocated from data->params[i] via kstrdup() when an error path is taken. The source bundle lists multiple Linux stable kernel commits as references for the fix.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions identified by the CVE record. The bundle names Linux as the affected product, but does not identify distributions, configurations, privileges required, or reachable attack paths.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation or public exploit use. Treat exploitation status as unconfirmed, not absent risk.

Researcher notes

Evidence is sparse. The public description supports a memory leak on an error path in tracing/histogram code, but not exploitability, privilege requirements, denial-of-service impact, or distribution-specific status. Further triage should rely on vendor kernel advisories and patch backport mapping.

Mitigation direction

  • Update affected Linux kernels through the normal vendor-supported channel.
  • Confirm the installed kernel includes the relevant upstream stable fix or vendor backport.
  • If immediate patching is not possible, check vendor guidance for supported mitigations.
  • Prioritize systems where kernel tracing features are enabled or exposed to untrusted users.

Validation and detection

  • Inventory Linux kernel versions across servers, containers hosts, and appliances.
  • Compare running kernels against the CVE affected version data and vendor advisories.
  • Verify patched kernels include one of the referenced stable commits or an equivalent backport.
  • Document any unpatched systems and compensating vendor guidance.
Prepared
Confidence
medium
Sources
7

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-48768 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
2ADP providers
6Source links

SSVC decision data

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

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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux38b67e60b6b582e81f9db1b2e7176cbbfbd3e574, d380dcde9a07ca5de4805dee11f58a98ec0ad6ff, d380dcde9a07ca5de4805dee11f58a98ec0ad6ff, d380dcde9a07ca5de4805dee11f58a98ec0ad6ff, d380dcde9a07ca5de4805dee11f58a98ec0ad6ff, c78a2baf5e1fe1b38121d6b54bab77ccb81a1a86, 5.4.19, 5.5.6unaffected
LinuxLinux5.6, 0, 5.4.176, 5.10.96, 5.15.19, 5.16.5, 5.17affected
Weakness

CWE details

No CWE listed

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