samples/damon/wsse: handle damon_start() failure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.517.2.57.3In the Linux kernel, the following vulnerability has been resolved:
samples/damon/wsse: handle damon_start() failure
Patch series "samples/damon: handle damon_{start,stop}() failures".
All DAMON sample modules are not correctly handling failures from damon_start(). Among those, mtier also has an additional problem for handling of damon_stop() failures. wsse and prcl also have a problem in their damon_call() failure handling. As a result, memory leaks, next DAMON operation disruptions, and use-after-free can happen. Fix those.
Note that only the damon_start() failure caused issues can reliably be reproduced. Reproducing those issues require the admin permission, though.
This patch (of 6):
damon_sample_wsse_start() callers assume it will clean up resources when it fails. And the function does the cleanup for context buildup failures. However, it is not doing the cleanup for damon_start() failure. As a result, when damon_start() fails, it leaks the memory for DAMON context. Free the context in case of the failure to fix the issues.
Note that the issue can reliably be reproduced because the module calls damon_start() in the exclusive mode. For example,
From the CVE record · Linux
The Linux kernel’s DAMON wsse sample module fails to free its context when damon_start() fails. A local user with administrator permission can repeatedly trigger a memory leak when another DAMON instance prevents the sample from starting in exclusive mode.
Administrators running Linux kernels with the DAMON wsse sample module should check their kernel against the vendor advisory; affected versions were not provided.