cve-2024-45818
Vulnerability from cvelistv5
Published
2024-12-19 12:00
Modified
2024-12-31 19:01
Severity ?
6.5 (Medium) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Summary
The hypervisor contains code to accelerate VGA memory accesses for HVM guests, when the (virtual) VGA is in "standard" mode. Locking involved there has an unusual discipline, leaving a lock acquired past the return from the function that acquired it. This behavior results in a problem when emulating an instruction with two memory accesses, both of which touch VGA memory (plus some further constraints which aren't relevant here). When emulating the 2nd access, the lock that is already being held would be attempted to be re-acquired, resulting in a deadlock. This deadlock was already found when the code was first introduced, but was analysed incorrectly and the fix was incomplete. Analysis in light of the new finding cannot find a way to make the existing locking discipline work. In staging, this logic has all been removed because it was discovered to be accidentally disabled since Xen 4.7. Therefore, we are fixing the locking problem by backporting the removal of most of the feature. Note that even with the feature disabled, the lock would still be acquired for any accesses to the VGA MMIO region.
References
security@xen.orghttps://xenbits.xenproject.org/xsa/advisory-463.html
af854a3a-2127-422b-91ae-364da2661108http://www.openwall.com/lists/oss-security/2024/11/12/2
af854a3a-2127-422b-91ae-364da2661108http://xenbits.xen.org/xsa/advisory-463.html
Impacted products
Vendor Product Version
Show details on NVD website

To clipboard 

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-12-19T12:04:41.161Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "url": "http://www.openwall.com/lists/oss-security/2024/11/12/2"
          },
          {
            "url": "http://xenbits.xen.org/xsa/advisory-463.html"
          }
        ],
        "title": "CVE Program Container"
      },
      {
        "metrics": [
          {
            "cvssV3_1": {
              "attackComplexity": "LOW",
              "attackVector": "LOCAL",
              "availabilityImpact": "NONE",
              "baseScore": 6.5,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "HIGH",
              "integrityImpact": "NONE",
              "privilegesRequired": "LOW",
              "scope": "CHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N",
              "version": "3.1"
            }
          },
          {
            "other": {
              "content": {
                "id": "CVE-2024-45818",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-12-31T18:59:24.741670Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "problemTypes": [
          {
            "descriptions": [
              {
                "cweId": "CWE-667",
                "description": "CWE-667 Improper Locking",
                "lang": "en",
                "type": "CWE"
              }
            ]
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-12-31T19:01:43.510Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unknown",
          "product": "Xen",
          "vendor": "Xen",
          "versions": [
            {
              "status": "unknown",
              "version": "consult Xen advisory XSA-463"
            }
          ]
        }
      ],
      "configurations": [
        {
          "lang": "en",
          "value": "Xen versions 4.6 through 4.19 are vulnerable.  Staging (4.20 dev) is\nnot vulnerable; as noted above, the functionality was already removed\nprior to the discovery of this issue.\n\nOnly x86 systems running HVM guests are vulnerable.  Architectures other\nthan x86 are not vulnerable.\n\nOnly HVM guests can leverage the vulnerability.  PVH and PV guests\ncannot leverage the vulnerability."
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "This issue was discovered by Manuel Andreas of Technical University of\nMunich."
        }
      ],
      "datePublic": "2024-11-12T12:00:00Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "The hypervisor contains code to accelerate VGA memory accesses for HVM\nguests, when the (virtual) VGA is in \"standard\" mode.  Locking involved\nthere has an unusual discipline, leaving a lock acquired past the\nreturn from the function that acquired it.  This behavior results in a\nproblem when emulating an instruction with two memory accesses, both of\nwhich touch VGA memory (plus some further constraints which aren\u0027t\nrelevant here).  When emulating the 2nd access, the lock that is already\nbeing held would be attempted to be re-acquired, resulting in a\ndeadlock.\n\nThis deadlock was already found when the code was first introduced, but\nwas analysed incorrectly and the fix was incomplete.  Analysis in light\nof the new finding cannot find a way to make the existing locking\ndiscipline work.\n\nIn staging, this logic has all been removed because it was discovered\nto be accidentally disabled since Xen 4.7.  Therefore, we are fixing the\nlocking problem by backporting the removal of most of the feature.  Note\nthat even with the feature disabled, the lock would still be acquired\nfor any accesses to the VGA MMIO region."
        }
      ],
      "impacts": [
        {
          "descriptions": [
            {
              "lang": "en",
              "value": "A (not necessarily malicious) HVM guest kernel can lock up the entire\nhost."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2024-12-19T12:00:41.413Z",
        "orgId": "23aa2041-22e1-471f-9209-9b7396fa234f",
        "shortName": "XEN"
      },
      "references": [
        {
          "url": "https://xenbits.xenproject.org/xsa/advisory-463.html"
        }
      ],
      "title": "Deadlock in x86 HVM standard VGA handling",
      "workarounds": [
        {
          "lang": "en",
          "value": "Running only PV or PVH guests will avoid this vulnerability."
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "23aa2041-22e1-471f-9209-9b7396fa234f",
    "assignerShortName": "XEN",
    "cveId": "CVE-2024-45818",
    "datePublished": "2024-12-19T12:00:41.413Z",
    "dateReserved": "2024-09-09T14:43:11.826Z",
    "dateUpdated": "2024-12-31T19:01:43.510Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "fkie_nvd": {
      "descriptions": "[{\"lang\": \"en\", \"value\": \"The hypervisor contains code to accelerate VGA memory accesses for HVM\\nguests, when the (virtual) VGA is in \\\"standard\\\" mode.  Locking involved\\nthere has an unusual discipline, leaving a lock acquired past the\\nreturn from the function that acquired it.  This behavior results in a\\nproblem when emulating an instruction with two memory accesses, both of\\nwhich touch VGA memory (plus some further constraints which aren\u0027t\\nrelevant here).  When emulating the 2nd access, the lock that is already\\nbeing held would be attempted to be re-acquired, resulting in a\\ndeadlock.\\n\\nThis deadlock was already found when the code was first introduced, but\\nwas analysed incorrectly and the fix was incomplete.  Analysis in light\\nof the new finding cannot find a way to make the existing locking\\ndiscipline work.\\n\\nIn staging, this logic has all been removed because it was discovered\\nto be accidentally disabled since Xen 4.7.  Therefore, we are fixing the\\nlocking problem by backporting the removal of most of the feature.  Note\\nthat even with the feature disabled, the lock would still be acquired\\nfor any accesses to the VGA MMIO region.\"}, {\"lang\": \"es\", \"value\": \"El hipervisor contiene c\\u00f3digo para acelerar los accesos a la memoria VGA para los invitados HVM, cuando el VGA (virtual) est\\u00e1 en modo \\\"est\\u00e1ndar\\\". El bloqueo involucrado all\\u00ed tiene una disciplina inusual, dejando un bloqueo adquirido m\\u00e1s all\\u00e1 del retorno de la funci\\u00f3n que lo adquiri\\u00f3. Este comportamiento genera un problema al emular una instrucci\\u00f3n con dos accesos a la memoria, ambos de los cuales tocan la memoria VGA (adem\\u00e1s de algunas restricciones adicionales que no son relevantes aqu\\u00ed). Al emular el segundo acceso, se intentar\\u00eda volver a adquirir el bloqueo que ya se mantiene, lo que resultar\\u00eda en un bloqueo. Este bloqueo ya se encontr\\u00f3 cuando se introdujo el c\\u00f3digo por primera vez, pero se analiz\\u00f3 incorrectamente y la soluci\\u00f3n fue incompleta. El an\\u00e1lisis a la luz del nuevo hallazgo no puede encontrar una manera de hacer que funcione la disciplina de bloqueo existente. En la etapa de preparaci\\u00f3n, se elimin\\u00f3 toda esta l\\u00f3gica porque se descubri\\u00f3 que se hab\\u00eda deshabilitado accidentalmente desde Xen 4.7. Por lo tanto, estamos solucionando el problema de bloqueo al incorporar la eliminaci\\u00f3n de la mayor parte de la funci\\u00f3n. Tenga en cuenta que incluso con la funci\\u00f3n deshabilitada, el bloqueo a\\u00fan se adquirir\\u00eda para cualquier acceso a la regi\\u00f3n MMIO de VGA.\"}]",
      "id": "CVE-2024-45818",
      "lastModified": "2024-12-31T19:15:46.603",
      "metrics": "{\"cvssMetricV31\": [{\"source\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"type\": \"Secondary\", \"cvssData\": {\"version\": \"3.1\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N\", \"baseScore\": 6.5, \"baseSeverity\": \"MEDIUM\", \"attackVector\": \"LOCAL\", \"attackComplexity\": \"LOW\", \"privilegesRequired\": \"LOW\", \"userInteraction\": \"NONE\", \"scope\": \"CHANGED\", \"confidentialityImpact\": \"HIGH\", \"integrityImpact\": \"NONE\", \"availabilityImpact\": \"NONE\"}, \"exploitabilityScore\": 2.0, \"impactScore\": 4.0}]}",
      "published": "2024-12-19T12:15:16.540",
      "references": "[{\"url\": \"https://xenbits.xenproject.org/xsa/advisory-463.html\", \"source\": \"security@xen.org\"}, {\"url\": \"http://www.openwall.com/lists/oss-security/2024/11/12/2\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}, {\"url\": \"http://xenbits.xen.org/xsa/advisory-463.html\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}]",
      "sourceIdentifier": "security@xen.org",
      "vulnStatus": "Awaiting Analysis",
      "weaknesses": "[{\"source\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"type\": \"Secondary\", \"description\": [{\"lang\": \"en\", \"value\": \"CWE-667\"}]}]"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-45818\",\"sourceIdentifier\":\"security@xen.org\",\"published\":\"2024-12-19T12:15:16.540\",\"lastModified\":\"2024-12-31T19:15:46.603\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"The hypervisor contains code to accelerate VGA memory accesses for HVM\\nguests, when the (virtual) VGA is in \\\"standard\\\" mode.  Locking involved\\nthere has an unusual discipline, leaving a lock acquired past the\\nreturn from the function that acquired it.  This behavior results in a\\nproblem when emulating an instruction with two memory accesses, both of\\nwhich touch VGA memory (plus some further constraints which aren\u0027t\\nrelevant here).  When emulating the 2nd access, the lock that is already\\nbeing held would be attempted to be re-acquired, resulting in a\\ndeadlock.\\n\\nThis deadlock was already found when the code was first introduced, but\\nwas analysed incorrectly and the fix was incomplete.  Analysis in light\\nof the new finding cannot find a way to make the existing locking\\ndiscipline work.\\n\\nIn staging, this logic has all been removed because it was discovered\\nto be accidentally disabled since Xen 4.7.  Therefore, we are fixing the\\nlocking problem by backporting the removal of most of the feature.  Note\\nthat even with the feature disabled, the lock would still be acquired\\nfor any accesses to the VGA MMIO region.\"},{\"lang\":\"es\",\"value\":\"El hipervisor contiene c\u00f3digo para acelerar los accesos a la memoria VGA para los invitados HVM, cuando el VGA (virtual) est\u00e1 en modo \\\"est\u00e1ndar\\\". El bloqueo involucrado all\u00ed tiene una disciplina inusual, dejando un bloqueo adquirido m\u00e1s all\u00e1 del retorno de la funci\u00f3n que lo adquiri\u00f3. Este comportamiento genera un problema al emular una instrucci\u00f3n con dos accesos a la memoria, ambos de los cuales tocan la memoria VGA (adem\u00e1s de algunas restricciones adicionales que no son relevantes aqu\u00ed). Al emular el segundo acceso, se intentar\u00eda volver a adquirir el bloqueo que ya se mantiene, lo que resultar\u00eda en un bloqueo. Este bloqueo ya se encontr\u00f3 cuando se introdujo el c\u00f3digo por primera vez, pero se analiz\u00f3 incorrectamente y la soluci\u00f3n fue incompleta. El an\u00e1lisis a la luz del nuevo hallazgo no puede encontrar una manera de hacer que funcione la disciplina de bloqueo existente. En la etapa de preparaci\u00f3n, se elimin\u00f3 toda esta l\u00f3gica porque se descubri\u00f3 que se hab\u00eda deshabilitado accidentalmente desde Xen 4.7. Por lo tanto, estamos solucionando el problema de bloqueo al incorporar la eliminaci\u00f3n de la mayor parte de la funci\u00f3n. Tenga en cuenta que incluso con la funci\u00f3n deshabilitada, el bloqueo a\u00fan se adquirir\u00eda para cualquier acceso a la regi\u00f3n MMIO de VGA.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N\",\"baseScore\":6.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"CHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":2.0,\"impactScore\":4.0}]},\"weaknesses\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-667\"}]}],\"references\":[{\"url\":\"https://xenbits.xenproject.org/xsa/advisory-463.html\",\"source\":\"security@xen.org\"},{\"url\":\"http://www.openwall.com/lists/oss-security/2024/11/12/2\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"},{\"url\":\"http://xenbits.xen.org/xsa/advisory-463.html\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"}]}}",
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"http://www.openwall.com/lists/oss-security/2024/11/12/2\"}, {\"url\": \"http://xenbits.xen.org/xsa/advisory-463.html\"}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2024-12-19T12:04:41.161Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"cvssV3_1\": {\"scope\": \"CHANGED\", \"version\": \"3.1\", \"baseScore\": 6.5, \"attackVector\": \"LOCAL\", \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N\", \"integrityImpact\": \"NONE\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"NONE\", \"privilegesRequired\": \"LOW\", \"confidentialityImpact\": \"HIGH\"}}, {\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-45818\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-12-31T18:59:24.741670Z\"}}}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-667\", \"description\": \"CWE-667 Improper Locking\"}]}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-12-31T19:01:38.432Z\"}}], \"cna\": {\"title\": \"Deadlock in x86 HVM standard VGA handling\", \"credits\": [{\"lang\": \"en\", \"type\": \"finder\", \"value\": \"This issue was discovered by Manuel Andreas of Technical University of\\nMunich.\"}], \"impacts\": [{\"descriptions\": [{\"lang\": \"en\", \"value\": \"A (not necessarily malicious) HVM guest kernel can lock up the entire\\nhost.\"}]}], \"affected\": [{\"vendor\": \"Xen\", \"product\": \"Xen\", \"versions\": [{\"status\": \"unknown\", \"version\": \"consult Xen advisory XSA-463\"}], \"defaultStatus\": \"unknown\"}], \"datePublic\": \"2024-11-12T12:00:00Z\", \"references\": [{\"url\": \"https://xenbits.xenproject.org/xsa/advisory-463.html\"}], \"workarounds\": [{\"lang\": \"en\", \"value\": \"Running only PV or PVH guests will avoid this vulnerability.\"}], \"descriptions\": [{\"lang\": \"en\", \"value\": \"The hypervisor contains code to accelerate VGA memory accesses for HVM\\nguests, when the (virtual) VGA is in \\\"standard\\\" mode.  Locking involved\\nthere has an unusual discipline, leaving a lock acquired past the\\nreturn from the function that acquired it.  This behavior results in a\\nproblem when emulating an instruction with two memory accesses, both of\\nwhich touch VGA memory (plus some further constraints which aren\u0027t\\nrelevant here).  When emulating the 2nd access, the lock that is already\\nbeing held would be attempted to be re-acquired, resulting in a\\ndeadlock.\\n\\nThis deadlock was already found when the code was first introduced, but\\nwas analysed incorrectly and the fix was incomplete.  Analysis in light\\nof the new finding cannot find a way to make the existing locking\\ndiscipline work.\\n\\nIn staging, this logic has all been removed because it was discovered\\nto be accidentally disabled since Xen 4.7.  Therefore, we are fixing the\\nlocking problem by backporting the removal of most of the feature.  Note\\nthat even with the feature disabled, the lock would still be acquired\\nfor any accesses to the VGA MMIO region.\"}], \"configurations\": [{\"lang\": \"en\", \"value\": \"Xen versions 4.6 through 4.19 are vulnerable.  Staging (4.20 dev) is\\nnot vulnerable; as noted above, the functionality was already removed\\nprior to the discovery of this issue.\\n\\nOnly x86 systems running HVM guests are vulnerable.  Architectures other\\nthan x86 are not vulnerable.\\n\\nOnly HVM guests can leverage the vulnerability.  PVH and PV guests\\ncannot leverage the vulnerability.\"}], \"providerMetadata\": {\"orgId\": \"23aa2041-22e1-471f-9209-9b7396fa234f\", \"shortName\": \"XEN\", \"dateUpdated\": \"2024-12-19T12:00:41.413Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2024-45818\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2024-12-31T19:01:43.510Z\", \"dateReserved\": \"2024-09-09T14:43:11.826Z\", \"assignerOrgId\": \"23aa2041-22e1-471f-9209-9b7396fa234f\", \"datePublished\": \"2024-12-19T12:00:41.413Z\", \"assignerShortName\": \"XEN\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.1"
    }
  }
}


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.