cve-2024-57876
Vulnerability from cvelistv5
Published
2025-01-11 14:49
Modified
2025-01-20 06:28
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/dp_mst: Fix resetting msg rx state after topology removal If the MST topology is removed during the reception of an MST down reply or MST up request sideband message, the drm_dp_mst_topology_mgr::up_req_recv/down_rep_recv states could be reset from one thread via drm_dp_mst_topology_mgr_set_mst(false), racing with the reading/parsing of the message from another thread via drm_dp_mst_handle_down_rep() or drm_dp_mst_handle_up_req(). The race is possible since the reader/parser doesn't hold any lock while accessing the reception state. This in turn can lead to a memory corruption in the reader/parser as described by commit bd2fccac61b4 ("drm/dp_mst: Fix MST sideband message body length check"). Fix the above by resetting the message reception state if needed before reading/parsing a message. Another solution would be to hold the drm_dp_mst_topology_mgr::lock for the whole duration of the message reception/parsing in drm_dp_mst_handle_down_rep() and drm_dp_mst_handle_up_req(), however this would require a bigger change. Since the fix is also needed for stable, opting for the simpler solution in this patch.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/94b33b2d7640e807869451384eb88321dd0ffbd4
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/a6fa67d26de385c3c7a23c1e109a0e23bfda4ec7
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/be826b4451fd187a7c0b04be4f8243d5df6e0450
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/d834d20d2e86c52ed5cab41763fa61e6071680ef
Impacted products
Vendor Product Version
Linux Linux Version: b30fcedeba643ca16eaa6212c1245598b7cd830d
Version: 1d082618bbf3b6755b8cc68c0a8122af2842d593
Version: 1d082618bbf3b6755b8cc68c0a8122af2842d593
Version: 1d082618bbf3b6755b8cc68c0a8122af2842d593
 Create a notification for this product.
   Linux Linux Version: 6.3
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/display/drm_dp_mst_topology.c",
            "include/drm/display/drm_dp_mst_helper.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "94b33b2d7640e807869451384eb88321dd0ffbd4",
              "status": "affected",
              "version": "b30fcedeba643ca16eaa6212c1245598b7cd830d",
              "versionType": "git"
            },
            {
              "lessThan": "d834d20d2e86c52ed5cab41763fa61e6071680ef",
              "status": "affected",
              "version": "1d082618bbf3b6755b8cc68c0a8122af2842d593",
              "versionType": "git"
            },
            {
              "lessThan": "be826b4451fd187a7c0b04be4f8243d5df6e0450",
              "status": "affected",
              "version": "1d082618bbf3b6755b8cc68c0a8122af2842d593",
              "versionType": "git"
            },
            {
              "lessThan": "a6fa67d26de385c3c7a23c1e109a0e23bfda4ec7",
              "status": "affected",
              "version": "1d082618bbf3b6755b8cc68c0a8122af2842d593",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/display/drm_dp_mst_topology.c",
            "include/drm/display/drm_dp_mst_helper.h"
          ],
          "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.1.*",
              "status": "unaffected",
              "version": "6.1.120",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.66",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.13",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/dp_mst: Fix resetting msg rx state after topology removal\n\nIf the MST topology is removed during the reception of an MST down reply\nor MST up request sideband message, the\ndrm_dp_mst_topology_mgr::up_req_recv/down_rep_recv states could be reset\nfrom one thread via drm_dp_mst_topology_mgr_set_mst(false), racing with\nthe reading/parsing of the message from another thread via\ndrm_dp_mst_handle_down_rep() or drm_dp_mst_handle_up_req(). The race is\npossible since the reader/parser doesn\u0027t hold any lock while accessing\nthe reception state. This in turn can lead to a memory corruption in the\nreader/parser as described by commit bd2fccac61b4 (\"drm/dp_mst: Fix MST\nsideband message body length check\").\n\nFix the above by resetting the message reception state if needed before\nreading/parsing a message. Another solution would be to hold the\ndrm_dp_mst_topology_mgr::lock for the whole duration of the message\nreception/parsing in drm_dp_mst_handle_down_rep() and\ndrm_dp_mst_handle_up_req(), however this would require a bigger change.\nSince the fix is also needed for stable, opting for the simpler solution\nin this patch."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-01-20T06:28:41.699Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/94b33b2d7640e807869451384eb88321dd0ffbd4"
        },
        {
          "url": "https://git.kernel.org/stable/c/d834d20d2e86c52ed5cab41763fa61e6071680ef"
        },
        {
          "url": "https://git.kernel.org/stable/c/be826b4451fd187a7c0b04be4f8243d5df6e0450"
        },
        {
          "url": "https://git.kernel.org/stable/c/a6fa67d26de385c3c7a23c1e109a0e23bfda4ec7"
        }
      ],
      "title": "drm/dp_mst: Fix resetting msg rx state after topology removal",
      "x_generator": {
        "engine": "bippy-5f407fcff5a0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-57876",
    "datePublished": "2025-01-11T14:49:02.550Z",
    "dateReserved": "2025-01-11T14:45:42.023Z",
    "dateUpdated": "2025-01-20T06:28:41.699Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-57876\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-01-11T15:15:07.930\",\"lastModified\":\"2025-01-11T15:15:07.930\",\"vulnStatus\":\"Received\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\ndrm/dp_mst: Fix resetting msg rx state after topology removal\\n\\nIf the MST topology is removed during the reception of an MST down reply\\nor MST up request sideband message, the\\ndrm_dp_mst_topology_mgr::up_req_recv/down_rep_recv states could be reset\\nfrom one thread via drm_dp_mst_topology_mgr_set_mst(false), racing with\\nthe reading/parsing of the message from another thread via\\ndrm_dp_mst_handle_down_rep() or drm_dp_mst_handle_up_req(). The race is\\npossible since the reader/parser doesn\u0027t hold any lock while accessing\\nthe reception state. This in turn can lead to a memory corruption in the\\nreader/parser as described by commit bd2fccac61b4 (\\\"drm/dp_mst: Fix MST\\nsideband message body length check\\\").\\n\\nFix the above by resetting the message reception state if needed before\\nreading/parsing a message. Another solution would be to hold the\\ndrm_dp_mst_topology_mgr::lock for the whole duration of the message\\nreception/parsing in drm_dp_mst_handle_down_rep() and\\ndrm_dp_mst_handle_up_req(), however this would require a bigger change.\\nSince the fix is also needed for stable, opting for the simpler solution\\nin this patch.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/94b33b2d7640e807869451384eb88321dd0ffbd4\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/a6fa67d26de385c3c7a23c1e109a0e23bfda4ec7\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/be826b4451fd187a7c0b04be4f8243d5df6e0450\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/d834d20d2e86c52ed5cab41763fa61e6071680ef\",\"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.
  • 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.