# CVE-2025-68234: io_uring/cmd_net: fix wrong argument types for skb_queue_splice()

> Incorrect argument order in io_uring network command handling causes improper socket queue splicing, potentially leading to undefined behavior or data corruption.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Dec 2025
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2025-68234, DEBIAN-CVE-2025-68234, GHSA-q84f-vw64-jf47, UBUNTU-CVE-2025-68234

## What is CVE-2025-68234?

CVE-2025-68234 is a high-severity vulnerability in Linux, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

io_uring/cmd_net: fix wrong argument types for skb_queue_splice()

If timestamp retriving needs to be retried and the local list of
SKB's already has entries, then it's spliced back into the socket
queue. However, the arguments for the splice helper are transposed,
causing exactly the wrong direction of splicing into the on-stack
list. Fix that up.

## Which versions are affected by CVE-2025-68234?


## How do I fix CVE-2025-68234?

Apply the vendor's patch.

## Is CVE-2025-68234 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68234 and fix it if it is affected.

What it is: CVE-2025-68234 is a high-severity vulnerability in Linux, published on 16 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-68234 in the wild and no public exploit code.

Affected product: Linux. 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-2025-68234/ (Markdown: https://insights.sbomify.com/CVE-2025-68234/index.md)
```

## Sources

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

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