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

CVE record · `CVE-2025-68310`

- **Identifiers:** `CVE-2025-68310`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 16 Dec 2025
- **Updated:** 11 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 16 Dec 2025, 15:39 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `4cdf2f4e24ff0d345fc36ef6d6aec059333a261e to before d0df2503bc3c2be385ca2fd96585daad1870c7c5` (git)
  - affected: `4cdf2f4e24ff0d345fc36ef6d6aec059333a261e to before b63c061be622b17b495cbf78a6d5f2d4c3147f8e` (git)
  - affected: `4cdf2f4e24ff0d345fc36ef6d6aec059333a261e to before 3591d56ea9bfd3e7fbbe70f749bdeed689d415f9` (git)
  - affected: `4cdf2f4e24ff0d345fc36ef6d6aec059333a261e to before 54f938d9f5693af8ed586a08db4af5d9da1f0f2d` (git)
  - affected: `4cdf2f4e24ff0d345fc36ef6d6aec059333a261e to before 0fd20f65df6aa430454a0deed8f43efa91c54835` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.16`
  - unaffected: `before 5.16` (semver)
  - unaffected: `6.1.159 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.117 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.58 to 6.12.*, inclusive` (semver)
  - unaffected: `6.17.8 to 6.17.*, inclusive` (semver)
  - unaffected: `6.18 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0021, the 10th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 16 Dec 2025. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2025-68310](https://www.cve.org/CVERecord?id=CVE-2025-68310)
- [NVD: CVE-2025-68310](https://nvd.nist.gov/vuln/detail/CVE-2025-68310)

### References from the CNA

- <https://git.kernel.org/stable/c/d0df2503bc3c2be385ca2fd96585daad1870c7c5>
- <https://git.kernel.org/stable/c/b63c061be622b17b495cbf78a6d5f2d4c3147f8e>
- <https://git.kernel.org/stable/c/3591d56ea9bfd3e7fbbe70f749bdeed689d415f9>
- <https://git.kernel.org/stable/c/54f938d9f5693af8ed586a08db4af5d9da1f0f2d>
- <https://git.kernel.org/stable/c/0fd20f65df6aa430454a0deed8f43efa91c54835>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2025-68310>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2025-68310/>. Everything for agents: <https://agentprime.io/llms.txt>.
