crypto: ccp - Fix a crash due to incorrect cleanup usage of kfree
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 90f9090e3e744a8fe3bb6fa0e61f577347728b0b, Kernel 9a3ace9b010ffd8c422c97844ae152f7c53d6b18 and Kernel d5abcc33ee76bc26d58b39dc1a097e43a99dd438.
In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Fix a crash due to incorrect cleanup usage of kfree Annotating a local pointer variable, which will be assigned with the kmalloc-family functions, with the `__cleanup(kfree)` attribute will make the address of the local variable, rather than the address returned by kmalloc, passed to kfree directly and lead to a crash due to invalid deallocation of stack address. According to other places in the repo, the correct usage should be `__free(kfree)`. The code coincidentally compiled because the parameter type `void *` of kfree is compatible with the desired type `struct { ... } **`.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.17, >=a71475582ada92ba021852bf3c2b40ab3718549b <90f9090e3e744a8fe3bb6fa0e61f577347728b0b, >=a71475582ada92ba021852bf3c2b40ab3718549b <9a3ace9b010ffd8c422c97844ae152f7c53d6b18, >=a71475582ada92ba021852bf3c2b40ab3718549b <d5abcc33ee76bc26d58b39dc1a097e43a99dd438 | 90f9090e3e744a8fe3bb6fa0e61f577347728b0b, 9a3ace9b010ffd8c422c97844ae152f7c53d6b18, d5abcc33ee76bc26d58b39dc1a097e43a99dd438 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket