tracing: Fix potential double free in create_var_ref()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 067fe038e70f6e64960d26a79c4df5f1413d0f13 · < bd83ff3bbfb003832481c9bff999d12385f396ae| No fix yet |
| Linux Linux |
|
|
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().
From the CVE record · Linux
The Linux kernel tracing code can free the same fields twice when init_var_ref() encounters an error and its caller performs cleanup. The input does not specify how an attacker could trigger the error or whether access, authentication, or user interaction is required.
Anyone running the Linux kernel should check whether their version is affected; no affected versions are specified.