ksmbd: use aead_request_free to match aead_request_alloc
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 · < 46caeae23035192b9cc41872c827f30d0233f16e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: use aead_request_free to match aead_request_alloc
Use aead_request_free() instead of kfree() to properly free memory allocated by aead_request_alloc(). This ensures sensitive crypto data is zeroed before being freed.
From the CVE record · Linux
The Linux kernel's ksmbd component used kfree() to release memory allocated by aead_request_alloc(), rather than aead_request_free(), which zeros sensitive crypto data before freeing it. The input does not specify how an attacker could exploit this issue or whether access, authentication, or user interaction is required.
Engineers running Linux kernels with ksmbd should check their versions; affected versions were not provided.