cve-2024-35803
Vulnerability from cvelistv5
Published
2024-05-17 13:23
Modified
2024-08-02 03:21
Severity
Summary
x86/efistub: Call mixed mode boot services on the firmware's stack
References
SourceURLTags
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/2149f8a56e2ed345c7a4d022a79f6b8fc53ae926
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/725351c036452b7db5771a7bed783564bc4b99cc
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/930775060ca348b8665f60eef14b204172d14f31
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/cefcd4fe2e3aaf792c14c9e56dab89e3d7a65d02
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/fba7ee7187581b5bc222003e73e2592b398bb06d
Impacted products
VendorProduct
LinuxLinux
LinuxLinux
Show details on NVD website

To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2024-35803",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-05-28T15:53:37.707964Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-06-04T17:33:39.635Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      },
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-02T03:21:47.550Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/2149f8a56e2ed345c7a4d022a79f6b8fc53ae926"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/930775060ca348b8665f60eef14b204172d14f31"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/fba7ee7187581b5bc222003e73e2592b398bb06d"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/725351c036452b7db5771a7bed783564bc4b99cc"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/cefcd4fe2e3aaf792c14c9e56dab89e3d7a65d02"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "arch/x86/boot/compressed/efi_mixed.S"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "2149f8a56e2e",
              "status": "affected",
              "version": "1da177e4c3f4",
              "versionType": "git"
            },
            {
              "lessThan": "930775060ca3",
              "status": "affected",
              "version": "1da177e4c3f4",
              "versionType": "git"
            },
            {
              "lessThan": "fba7ee718758",
              "status": "affected",
              "version": "1da177e4c3f4",
              "versionType": "git"
            },
            {
              "lessThan": "725351c03645",
              "status": "affected",
              "version": "1da177e4c3f4",
              "versionType": "git"
            },
            {
              "lessThan": "cefcd4fe2e3a",
              "status": "affected",
              "version": "1da177e4c3f4",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "arch/x86/boot/compressed/efi_mixed.S"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.84",
              "versionType": "custom"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.24",
              "versionType": "custom"
            },
            {
              "lessThanOrEqual": "6.7.*",
              "status": "unaffected",
              "version": "6.7.12",
              "versionType": "custom"
            },
            {
              "lessThanOrEqual": "6.8.*",
              "status": "unaffected",
              "version": "6.8.3",
              "versionType": "custom"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.9",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nx86/efistub: Call mixed mode boot services on the firmware\u0027s stack\n\nNormally, the EFI stub calls into the EFI boot services using the stack\nthat was live when the stub was entered. According to the UEFI spec,\nthis stack needs to be at least 128k in size - this might seem large but\nall asynchronous processing and event handling in EFI runs from the same\nstack and so quite a lot of space may be used in practice.\n\nIn mixed mode, the situation is a bit different: the bootloader calls\nthe 32-bit EFI stub entry point, which calls the decompressor\u0027s 32-bit\nentry point, where the boot stack is set up, using a fixed allocation\nof 16k. This stack is still in use when the EFI stub is started in\n64-bit mode, and so all calls back into the EFI firmware will be using\nthe decompressor\u0027s limited boot stack.\n\nDue to the placement of the boot stack right after the boot heap, any\nstack overruns have gone unnoticed. However, commit\n\n  5c4feadb0011983b (\"x86/decompressor: Move global symbol references to C code\")\n\nmoved the definition of the boot heap into C code, and now the boot\nstack is placed right at the base of BSS, where any overruns will\ncorrupt the end of the .data section.\n\nWhile it would be possible to work around this by increasing the size of\nthe boot stack, doing so would affect all x86 systems, and mixed mode\nsystems are a tiny (and shrinking) fraction of the x86 installed base.\n\nSo instead, record the firmware stack pointer value when entering from\nthe 32-bit firmware, and switch to this stack every time a EFI boot\nservice call is made."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2024-05-29T05:29:15.447Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/2149f8a56e2ed345c7a4d022a79f6b8fc53ae926"
        },
        {
          "url": "https://git.kernel.org/stable/c/930775060ca348b8665f60eef14b204172d14f31"
        },
        {
          "url": "https://git.kernel.org/stable/c/fba7ee7187581b5bc222003e73e2592b398bb06d"
        },
        {
          "url": "https://git.kernel.org/stable/c/725351c036452b7db5771a7bed783564bc4b99cc"
        },
        {
          "url": "https://git.kernel.org/stable/c/cefcd4fe2e3aaf792c14c9e56dab89e3d7a65d02"
        }
      ],
      "title": "x86/efistub: Call mixed mode boot services on the firmware\u0027s stack",
      "x_generator": {
        "engine": "bippy-a5840b7849dd"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-35803",
    "datePublished": "2024-05-17T13:23:12.183Z",
    "dateReserved": "2024-05-17T12:19:12.341Z",
    "dateUpdated": "2024-08-02T03:21:47.550Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-35803\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-05-17T14:15:13.337\",\"lastModified\":\"2024-05-17T18:35:35.070\",\"vulnStatus\":\"Awaiting Analysis\",\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nx86/efistub: Call mixed mode boot services on the firmware\u0027s stack\\n\\nNormally, the EFI stub calls into the EFI boot services using the stack\\nthat was live when the stub was entered. According to the UEFI spec,\\nthis stack needs to be at least 128k in size - this might seem large but\\nall asynchronous processing and event handling in EFI runs from the same\\nstack and so quite a lot of space may be used in practice.\\n\\nIn mixed mode, the situation is a bit different: the bootloader calls\\nthe 32-bit EFI stub entry point, which calls the decompressor\u0027s 32-bit\\nentry point, where the boot stack is set up, using a fixed allocation\\nof 16k. This stack is still in use when the EFI stub is started in\\n64-bit mode, and so all calls back into the EFI firmware will be using\\nthe decompressor\u0027s limited boot stack.\\n\\nDue to the placement of the boot stack right after the boot heap, any\\nstack overruns have gone unnoticed. However, commit\\n\\n  5c4feadb0011983b (\\\"x86/decompressor: Move global symbol references to C code\\\")\\n\\nmoved the definition of the boot heap into C code, and now the boot\\nstack is placed right at the base of BSS, where any overruns will\\ncorrupt the end of the .data section.\\n\\nWhile it would be possible to work around this by increasing the size of\\nthe boot stack, doing so would affect all x86 systems, and mixed mode\\nsystems are a tiny (and shrinking) fraction of the x86 installed base.\\n\\nSo instead, record the firmware stack pointer value when entering from\\nthe 32-bit firmware, and switch to this stack every time a EFI boot\\nservice call is made.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: x86/efistub: llame a los servicios de arranque en modo mixto en la pila del firmware. Normalmente, el c\u00f3digo auxiliar de EFI llama a los servicios de arranque de EFI utilizando la pila que estaba activa cuando se ingres\u00f3 el c\u00f3digo auxiliar. Seg\u00fan la especificaci\u00f3n UEFI, esta pila debe tener un tama\u00f1o m\u00ednimo de 128k; esto puede parecer grande, pero todo el procesamiento as\u00edncrono y el manejo de eventos en EFI se ejecutan desde la misma pila, por lo que en la pr\u00e1ctica se puede utilizar bastante espacio. En modo mixto, la situaci\u00f3n es un poco diferente: el gestor de arranque llama al punto de entrada del c\u00f3digo auxiliar EFI de 32 bits, que llama al punto de entrada de 32 bits del descompresor, donde se configura la pila de arranque, utilizando una asignaci\u00f3n fija de 16k. Esta pila todav\u00eda est\u00e1 en uso cuando el c\u00f3digo auxiliar EFI se inicia en modo de 64 bits, por lo que todas las llamadas al firmware EFI utilizar\u00e1n la pila de arranque limitada del descompresor. Debido a la ubicaci\u00f3n de la pila de arranque justo despu\u00e9s del mont\u00f3n de arranque, cualquier desbordamiento de la pila pasa desapercibido. Sin embargo, la confirmaci\u00f3n 5c4feadb0011983b (\\\"x86/decompressor: Mover referencias de s\u00edmbolos globales al c\u00f3digo C\\\") movi\u00f3 la definici\u00f3n del mont\u00f3n de arranque al c\u00f3digo C, y ahora la pila de arranque se coloca justo en la base de BSS, donde cualquier desbordamiento da\u00f1ar\u00e1 el final de la secci\u00f3n .data. Si bien ser\u00eda posible solucionar este problema aumentando el tama\u00f1o de la pila de arranque, hacerlo afectar\u00eda a todos los sistemas x86, y los sistemas de modo mixto son una fracci\u00f3n peque\u00f1a (y cada vez menor) de la base instalada x86. En su lugar, registre el valor del puntero de la pila de firmware al ingresar desde el firmware de 32 bits y cambie a esta pila cada vez que se realice una llamada al servicio de arranque EFI.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/2149f8a56e2ed345c7a4d022a79f6b8fc53ae926\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/725351c036452b7db5771a7bed783564bc4b99cc\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/930775060ca348b8665f60eef14b204172d14f31\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/cefcd4fe2e3aaf792c14c9e56dab89e3d7a65d02\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/fba7ee7187581b5bc222003e73e2592b398bb06d\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.