CVSS 3.1
7.8 highCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HHigh (7.8) in linux linux. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExplain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | 6.10 and later |
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.12 | 6.12.58 |
| Linux | 6.17 | 6.17.8 |
| Linux | later releases | 6.18 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 13 | linux | 6.12.63-1 | DEBIAN-CVE-2025-68317 |
| Debian | 14 | linux | 6.17.8-1 | DEBIAN-CVE-2025-68317 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2025-68317 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2025-68317 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2025-68317 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 more | no fix listed | UBUNTU-CVE-2025-68317 |
| Ubuntu | 24.04:LTS | linux-aws-6.17, linux-oracle-6.17 | 6.17.0-1007.7~24.04.1 | UBUNTU-CVE-2025-68317 |
| Ubuntu | 24.04:LTS | linux-gcp-6.17 | 6.17.0-1008.8~24.04.1 | UBUNTU-CVE-2025-68317 |
| Ubuntu | 24.04:LTS | linux-nvidia-6.17 | 6.17.0-1008.8 | UBUNTU-CVE-2025-68317 |
| Ubuntu | 24.04:LTS | linux-oem-6.17 | 6.17.0-1011.11 | UBUNTU-CVE-2025-68317 USN-8048-1 |
| Ubuntu | 24.04:LTS | linux-riscv, linux-oem-6.8, linux-aws-6.14 and 17 more | no fix listed | UBUNTU-CVE-2025-68317 |
| Ubuntu | 25.10 | linux | 6.17.0-14.14 | UBUNTU-CVE-2025-68317 USN-8029-1 |
| Ubuntu | 25.10 | linux-aws, linux-gcp, linux-oracle | 6.17.0-1007.7 | UBUNTU-CVE-2025-68317 USN-8029-2 USN-8030-1 |
| Ubuntu | 25.10 | linux-azure, linux-raspi | 6.17.0-1008.8 | UBUNTU-CVE-2025-68317 USN-8029-1 USN-8029-3 |
| 5 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| SUSE | Linux Enterprise High Availability Extension 16.0 | kernel-default | 6.12.0-160000.9.1 | SUSE-SU-2026:20228-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | kernel-64kb, kernel-docs, kernel-syms and 6 more | 6.12.0-160000.9.1 | SUSE-SU-2026:20220-1 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | kernel-default-base | 6.12.0-160000.9.1.160000.2.6 | SUSE-SU-2026:20220-1 |
| SUSE | Linux Micro 6.2 | kernel-default-base | 6.12.0-160000.9.1.160000.2.6 | SUSE-SU-2026:20207-1 |
| SUSE | Linux Micro 6.2 | kernel-rt, kernel-64kb, kernel-source and 1 more | 6.12.0-160000.9.1 | SUSE-SU-2026:20207-1 |
| SUSE | Linux Micro Extras 6.2 | kernel-syms, kernel-obs-build | 6.12.0-160000.9.1 | SUSE-SU-2026:20564-1 |
| openSUSE | Leap 16.0 | kernel-default-base | 6.12.0-160000.9.1.160000.2.6 | openSUSE-SU-2026:20145-1 |
| openSUSE | Leap 16.0 | kernel-rt, dtb-aarch64, kernel-64kb and 9 more | 6.12.0-160000.9.1 | openSUSE-SU-2026:20145-1 |
| Alpaquita | 25 | linux-lts | 6.12.58-r0 | BELL-CVE-2025-68317 |
| Alpaquita | stream | linux-lts | 6.18.35-r1 | BELL-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 rates this Low.
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.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 6 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Not affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 9 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 9 | kernel-rt | Fix 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.