cve.bz

CVE-2025-68317 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/zctx: check chained notif contexts Send zc only links ubuf_info for requests coming from the same context. There are some ambiguous syz reports, so let's check the assumption on notification completion.

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.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
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-68317 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-68317?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-68317?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-68317 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-68317

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-68317](https://cve.bz/cve/badge/CVE-2025-68317.svg)](https://cve.bz/cve/CVE-2025-68317)

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.10 and later

Fixed in

ProductRelease lineFixed in
Linux6.126.12.58
Linux6.176.17.8
Linuxlater releases6.18

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13linux6.12.63-1DEBIAN-CVE-2025-68317
Debian14linux6.17.8-1DEBIAN-CVE-2025-68317
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2025-68317
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2025-68317
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2025-68317
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2025-68317
Ubuntu24.04:LTSlinux-aws-6.17, linux-oracle-6.176.17.0-1007.7~24.04.1UBUNTU-CVE-2025-68317
Ubuntu24.04:LTSlinux-gcp-6.176.17.0-1008.8~24.04.1UBUNTU-CVE-2025-68317
Ubuntu24.04:LTSlinux-nvidia-6.176.17.0-1008.8UBUNTU-CVE-2025-68317
Ubuntu24.04:LTSlinux-oem-6.176.17.0-1011.11UBUNTU-CVE-2025-68317 USN-8048-1
Ubuntu24.04:LTSlinux-riscv, linux-oem-6.8, linux-aws-6.14 and 17 moreno fix listedUBUNTU-CVE-2025-68317
Ubuntu25.10linux6.17.0-14.14UBUNTU-CVE-2025-68317 USN-8029-1
Ubuntu25.10linux-aws, linux-gcp, linux-oracle6.17.0-1007.7UBUNTU-CVE-2025-68317 USN-8029-2 USN-8030-1
Ubuntu25.10linux-azure, linux-raspi6.17.0-1008.8UBUNTU-CVE-2025-68317 USN-8029-1 USN-8029-3
5 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Availability Extension 16.0kernel-default6.12.0-160000.9.1SUSE-SU-2026:20228-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-64kb, kernel-docs, kernel-syms and 6 more6.12.0-160000.9.1SUSE-SU-2026:20220-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0kernel-default-base6.12.0-160000.9.1.160000.2.6SUSE-SU-2026:20220-1
SUSELinux Micro 6.2kernel-default-base6.12.0-160000.9.1.160000.2.6SUSE-SU-2026:20207-1
SUSELinux Micro 6.2kernel-rt, kernel-64kb, kernel-source and 1 more6.12.0-160000.9.1SUSE-SU-2026:20207-1
SUSELinux Micro Extras 6.2kernel-syms, kernel-obs-build6.12.0-160000.9.1SUSE-SU-2026:20564-1
openSUSELeap 16.0kernel-default-base6.12.0-160000.9.1.160000.2.6openSUSE-SU-2026:20145-1
openSUSELeap 16.0kernel-rt, dtb-aarch64, kernel-64kb and 9 more6.12.0-160000.9.1openSUSE-SU-2026:20145-1
Alpaquita25linux-lts6.12.58-r0BELL-CVE-2025-68317
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2025-68317

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

Red Hat

Red Hat rates this Low.

Red Hat's statement

A low impact denial-of-service flaw was found in the Linux kernel's io_uring zero-copy send notification handling (io_uring/notif.c). The send zero-copy code links ubuf_info notification structures only for requests originating from the same zero-copy context, but that assumption was not validated when chained notifications completed. A local attacker able to submit io_uring requests could exploit this improper handling of chained notification contexts to cause a denial of service. This flaw affects the kernels shipped in Red Hat Enterprise Linux 9 (kernel and kernel-rt) and Red Hat Enterprise Linux 10 (kernel); Red Hat Enterprise Linux 6, 7, and 8, and Red Hat In-Vehicle OS 1.1 are not affected because the vulnerable code is not present in those kernels. Because this flaw is rated Low severity, the fix for the affected Red Hat Enterprise Linux 9 and 10 streams is deferred to a future scheduled kernel update; the residual risk is a local user causing a denial of service, and only on systems where io_uring has been explicitly enabled by an administrator, since in the default Red Hat Enterprise Linux kernel io_uring is disabled and cannot be used unless enabled through the kernel.io_uring_disabled sysctl parameter. Red Hat assesses the severity of this flaw as Low (CVSS 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), which differs from the upstream CVE record severity of 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H): the available technical evidence supports an availability-only impact, with no demonstrated confidentiality or integrity impact.

Red Hat's mitigation

This flaw can only be triggered through the io_uring interface, which is disabled by default in Red Hat Enterprise Linux 9 and 10 (kernel.io_uring_disabled=2); no action is needed on systems where io_uring has not been explicitly enabled. On systems where an administrator has enabled io_uring, exploitation can be prevented by disabling it again: set the kernel.io_uring_disabled sysctl to 2, for example by running `sysctl -w kernel.io_uring_disabled=2`, and make the setting persistent via /etc/sysctl.conf or a file under /etc/sysctl.d/. With this setting, io_uring_setup() fails with -EPERM for all processes; note that applications relying on io_uring are affected, and io_uring instances that already exist at the time of the change can still be used.

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 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

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-68317.

References

Check your stackJSON