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

> A use-after-free in the Linux kernel SMB client allows attackers to cause denial of service or execute code via race conditions during SMB2.1 signed mounts.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Dec 2024
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-55573, BELL-CVE-2024-53179, DEBIAN-CVE-2024-53179, GHSA-2qfq-q4fv-fp24, ROOT-OS-DEBIAN-11-CVE-2024-53179, ROOT-OS-DEBIAN-12-CVE-2024-53179, ROOT-OS-UBUNTU-2204-CVE-2024-53179, UBUNTU-CVE-2024-53179

## What is CVE-2024-53179?

CVE-2024-53179 is a critical use after free vulnerability in Linux kernel, published on 27 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2024-53179?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-53179?

Apply the vendor's patch.

## Is CVE-2024-53179 being exploited?

There is no known exploitation of CVE-2024-53179 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-53179 and fix it if it is affected.

What it is: CVE-2024-53179 is a critical use after free vulnerability in Linux kernel, published on 27 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-53179 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-53179/ (Markdown: https://insights.sbomify.com/CVE-2024-53179/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-53179
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-53179
- OSV: https://osv.dev/vulnerability/CVE-2024-53179

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-53179/
Summaries are generated and may contain mistakes; the official description above is the record.