Answer in brief
CVE-2024-53179 records a Critical severity (CVSS 9.8) vulnerability in smb: client: fix use-after-free of signing key. 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=32811d242ff6f28da2ab18c90a15e32fd958e774 <0944c2596c2a3442735b5bb6714a17a16188a68f || >=32811d242ff6f28da2ab18c90a15e32fd958e774 <39619c65ab4bbb3e78c818f537687653e112764d || >=32811d242ff6f28da2ab18c90a15e32fd958e774 <0e2b654a3848bf9da3b0d54c1ccf3f1b8c635591 || >=32811d242ff6f28da2ab18c90a15e32fd958e774 <343d7fe6df9e247671440a932b6a73af4fa86d95 | 0944c2596c2a3442735b5bb6714a17a16188a68f, 39619c65ab4bbb3e78c818f537687653e112764d, 0e2b654a3848bf9da3b0d54c1ccf3f1b8c635591, 343d7fe6df9e247671440a932b6a73af4fa86d95 |
| Linux/Linuxgeneric | 3.12 | Not reported |
Published upstream
Dec 27, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 30, 2026
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix use-after-free of signing key Customers have reported use-after-free in @ses->auth_key.response with SMB2.1 + sign mounts which occurs due to following race: task A task B cifs_mount() dfs_mount_share() get_session() cifs_mount_get_session() cifs_send_recv() cifs_get_smb_ses() compound_send_recv() cifs_setup_session() smb2_setup_request() kfree_sensitive() smb2_calc_signature() crypto_shash_setkey() *UAF* Fix this by ensuring that we have a valid @ses->auth_key.response by checking whether @ses->ses_status is SES_GOOD or SES_EXITING with @ses->ses_lock held. After commit 24a9799aa8ef ("smb: client: fix UAF in smb2_reconnect_server()"), we made sure to call ->logoff() only when @ses was known to be good (e.g. valid ->auth_key.response), so it's safe to access signing key when @ses->ses_status == SES_EXITING.
Quoted source text, attributed separately from HOL analysis.