crypto: ccp - Fix a crash due to incorrect cleanup usage of kfree
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.14, 6.19.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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 { ... } **`.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From a71475582ada92ba021852bf3c2b40ab3718549b · fixed in 9a3ace9b010ffd8c422c97844ae152f7c53d6b18; From a71475582ada92ba021852bf3c2b40ab3718549b · fixed in 90f9090e3e744a8fe3bb6fa0e61f577347728b0b; From a71475582ada92ba021852bf3c2b40ab3718549b · fixed in d5abcc33ee76bc26d58b39dc1a097e43a99dd438
- Linux Linux
6.17
- KernelLinux
From 6.17.0 · fixed in 6.18.14; From 6.19.0 · fixed in 6.19.4