Breaking News: Hijacked Releases of Microsoft’s Official agent-framework Steals Azure and CI Credentials
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2025-68310

kernel: Linux kernel: Denial of Service due to deadlock in PCI error recovery

Overview

Published
16 Dec 2025
Modified
17 Jun 2026
Medium CVE
0 Registry packages
232 OS packages
10 Linux distributions
Yes Fix available

Description

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

s390/pci: Avoid deadlock between PCI error recovery and mlx5 crdump

Do not block PCI config accesses through pci_cfg_access_lock() when executing the s390 variant of PCI error recovery: Acquire just device_lock() instead of pci_dev_lock() as powerpc's EEH and generig PCI AER processing do.

During error recovery testing a pair of tasks was reported to be hung:

mlx5_core 0000:00:00.1: mlx5_health_try_recover:338:(pid 5553): health recovery flow aborted, PCI reads still not working INFO: task kmcheck:72 blocked for more than 122 seconds. Not tainted 5.14.0-570.12.1.bringup7.el9.s390x #1 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kmcheck state:D stack:0 pid:72 tgid:72 ppid:2 flags:0x00000000 Call Trace: [<000000065256f030>] __schedule+0x2a0/0x590 [<000000065256f356>] schedule+0x36/0xe0 [<000000065256f572>] schedule_preempt_disabled+0x22/0x30 [<0000000652570a94>] __mutex_lock.constprop.0+0x484/0x8a8 [<000003ff800673a4>] mlx5_unload_one+0x34/0x58 [mlx5_core] [<000003ff8006745c>] mlx5_pci_err_detected+0x94/0x140 [mlx5_core] [<0000000652556c5a>] zpci_event_attempt_error_recovery+0xf2/0x398 [<0000000651b9184a>] __zpci_event_error+0x23a/0x2c0 INFO: task kworker/u1664:6:1514 blocked for more than 122 seconds. Not tainted 5.14.0-570.12.1.bringup7.el9.s390x #1 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:kworker/u1664:6 state:D stack:0 pid:1514 tgid:1514 ppid:2 flags:0x00000000 Workqueue: mlx5_health0000:00:00.0 mlx5_fw_fatal_reporter_err_work [mlx5_core] Call Trace: [<000000065256f030>] __schedule+0x2a0/0x590 [<000000065256f356>] schedule+0x36/0xe0 [<0000000652172e28>] pci_wait_cfg+0x80/0xe8 [<0000000652172f94>] pci_cfg_access_lock+0x74/0x88 [<000003ff800916b6>] mlx5_vsc_gw_lock+0x36/0x178 [mlx5_core] [<000003ff80098824>] mlx5_crdump_collect+0x34/0x1c8 [mlx5_core] [<000003ff80074b62>] mlx5_fw_fatal_reporter_dump+0x6a/0xe8 [mlx5_core] [<0000000652512242>] devlink_health_do_dump.part.0+0x82/0x168 [<0000000652513212>] devlink_health_report+0x19a/0x230 [<000003ff80075a12>] mlx5_fw_fatal_reporter_err_work+0xba/0x1b0 [mlx5_core]

No kernel log of the exact same error with an upstream kernel is available - but the very same deadlock situation can be constructed there, too:

  • task: kmcheck mlx5_unload_one() tries to acquire devlink lock while the PCI error recovery code has set pdev->block_cfg_access by way of pci_cfg_access_lock()
  • task: kworker mlx5_crdump_collect() tries to set block_cfg_access through pci_cfg_access_lock() while devlink_health_report() had acquired the devlink lock.

A similar deadlock situation can be reproduced by requesting a crdump with

devlink health dump show pci/<BDF> reporter fw_fatal

while PCI error recovery is executed on the same <BDF> physical function by mlx5_core's pci_error_handlers. On s390 this can be injected with

zpcictl --reset-fw <BDF>

Tests with this patch failed to reproduce that second deadlock situation, the devlink command is rejected with "kernel answers: Permission denied" - and we get a kernel log message of:

mlx5_core 1ed0:00:00.1: mlx5_crdump_collect:50:(pid 254382): crdump: failed to lock vsc gw err -5

because the config read of VSC_SEMAPHORE is rejected by the underlying hardware.

Two prior attempts to address this issue have been discussed and ultimately rejected [see link], with the primary argument that s390's implementation of PCI error recovery is imposing restrictions that neither powerpc's EEH nor PCI AER handling need. Tests show that PCI error recovery on s390 is running to completion even without blocking access to PCI config space.

