cve.bz

CVE-2025-68294 linux linux

7.8 highEPSS 0.1%Fix available

High (7.8) in linux linux. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: io_uring/net: ensure vectored buffer node import is tied to notification When support for vectored registered buffers was added, the import itself is using 'req' rather than the notification io_kiocb, sr->notif. For non-vectored imports, sr->notif is correctly used. This is important as the lifetime of the two may be different. Use the correct io_kiocb for the vectored buffer import.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 4th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-68294 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-68294?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-68294?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-68294 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-68294

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-68294](https://cve.bz/cve/badge/CVE-2025-68294.svg)](https://cve.bz/cve/CVE-2025-68294)

HTML:

<a href="https://cve.bz/cve/CVE-2025-68294"><img src="https://cve.bz/cve/badge/CVE-2025-68294.svg" alt="CVE-2025-68294"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.15 and later

Fixed in

ProductRelease lineFixed in
Linux6.176.17.11
Linuxlater releases6.18

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14linux6.17.11-1DEBIAN-CVE-2025-68294
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-68294
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-68294
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-68294
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2025-68294
Ubuntu24.04:LTSlinux-aws-6.176.17.0-1009.9~24.04.2UBUNTU-CVE-2025-68294 USN-8094-1
Ubuntu24.04:LTSlinux-azure-6.176.17.0-1010.10~24.04.1UBUNTU-CVE-2025-68294 USN-8094-4
Ubuntu24.04:LTSlinux-gcp-6.176.17.0-1009.9~24.04.3UBUNTU-CVE-2025-68294 USN-8094-2
Ubuntu24.04:LTSlinux-hwe-6.176.17.0-19.19~24.04.2UBUNTU-CVE-2025-68294 USN-8094-1
Ubuntu24.04:LTSlinux-nvidia-6.176.17.0-1018.18UBUNTU-CVE-2025-68294
Ubuntu24.04:LTSlinux-oem-6.176.17.0-1017.17UBUNTU-CVE-2025-68294 USN-8152-1
Ubuntu24.04:LTSlinux-oracle-6.176.17.0-1009.9~24.04.1UBUNTU-CVE-2025-68294 USN-8094-1
Ubuntu24.04:LTSlinux-riscv, linux-oem-6.8, linux-gcp-6.11 and 8 moreno fix listedUBUNTU-CVE-2025-68294
8 more for Ubuntu in the JSON and on Ubuntu's page.
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2025-68294

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A lifetime mismatch in io_uring's vectored registered buffer import ties the buffer to the wrong io_kiocb, potentially leading to use-after-free when the main request is freed before the associated notification. A local attacker able to use io_uring with vectored registered buffers may trigger memory corruption in kernel context. The issue is locally exploitable and may allow privilege escalation due to heap UAF in the networking zero-copy path.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-68294.

References

Check your stackJSON