Skip to main content
VulnerabilityPublished Updated

CVE-2025-68209: Linux kernel · mlx5: Fix default values in create CQ

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in e5eba42f01340f73888dfe560be2806057c25913 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 12:55 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in e5eba42f01340f73888dfe560be2806057c25913, a39d334c9840705af69f0466f8f0129c366004ca, 08469f5393a1a39f26a6e2eb2e8c33187665c1f4 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Linux kernel to e5eba42f01340f73888dfe560be2806057c25913, a39d334c9840705af69f0466f8f0129c366004ca, 08469f5393a1a39f26a6e2eb2e8c33187665c1f4 or 1a7865e3e4de2830d8a9fe8c273dc10b248b7338.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ cdd04f4d4d71cbf93d0d9abe63bc838f47c467fa, < e5eba42f01340f73888dfe560be2806057c25913
Fixed in
  • e5eba42f01340f73888dfe560be2806057c25913
LinuxLinuxAffected
  • ≥ cdd04f4d4d71cbf93d0d9abe63bc838f47c467fa, < a39d334c9840705af69f0466f8f0129c366004ca
Fixed in
  • a39d334c9840705af69f0466f8f0129c366004ca
LinuxLinuxAffected
  • ≥ cdd04f4d4d71cbf93d0d9abe63bc838f47c467fa, < 08469f5393a1a39f26a6e2eb2e8c33187665c1f4
Fixed in
  • 08469f5393a1a39f26a6e2eb2e8c33187665c1f4
LinuxLinuxAffected
  • ≥ cdd04f4d4d71cbf93d0d9abe63bc838f47c467fa, < 1a7865e3e4de2830d8a9fe8c273dc10b248b7338
Fixed in
  • 1a7865e3e4de2830d8a9fe8c273dc10b248b7338
LinuxLinuxAffected
  • =6.0
Fixed in–

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.

References

Community reviews

Loading reviews…