cve-2024-43864
Vulnerability from cvelistv5
Published
2024-08-20 23:45
Modified
2024-11-05 09:41
Severity ?
Summary
net/mlx5e: Fix CT entry update leaks of modify header context
Impacted products
Vendor Product Version
Linux Linux Version: 6.3
Show details on NVD website


{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2024-43864",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-09-10T16:06:42.010575Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-09-12T17:33:19.476Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/net/ethernet/mellanox/mlx5/core/en/tc_ct.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "daab2cc17b6b",
              "status": "affected",
              "version": "94ceffb48eac",
              "versionType": "git"
            },
            {
              "lessThan": "89064d09c56b",
              "status": "affected",
              "version": "94ceffb48eac",
              "versionType": "git"
            },
            {
              "lessThan": "025f2b85a5e5",
              "status": "affected",
              "version": "94ceffb48eac",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/net/ethernet/mellanox/mlx5/core/en/tc_ct.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.3"
            },
            {
              "lessThan": "6.3",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.45",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.10.*",
              "status": "unaffected",
              "version": "6.10.4",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.11",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Fix CT entry update leaks of modify header context\n\nThe cited commit allocates a new modify header to replace the old\none when updating CT entry. But if failed to allocate a new one, eg.\nexceed the max number firmware can support, modify header will be\nan error pointer that will trigger a panic when deallocating it. And\nthe old modify header point is copied to old attr. When the old\nattr is freed, the old modify header is lost.\n\nFix it by restoring the old attr to attr when failed to allocate a\nnew modify header context. So when the CT entry is freed, the right\nmodify header context will be freed. And the panic of accessing\nerror pointer is also fixed."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2024-11-05T09:41:22.846Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/daab2cc17b6b6ab158566bba037e9551fd432b59"
        },
        {
          "url": "https://git.kernel.org/stable/c/89064d09c56b44c668509bf793c410484f63f5ad"
        },
        {
          "url": "https://git.kernel.org/stable/c/025f2b85a5e5a46df14ecf162c3c80a957a36d0b"
        }
      ],
      "title": "net/mlx5e: Fix CT entry update leaks of modify header context",
      "x_generator": {
        "engine": "bippy-9e1c9544281a"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-43864",
    "datePublished": "2024-08-20T23:45:28.833Z",
    "dateReserved": "2024-08-17T09:11:59.279Z",
    "dateUpdated": "2024-11-05T09:41:22.846Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-43864\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-08-21T00:15:04.910\",\"lastModified\":\"2024-08-21T12:30:33.697\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nnet/mlx5e: Fix CT entry update leaks of modify header context\\n\\nThe cited commit allocates a new modify header to replace the old\\none when updating CT entry. But if failed to allocate a new one, eg.\\nexceed the max number firmware can support, modify header will be\\nan error pointer that will trigger a panic when deallocating it. And\\nthe old modify header point is copied to old attr. When the old\\nattr is freed, the old modify header is lost.\\n\\nFix it by restoring the old attr to attr when failed to allocate a\\nnew modify header context. So when the CT entry is freed, the right\\nmodify header context will be freed. And the panic of accessing\\nerror pointer is also fixed.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: net/mlx5e: corrige las fugas de actualizaci\u00f3n de la entrada CT del contexto del encabezado de modificaci\u00f3n. El commit citada asigna un nuevo encabezado de modificaci\u00f3n para reemplazar el anterior al actualizar la entrada CT. Pero si no se pudo asignar uno nuevo, por ejemplo. Si excede el n\u00famero m\u00e1ximo que el firmware puede admitir, modificar el encabezado ser\u00e1 un indicador de error que provocar\u00e1 p\u00e1nico al desasignarlo. Y el punto de encabezado de modificaci\u00f3n anterior se copia al atributo anterior. Cuando se libera el antiguo atributo, el antiguo encabezado de modificaci\u00f3n se pierde. Solucionelo restaurando el antiguo atributo a attr cuando no se pudo asignar un nuevo contexto de encabezado de modificaci\u00f3n. Entonces, cuando se libera la entrada CT, se liberar\u00e1 el contexto del encabezado de modificaci\u00f3n derecho. Y el p\u00e1nico al acceder al puntero de error tambi\u00e9n se soluciona.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/025f2b85a5e5a46df14ecf162c3c80a957a36d0b\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/89064d09c56b44c668509bf793c410484f63f5ad\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/daab2cc17b6b6ab158566bba037e9551fd432b59\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.
  • 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.