kunit/overflow: Fix UB in overflow_allocation_test
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/overflow: Fix UB in overflow_allocation_test
The 'device_name' array doesn't exist out of the 'overflow_allocation_test' function scope. However, it is being used as a driver name when calling 'kunit_driver_create' from 'kunit_device_register'. It produces the kernel panic with KASAN enabled.
Since this variable is used in one place only, remove it and pass the device name into kunit_device_register directly as an ascii string.
From the CVE record · Linux
The Linux kernel KUnit overflow_allocation_test uses a device name after its array goes out of scope. This can cause a kernel panic when KASAN is enabled. The input does not specify whether an attacker can trigger it or whether access or user interaction is required.
Engineers running the Linux kernel with KUnit overflow tests and KASAN enabled should check their installations; affected versions are not specified.