params: fix charp corruption on allocation failure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e180a6b7759a99a28cbcce3547c4c80822cb6c2a · < 704ecd010d4a9b33160e40b74eb402f6b86a18e0| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
params: fix charp corruption on allocation failure
param_set_charp() stores charp parameters in allocated memory after slab is available, and releases the previous value when the parameter is updated.
The previous value is released before the replacement allocation succeeds. If kmalloc_parameter() fails, the setter returns -ENOMEM with the parameter left as NULL.
Failing zswap's compressor update before zswap is initialized can later trigger:
BUG: kernel NULL pointer dereference, address: 0000000000000000 RIP: 0010:strcmp+0x10/0x30 Call Trace: zswap_setup+0x3b1/0x490 zswap_enabled_param_set+0x5b/0xa0 param_attr_store+0x93/0xe0 module_attr_store+0x1c/0x30 kernfs_fop_write_iter+0x116/0x1f0
Allocate and copy the replacement first, then replace the parameter value only after allocation succeeds.
From the CVE record · Linux
The Linux kernel's charp parameter setter can leave a parameter NULL if allocation fails during an update. A local actor able to update zswap's compressor parameter before zswap is initialized could trigger a kernel NULL-pointer dereference if that allocation fails.
Engineers running Linux kernels with the affected charp parameter handling should check their kernel versions against the vendor advisory; affected versions were not provided.