CVE-2025-68209 (GCVE-0-2025-68209)
Vulnerability from cvelistv5
Published
2025-12-16 13:48
Modified
2025-12-16 13:48
Severity ?
Summary
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
Impacted products
Vendor Product Version
Linux Linux Version: cdd04f4d4d71cbf93d0d9abe63bc838f47c467fa
Version: cdd04f4d4d71cbf93d0d9abe63bc838f47c467fa
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/infiniband/hw/mlx5/cq.c",
            "drivers/net/ethernet/mellanox/mlx5/core/cq.c",
            "drivers/net/ethernet/mellanox/mlx5/core/en_main.c",
            "drivers/net/ethernet/mellanox/mlx5/core/fpga/conn.c",
            "drivers/net/ethernet/mellanox/mlx5/core/steering/hws/send.c",
            "drivers/net/ethernet/mellanox/mlx5/core/steering/sws/dr_send.c",
            "drivers/vdpa/mlx5/net/mlx5_vnet.c",
            "include/linux/mlx5/cq.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "08469f5393a1a39f26a6e2eb2e8c33187665c1f4",
              "status": "affected",
              "version": "cdd04f4d4d71cbf93d0d9abe63bc838f47c467fa",
              "versionType": "git"
            },
            {
              "lessThan": "e5eba42f01340f73888dfe560be2806057c25913",
              "status": "affected",
              "version": "cdd04f4d4d71cbf93d0d9abe63bc838f47c467fa",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/infiniband/hw/mlx5/cq.c",
            "drivers/net/ethernet/mellanox/mlx5/core/cq.c",
            "drivers/net/ethernet/mellanox/mlx5/core/en_main.c",
            "drivers/net/ethernet/mellanox/mlx5/core/fpga/conn.c",
            "drivers/net/ethernet/mellanox/mlx5/core/steering/hws/send.c",
            "drivers/net/ethernet/mellanox/mlx5/core/steering/sws/dr_send.c",
            "drivers/vdpa/mlx5/net/mlx5_vnet.c",
            "include/linux/mlx5/cq.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.0"
            },
            {
              "lessThan": "6.0",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.17.*",
              "status": "unaffected",
              "version": "6.17.9",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.18",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.17.9",
                  "versionStartIncluding": "6.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18",
                  "versionStartIncluding": "6.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmlx5: Fix default values in create CQ\n\nCurrently, CQs without a completion function are assigned the\nmlx5_add_cq_to_tasklet function by default. This is problematic since\nonly user CQs created through the mlx5_ib driver are intended to use\nthis function.\n\nAdditionally, all CQs that will use doorbells instead of polling for\ncompletions must call mlx5_cq_arm. However, the default CQ creation flow\nleaves a valid value in the CQ\u0027s arm_db field, allowing FW to send\ninterrupts to polling-only CQs in certain corner cases.\n\nThese two factors would allow a polling-only kernel CQ to be triggered\nby an EQ interrupt and call a completion function intended only for user\nCQs, causing a null pointer exception.\n\nSome areas in the driver have prevented this issue with one-off fixes\nbut did not address the root cause.\n\nThis patch fixes the described issue by adding defaults to the create CQ\nflow. It adds a default dummy completion function to protect against\nnull pointer exceptions, and it sets an invalid command sequence number\nby default in kernel CQs to prevent the FW from sending an interrupt to\nthe CQ until it is armed. User CQs are responsible for their own\ninitialization values.\n\nCallers of mlx5_core_create_cq are responsible for changing the\ncompletion function and arming the CQ per their needs."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-12-16T13:48:36.098Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/08469f5393a1a39f26a6e2eb2e8c33187665c1f4"
        },
        {
          "url": "https://git.kernel.org/stable/c/e5eba42f01340f73888dfe560be2806057c25913"
        }
      ],
      "title": "mlx5: Fix default values in create CQ",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-68209",
    "datePublished": "2025-12-16T13:48:36.098Z",
    "dateReserved": "2025-12-16T13:41:40.255Z",
    "dateUpdated": "2025-12-16T13:48:36.098Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2025-68209\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-12-16T14:15:53.813\",\"lastModified\":\"2025-12-18T15:08:25.907\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nmlx5: Fix default values in create CQ\\n\\nCurrently, CQs without a completion function are assigned the\\nmlx5_add_cq_to_tasklet function by default. This is problematic since\\nonly user CQs created through the mlx5_ib driver are intended to use\\nthis function.\\n\\nAdditionally, all CQs that will use doorbells instead of polling for\\ncompletions must call mlx5_cq_arm. However, the default CQ creation flow\\nleaves a valid value in the CQ\u0027s arm_db field, allowing FW to send\\ninterrupts to polling-only CQs in certain corner cases.\\n\\nThese two factors would allow a polling-only kernel CQ to be triggered\\nby an EQ interrupt and call a completion function intended only for user\\nCQs, causing a null pointer exception.\\n\\nSome areas in the driver have prevented this issue with one-off fixes\\nbut did not address the root cause.\\n\\nThis patch fixes the described issue by adding defaults to the create CQ\\nflow. It adds a default dummy completion function to protect against\\nnull pointer exceptions, and it sets an invalid command sequence number\\nby default in kernel CQs to prevent the FW from sending an interrupt to\\nthe CQ until it is armed. User CQs are responsible for their own\\ninitialization values.\\n\\nCallers of mlx5_core_create_cq are responsible for changing the\\ncompletion function and arming the CQ per their needs.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/08469f5393a1a39f26a6e2eb2e8c33187665c1f4\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/e5eba42f01340f73888dfe560be2806057c25913\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.