CVE-2025-68209mlx5: Fix default values in create CQ
- —Not scoredno CVSS score yet
- 0.22%Exploitation in 30 daysEPSS · top 87% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: mlx5: Fix default values in create CQ Currently, CQs without a completion function are assigned the mlx5_add_cq_to_tasklet function by default. This is problematic since only user CQs created through the mlx5_ib driver are intended to use this function. Additionally, all CQs that will use doorbells instead of polling for completions must call mlx5_cq_arm. However, the default CQ creation flow leaves a valid value in the CQ's arm_db field, allowing FW to send interrupts to polling-only CQs in certain corner cases. These two factors would allow a polling-only kernel CQ to be triggered by an EQ interrupt and call a completion function intended only for user CQs, causing a null pointer exception. Some areas in the driver have prevented this issue with one-off fixes but did not address the root cause. This patch fixes the described issue by adding defaults to the create CQ flow. It adds a default dummy completion function to protect against null pointer exceptions, and it sets an invalid command sequence number by default in kernel CQs to prevent the FW from sending an interrupt to the CQ until it is armed. User CQs are responsible for their own initialization values. Callers of mlx5_core_create_cq are responsible for changing the completion function and arming the CQ per their needs.
Timeline
ID reserved
By Linux
Published
- 11 months later
· 11 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.
- EPSS (exploitation in 30 days)
- 0.22% · top 87% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected cdd04f4d4d71cbf93d0d9abe63bc838f47c467fa – < 5c08079c3e5a3c1573afcb5643b5d296865d1170
- affected cdd04f4d4d71cbf93d0d9abe63bc838f47c467fa – < 1a7865e3e4de2830d8a9fe8c273dc10b248b7338
- affected cdd04f4d4d71cbf93d0d9abe63bc838f47c467fa – < a39d334c9840705af69f0466f8f0129c366004ca
- affected cdd04f4d4d71cbf93d0d9abe63bc838f47c467fa – < 08469f5393a1a39f26a6e2eb2e8c33187665c1f4
- affected cdd04f4d4d71cbf93d0d9abe63bc838f47c467fa – < e5eba42f01340f73888dfe560be2806057c25913
- affected 6.0
- unaffected < 6.0
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.17.9 – ≤ 6.17.*
- unaffected 6.18 – ≤ *
References
References5
- https://git.kernel.org/stable/c/5c08079c3e5a3c1573afcb5643b5d296865d1170 (opens in a new tab)
- https://git.kernel.org/stable/c/1a7865e3e4de2830d8a9fe8c273dc10b248b7338 (opens in a new tab)
- https://git.kernel.org/stable/c/a39d334c9840705af69f0466f8f0129c366004ca (opens in a new tab)
- https://git.kernel.org/stable/c/08469f5393a1a39f26a6e2eb2e8c33187665c1f4 (opens in a new tab)
- https://git.kernel.org/stable/c/e5eba42f01340f73888dfe560be2806057c25913 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-203687 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-68209)Record last updated .