CVE-2022-49410: tracing: Fix potential double free in create_var_ref()
In the Linux kernel, the following vulnerability has been resolved:
tracing: Fix potential double free in create_var_ref()
In create_var_ref(), init_var_ref() is called to initialize the fields
of variable ref_field, which is allocated in the previous function call
to create_hist_field(). Function init_var_ref() allocates the
corresponding fields such as ref_field->system, but frees these fields
when the function encounters an error. The caller later calls
destroy_hist_field() to conduct error handling, which frees the fields
and the variable itself. This results in double free of the fields which
are already freed in the previous function.
Fix this by storing NULL to the corresponding fields when they are freed
in init_var_ref().
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory safety flaw in tracing code. A local user with some privileges could trigger a double free, which can crash a system or potentially compromise confidentiality, integrity, and availability. The supplied sources do not show active exploitation.
Executive priority
Treat as high priority for Linux fleets with local users, shared workloads, or sensitive hosts. No active exploitation is cited, but kernel double-free bugs can have severe business impact.
Technical view
create_var_ref() calls init_var_ref(), which may free ref_field subfields on error. Later error handling calls destroy_hist_field(), freeing the same fields again. The kernel fix NULLs freed fields in init_var_ref() to prevent double free during cleanup.
Likely exposure
Linux systems running affected kernel versions or downstream kernels missing the stable fixes. Exposure is local, requires low privileges, and depends on access to affected tracing functionality and distro backport status.
Exploitation context
The source bundle marks KEV as false and provides no cited evidence of active exploitation. CVSS 3.1 is 7.8 with local attack vector, low attack complexity, low privileges required, and high CIA impact.
Researcher notes
Evidence identifies CWE-415 in Linux tracing error handling. The bundle names stable kernel commits but does not provide exploit details. Validate against exact downstream kernel packages because vendor backports may not match upstream version numbers.
Mitigation direction
Apply vendor or distribution kernel updates containing the referenced stable fixes.
Confirm whether your distribution has backported the fix to its supported kernels.
Restrict untrusted local access where kernel updates cannot be applied promptly.
Monitor vendor advisories for any revised affected-version guidance.
Validation and detection
Inventory Linux kernel versions across servers, workstations, and container hosts.
Map running kernels to vendor advisories or the referenced stable commits.
Check whether tracing interfaces are exposed to non-administrative users.
Prioritize validation on multi-user systems and shared compute hosts.
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-415: 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.
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
8Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
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.