kunit: fix reference count leak in kfree_at_end
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
kunit: fix reference count leak in kfree_at_end
The reference counting issue happens in the normal path of kfree_at_end(). When kunit_alloc_and_get_resource() is invoked, the function forgets to handle the returned resource object, whose refcount increased inside, causing a refcount leak.
Fix this issue by calling kunit_alloc_resource() instead of kunit_alloc_and_get_resource().
Fixed the following when applying: Shuah Khan <skhan@linuxfoundation.org>
CHECK: Alignment should match open parenthesis + kunit_alloc_resource(test, NULL, kfree_res_free, GFP_KERNEL, (void *)to_free);
From the CVE record · Linux
The Linux kernel’s KUnit kfree_at_end() leaks a resource reference count because it does not handle the resource returned by kunit_alloc_and_get_resource(). The input does not describe an attacker-controlled path or specify access, authentication, or user-interaction requirements.
Engineers running the Linux kernel should check whether their kernel includes the affected KUnit code; affected versions are not specified.