nvd-json-data-feeds/CVE-2021/CVE-2021-469xx/CVE-2021-46907.json

{
  "id": "CVE-2021-46907",
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "published": "2024-02-27T07:15:06.543",
  "lastModified": "2024-02-27T14:20:06.637",
  "vulnStatus": "Awaiting Analysis",
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: VMX: Don't use vcpu->run->internal.ndata as an array index\n\n__vmx_handle_exit() uses vcpu->run->internal.ndata as an index for\nan array access.  Since vcpu->run is (can be) mapped to a user address\nspace with a writer permission, the 'ndata' could be updated by the\nuser process at anytime (the user process can set it to outside the\nbounds of the array).\nSo, it is not safe that __vmx_handle_exit() uses the 'ndata' that way."
    },
    {
      "lang": "es",
      "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: KVM: VMX: No use vcpu->run->internal.ndata como \u00edndice de matriz __vmx_handle_exit() usa vcpu->run->internal.ndata como \u00edndice para un acceso a la matriz. Dado que vcpu->run est\u00e1 (puede) asignarse a un espacio de direcciones de usuario con permiso de escritor, el proceso de usuario podr\u00eda actualizar el 'ndata' en cualquier momento (el proceso de usuario puede configurarlo fuera de los l\u00edmites de la matriz). Por lo tanto, no es seguro que __vmx_handle_exit() use 'ndata' de esa manera."
    }
  ],
  "metrics": {},
  "references": [
    {
      "url": "https://git.kernel.org/stable/c/04c4f2ee3f68c9a4bf1653d15f1a9a435ae33f7a",
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    },
    {
      "url": "https://git.kernel.org/stable/c/7f64753835a78c7d2cc2932a5808ef3b7fd4c050",
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    },
    {
      "url": "https://git.kernel.org/stable/c/ce541d7b59566a0d94c7c99bfb5d34b050e6af70",
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ]
}