# CVE-2024-53094: RDMA/siw: Add sendpage_ok() check to disable MSG_SPLICE_PAGES

> A missing check in the Linux kernel RDMA/siw driver causes a kernel warning and potential instability when using MSG_SPLICE_PAGES, leading to denial of service.

- **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:** 21 Nov 2024
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-54598, AZL-54646, BELL-CVE-2024-53094, DEBIAN-CVE-2024-53094, GHSA-w7c6-4vwf-466q, ROOT-OS-DEBIAN-11-CVE-2024-53094, ROOT-OS-DEBIAN-12-CVE-2024-53094, ROOT-OS-UBUNTU-2204-CVE-2024-53094, UBUNTU-CVE-2024-53094

## What is CVE-2024-53094?

CVE-2024-53094 is a critical denial of service vulnerability in Linux kernel, published on 21 Nov 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:

RDMA/siw: Add sendpage_ok() check to disable MSG_SPLICE_PAGES

While running ISER over SIW, the initiator machine encounters a warning
from skb_splice_from_iter() indicating that a slab page is being used in
send_page. To address this, it is better to add a sendpage_ok() check
within the driver itself, and if it returns 0, then MSG_SPLICE_PAGES flag
should be disabled before entering the network stack.

A similar issue has been discussed for NVMe in this thread:
https://lore.kernel.org/all/20240530142417.146696-1-ofir.gal@volumez.com/

  WARNING: CPU: 0 PID: 5342 at net/core/skbuff.c:7140 skb_splice_from_iter+0x173/0x320
  Call Trace:
   tcp_sendmsg_locked+0x368/0xe40
   siw_tx_hdt+0x695/0xa40 [siw]
   siw_qp_sq_process+0x102/0xb00 [siw]
   siw_sq_resume+0x39/0x110 [siw]
   siw_run_sq+0x74/0x160 [siw]
   kthread+0xd2/0x100
   ret_from_fork+0x34/0x40
   ret_from_fork_asm+0x1a/0x30

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-53094 being exploited?

There is no known exploitation of CVE-2024-53094 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-53094 and fix it if it is affected.

What it is: CVE-2024-53094 is a critical denial of service vulnerability in Linux kernel, published on 21 Nov 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-53094 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-53094/ (Markdown: https://insights.sbomify.com/CVE-2024-53094/index.md)
```

## Sources

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

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