Source: OX vulnerability database

Severity

5.5 · MEDIUM

CVSS 3.1 base score, scored by redhat.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 53 fixes

Photon OS 1 release · 1 package

fixed 1
bpftool
Photon OS fixes for CVE-2025-68310
ReleasePackageFixed in
5.0 bpftool +10 6.1.159-1.ph5

Red Hat 2 releases · 1 package

affected 2
bpftool
Red Hat fixes for CVE-2025-68310
ReleasePackageFixed in
8 bpftool +45 affected
9 bpftool +106 affected

SUSE Linux Enterprise 2 releases · 5 packages

fixed 7
kernel-livepatch-6-4-0-150700-7-54-rt kernel-livepatch-6-4-0-150700-53-55-default cluster-md-kmp-default kernel-default-base kernel-64kb
SUSE Linux Enterprise fixes for CVE-2025-68310
ReleasePackageFixed inAdvisory
15.7 kernel-livepatch-6-4-0-150700-7-54-rt 1-150700.1.3.1 SUSE-SU-2026:2217-1
15.7 kernel-livepatch-6-4-0-150700-53-55-default 1-150700.15.3.1 SUSE-SU-2026:2238-1
15.7 cluster-md-kmp-default +20 6.4.0-150700.53.55.1 SUSE-SU-2026:2238-1
15.7 kernel-default-base 6.4.0-150700.53.55.1.150700.17.33.1 SUSE-SU-2026:2238-1
16.0 cluster-md-kmp-default +2 6.12.0-160000.33.1 SUSE-SU-2026:21845-1
16.0 kernel-64kb +23 6.12.0-160000.33.1 SUSE-SU-2026:21860-1

1 more row

SUSE Linux Enterprise Micro 1 release · 2 packages

fixed 2
kernel-64kb kernel-default-base
SUSE Linux Enterprise Micro fixes for CVE-2025-68310
ReleasePackageFixed inAdvisory
6.2 kernel-64kb +11 6.12.0-160000.33.1 SUSE-SU-2026:21841-1
6.2 kernel-default-base 6.12.0-160000.33.1.160000.2.14 SUSE-SU-2026:21841-1

debian 4 releases · 2 packages

fixed 4
linux-6-1 linux
debian fixes for CVE-2025-68310
ReleasePackageFixed in
11 linux-6-1 6.1.159-1~deb11u1
12 linux 6.1.159-1
13 linux 6.12.63-1
14 linux 6.17.8-1

echo 1 release · 1 package

fixed 1
linux
echo fixes for CVE-2025-68310
ReleasePackageFixed in
linux 1

openSUSE Leap 1 release · 2 packages

fixed 2
cluster-md-kmp-64kb kernel-default-base
openSUSE Leap fixes for CVE-2025-68310
ReleasePackageFixed inAdvisory
16.0 cluster-md-kmp-64kb +74 6.12.0-160000.33.1 openSUSE-SU-2026:20826-1
16.0 kernel-default-base 6.12.0-160000.33.1.160000.2.14 openSUSE-SU-2026:20826-1

root.io debian 2 releases · 1 package

fixed 2
linux
root.io debian fixes for CVE-2025-68310
ReleasePackageFixed in
12 linux +1 6.1.159-1
13 linux +1 6.12.63-1

root.io ubuntu 2 releases · 1 package

fixed 2
linux
root.io ubuntu fixes for CVE-2025-68310
ReleasePackageFixed in
22.04 linux +1 5.15.0-179.189.root.io.88
24.04 linux +1 6.8.0-106.106

ubuntu 2 releases · 29 packages

affected 1 fixed 29
linux linux-oracle-6-8 linux-ibm-6-8 linux-nvidia-6-8 linux-aws-6-8 linux-azure-6-8 +23
ubuntu fixes for CVE-2025-68310
ReleasePackageFixed in
22.04 linux +16 affected
22.04 linux-oracle-6-8 6.8.0-1047.48~22.04.1
22.04 linux-ibm-6-8 6.8.0-1049.49~22.04.1
22.04 linux-nvidia-6-8 6.8.0-1049.52~22.04.1
22.04 linux-aws-6-8 6.8.0-1050.53~22.04.1
22.04 linux-azure-6-8 6.8.0-1051.57~22.04.1

24 more rows

References

Show all 25 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.