Answer in brief
CVE-2026-45959 records a Unknown severity vulnerability in crypto: ccp - Fix a crash due to incorrect cleanup usage of kfree. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a71475582ada92ba021852bf3c2b40ab3718549b <9a3ace9b010ffd8c422c97844ae152f7c53d6b18 || >=a71475582ada92ba021852bf3c2b40ab3718549b <90f9090e3e744a8fe3bb6fa0e61f577347728b0b || >=a71475582ada92ba021852bf3c2b40ab3718549b <d5abcc33ee76bc26d58b39dc1a097e43a99dd438 | 9a3ace9b010ffd8c422c97844ae152f7c53d6b18, 90f9090e3e744a8fe3bb6fa0e61f577347728b0b, d5abcc33ee76bc26d58b39dc1a097e43a99dd438 |
| Linux/Linuxgeneric | 6.17 | Not reported |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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 { ... } **`.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-45959 records a Unknown severity vulnerability in crypto: ccp - Fix a crash due to incorrect cleanup usage of kfree. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a71475582ada92ba021852bf3c2b40ab3718549b <9a3ace9b010ffd8c422c97844ae152f7c53d6b18 || >=a71475582ada92ba021852bf3c2b40ab3718549b <90f9090e3e744a8fe3bb6fa0e61f577347728b0b || >=a71475582ada92ba021852bf3c2b40ab3718549b <d5abcc33ee76bc26d58b39dc1a097e43a99dd438 | 9a3ace9b010ffd8c422c97844ae152f7c53d6b18, 90f9090e3e744a8fe3bb6fa0e61f577347728b0b, d5abcc33ee76bc26d58b39dc1a097e43a99dd438 |
| Linux/Linuxgeneric | 6.17 | Not reported |
Published upstream
May 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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 { ... } **`.
Quoted source text, attributed separately from HOL analysis.