Answer in brief
CVE-2024-50152 records a Critical severity (CVSS 9.8) vulnerability in smb: client: fix possible double free in smb2_set_ea(). 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.
CVSS is 9.8. 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 | >=433042a91f9373241307725b52de573933ffedbf <b1813c220b76f60b1727984794377c4aa849d4c1 || >=4f1fffa2376922f3d1d506e49c0fd445b023a28e <c9f758ecf2562dfdd4adf12c22921b5de8366123 || >=4f1fffa2376922f3d1d506e49c0fd445b023a28e <19ebc1e6cab334a8193398d4152deb76019b5d34 || >=6.6.32 <6.6.59 | b1813c220b76f60b1727984794377c4aa849d4c1, c9f758ecf2562dfdd4adf12c22921b5de8366123, 19ebc1e6cab334a8193398d4152deb76019b5d34, 6.6.59 |
| Linux/Linuxgeneric | 6.8 | Not reported |
Published upstream
Nov 7, 2024
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: smb: client: fix possible double free in smb2_set_ea() Clang static checker(scan-build) warning： fs/smb/client/smb2ops.c:1304:2: Attempt to free released memory. 1304 | kfree(ea); | ^~~~~~~~~ There is a double free in such case: 'ea is initialized to NULL' -> 'first successful memory allocation for ea' -> 'something failed, goto sea_exit' -> 'first memory release for ea' -> 'goto replay_again' -> 'second goto sea_exit before allocate memory for ea' -> 'second memory release for ea resulted in double free'. Re-initialie 'ea' to NULL near to the replay_again label, it can fix this double free problem.
Quoted source text, attributed separately from HOL analysis.