CVE-2021-47226 (GCVE-0-2021-47226)

Vulnerability from cvelistv5 – Published: 2024-05-21 14:19 – Updated: 2025-05-04 07:06
VLAI?
Summary
In the Linux kernel, the following vulnerability has been resolved: x86/fpu: Invalidate FPU state after a failed XRSTOR from a user buffer Both Intel and AMD consider it to be architecturally valid for XRSTOR to fail with #PF but nonetheless change the register state. The actual conditions under which this might occur are unclear [1], but it seems plausible that this might be triggered if one sibling thread unmaps a page and invalidates the shared TLB while another sibling thread is executing XRSTOR on the page in question. __fpu__restore_sig() can execute XRSTOR while the hardware registers are preserved on behalf of a different victim task (using the fpu_fpregs_owner_ctx mechanism), and, in theory, XRSTOR could fail but modify the registers. If this happens, then there is a window in which __fpu__restore_sig() could schedule out and the victim task could schedule back in without reloading its own FPU registers. This would result in part of the FPU state that __fpu__restore_sig() was attempting to load leaking into the victim task's user-visible state. Invalidate preserved FPU registers on XRSTOR failure to prevent this situation from corrupting any state. [1] Frequent readers of the errata lists might imagine "complex microarchitectural conditions".
Severity ?
No CVSS data available.
Assigner
References
Impacted products
Vendor Product Version
Linux Linux Affected: 1d731e731c4cd7cbd3b1aa295f0932e7610da82f , < a7748e021b9fb7739e3cb88449296539de0b6817 (git)
Affected: 1d731e731c4cd7cbd3b1aa295f0932e7610da82f , < 002665dcba4bbec8c82f0aeb4bd3f44334ed2c14 (git)
Affected: 1d731e731c4cd7cbd3b1aa295f0932e7610da82f , < d8778e393afa421f1f117471144f8ce6deb6953a (git)
Create a notification for this product.
    Linux Linux Affected: 5.2
Unaffected: 0 , < 5.2 (semver)
Unaffected: 5.10.46 , ≤ 5.10.* (semver)
Unaffected: 5.12.13 , ≤ 5.12.* (semver)
Unaffected: 5.13 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2021-47226",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-05-21T15:36:03.024870Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-06-04T17:15:21.177Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      },
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-04T05:32:07.454Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/a7748e021b9fb7739e3cb88449296539de0b6817"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/002665dcba4bbec8c82f0aeb4bd3f44334ed2c14"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/d8778e393afa421f1f117471144f8ce6deb6953a"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "arch/x86/kernel/fpu/signal.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "a7748e021b9fb7739e3cb88449296539de0b6817",
              "status": "affected",
              "version": "1d731e731c4cd7cbd3b1aa295f0932e7610da82f",
              "versionType": "git"
            },
            {
              "lessThan": "002665dcba4bbec8c82f0aeb4bd3f44334ed2c14",
              "status": "affected",
              "version": "1d731e731c4cd7cbd3b1aa295f0932e7610da82f",
              "versionType": "git"
            },
            {
              "lessThan": "d8778e393afa421f1f117471144f8ce6deb6953a",
              "status": "affected",
              "version": "1d731e731c4cd7cbd3b1aa295f0932e7610da82f",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "arch/x86/kernel/fpu/signal.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.2"
            },
            {
              "lessThan": "5.2",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.10.*",
              "status": "unaffected",
              "version": "5.10.46",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.12.*",
              "status": "unaffected",
              "version": "5.12.13",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "5.13",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.10.46",
                  "versionStartIncluding": "5.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.12.13",
                  "versionStartIncluding": "5.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.13",
                  "versionStartIncluding": "5.2",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Invalidate FPU state after a failed XRSTOR from a user buffer\n\nBoth Intel and AMD consider it to be architecturally valid for XRSTOR to\nfail with #PF but nonetheless change the register state.  The actual\nconditions under which this might occur are unclear [1], but it seems\nplausible that this might be triggered if one sibling thread unmaps a page\nand invalidates the shared TLB while another sibling thread is executing\nXRSTOR on the page in question.\n\n__fpu__restore_sig() can execute XRSTOR while the hardware registers\nare preserved on behalf of a different victim task (using the\nfpu_fpregs_owner_ctx mechanism), and, in theory, XRSTOR could fail but\nmodify the registers.\n\nIf this happens, then there is a window in which __fpu__restore_sig()\ncould schedule out and the victim task could schedule back in without\nreloading its own FPU registers. This would result in part of the FPU\nstate that __fpu__restore_sig() was attempting to load leaking into the\nvictim task\u0027s user-visible state.\n\nInvalidate preserved FPU registers on XRSTOR failure to prevent this\nsituation from corrupting any state.\n\n[1] Frequent readers of the errata lists might imagine \"complex\n    microarchitectural conditions\"."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-05-04T07:06:41.696Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/a7748e021b9fb7739e3cb88449296539de0b6817"
        },
        {
          "url": "https://git.kernel.org/stable/c/002665dcba4bbec8c82f0aeb4bd3f44334ed2c14"
        },
        {
          "url": "https://git.kernel.org/stable/c/d8778e393afa421f1f117471144f8ce6deb6953a"
        }
      ],
      "title": "x86/fpu: Invalidate FPU state after a failed XRSTOR from a user buffer",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2021-47226",
    "datePublished": "2024-05-21T14:19:30.864Z",
    "dateReserved": "2024-04-10T18:59:19.529Z",
    "dateUpdated": "2025-05-04T07:06:41.696Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "fkie_nvd": {
      "descriptions": "[{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nx86/fpu: Invalidate FPU state after a failed XRSTOR from a user buffer\\n\\nBoth Intel and AMD consider it to be architecturally valid for XRSTOR to\\nfail with #PF but nonetheless change the register state.  The actual\\nconditions under which this might occur are unclear [1], but it seems\\nplausible that this might be triggered if one sibling thread unmaps a page\\nand invalidates the shared TLB while another sibling thread is executing\\nXRSTOR on the page in question.\\n\\n__fpu__restore_sig() can execute XRSTOR while the hardware registers\\nare preserved on behalf of a different victim task (using the\\nfpu_fpregs_owner_ctx mechanism), and, in theory, XRSTOR could fail but\\nmodify the registers.\\n\\nIf this happens, then there is a window in which __fpu__restore_sig()\\ncould schedule out and the victim task could schedule back in without\\nreloading its own FPU registers. This would result in part of the FPU\\nstate that __fpu__restore_sig() was attempting to load leaking into the\\nvictim task\u0027s user-visible state.\\n\\nInvalidate preserved FPU registers on XRSTOR failure to prevent this\\nsituation from corrupting any state.\\n\\n[1] Frequent readers of the errata lists might imagine \\\"complex\\n    microarchitectural conditions\\\".\"}, {\"lang\": \"es\", \"value\": \"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: x86/fpu: Invalida el estado de la FPU despu\\u00e9s de un XRSTOR fallido desde un b\\u00fafer de usuario. Tanto Intel como AMD consideran que es arquitect\\u00f3nicamente v\\u00e1lido que XRSTOR falle con #PF pero aun as\\u00ed cambie el estado del registro. . Las condiciones reales bajo las cuales esto podr\\u00eda ocurrir no est\\u00e1n claras [1], pero parece plausible que esto pueda desencadenarse si un hilo hermano desasigna una p\\u00e1gina e invalida el TLB compartido mientras otro hilo hermano est\\u00e1 ejecutando XRSTOR en la p\\u00e1gina en cuesti\\u00f3n. __fpu__restore_sig() puede ejecutar XRSTOR mientras los registros de hardware se conservan en nombre de una tarea de v\\u00edctima diferente (usando el mecanismo fpu_fpregs_owner_ctx) y, en teor\\u00eda, XRSTOR podr\\u00eda fallar pero modificar los registros. Si esto sucede, entonces hay una ventana en la que __fpu__restore_sig() podr\\u00eda programar la salida y la tarea de la v\\u00edctima podr\\u00eda volver a programarse sin recargar sus propios registros FPU. Esto resultar\\u00eda en parte del estado de la FPU en el que __fpu__restore_sig() intentaba cargar una filtraci\\u00f3n en el estado visible para el usuario de la tarea de la v\\u00edctima. Invalide los registros FPU preservados en caso de falla de XRSTOR para evitar que esta situaci\\u00f3n corrompa cualquier estado. [1] Los lectores frecuentes de las listas de erratas podr\\u00edan imaginar \\\"condiciones microarquitect\\u00f3nicas complejas\\\".\"}]",
      "id": "CVE-2021-47226",
      "lastModified": "2024-11-21T06:35:39.977",
      "published": "2024-05-21T15:15:11.823",
      "references": "[{\"url\": \"https://git.kernel.org/stable/c/002665dcba4bbec8c82f0aeb4bd3f44334ed2c14\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/a7748e021b9fb7739e3cb88449296539de0b6817\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/d8778e393afa421f1f117471144f8ce6deb6953a\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/002665dcba4bbec8c82f0aeb4bd3f44334ed2c14\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}, {\"url\": \"https://git.kernel.org/stable/c/a7748e021b9fb7739e3cb88449296539de0b6817\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}, {\"url\": \"https://git.kernel.org/stable/c/d8778e393afa421f1f117471144f8ce6deb6953a\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}]",
      "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "vulnStatus": "Awaiting Analysis"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2021-47226\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-05-21T15:15:11.823\",\"lastModified\":\"2025-04-29T19:26:36.690\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nx86/fpu: Invalidate FPU state after a failed XRSTOR from a user buffer\\n\\nBoth Intel and AMD consider it to be architecturally valid for XRSTOR to\\nfail with #PF but nonetheless change the register state.  The actual\\nconditions under which this might occur are unclear [1], but it seems\\nplausible that this might be triggered if one sibling thread unmaps a page\\nand invalidates the shared TLB while another sibling thread is executing\\nXRSTOR on the page in question.\\n\\n__fpu__restore_sig() can execute XRSTOR while the hardware registers\\nare preserved on behalf of a different victim task (using the\\nfpu_fpregs_owner_ctx mechanism), and, in theory, XRSTOR could fail but\\nmodify the registers.\\n\\nIf this happens, then there is a window in which __fpu__restore_sig()\\ncould schedule out and the victim task could schedule back in without\\nreloading its own FPU registers. This would result in part of the FPU\\nstate that __fpu__restore_sig() was attempting to load leaking into the\\nvictim task\u0027s user-visible state.\\n\\nInvalidate preserved FPU registers on XRSTOR failure to prevent this\\nsituation from corrupting any state.\\n\\n[1] Frequent readers of the errata lists might imagine \\\"complex\\n    microarchitectural conditions\\\".\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: x86/fpu: Invalida el estado de la FPU despu\u00e9s de un XRSTOR fallido desde un b\u00fafer de usuario. Tanto Intel como AMD consideran que es arquitect\u00f3nicamente v\u00e1lido que XRSTOR falle con #PF pero aun as\u00ed cambie el estado del registro. . Las condiciones reales bajo las cuales esto podr\u00eda ocurrir no est\u00e1n claras [1], pero parece plausible que esto pueda desencadenarse si un hilo hermano desasigna una p\u00e1gina e invalida el TLB compartido mientras otro hilo hermano est\u00e1 ejecutando XRSTOR en la p\u00e1gina en cuesti\u00f3n. __fpu__restore_sig() puede ejecutar XRSTOR mientras los registros de hardware se conservan en nombre de una tarea de v\u00edctima diferente (usando el mecanismo fpu_fpregs_owner_ctx) y, en teor\u00eda, XRSTOR podr\u00eda fallar pero modificar los registros. Si esto sucede, entonces hay una ventana en la que __fpu__restore_sig() podr\u00eda programar la salida y la tarea de la v\u00edctima podr\u00eda volver a programarse sin recargar sus propios registros FPU. Esto resultar\u00eda en parte del estado de la FPU en el que __fpu__restore_sig() intentaba cargar una filtraci\u00f3n en el estado visible para el usuario de la tarea de la v\u00edctima. Invalide los registros FPU preservados en caso de falla de XRSTOR para evitar que esta situaci\u00f3n corrompa cualquier estado. [1] Los lectores frecuentes de las listas de erratas podr\u00edan imaginar \\\"condiciones microarquitect\u00f3nicas complejas\\\".\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H\",\"baseScore\":7.1,\"baseSeverity\":\"HIGH\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":5.2}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-203\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.2\",\"versionEndExcluding\":\"5.10.46\",\"matchCriteriaId\":\"71A9FF74-A7CD-4A97-B822-6302C3124C48\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.11\",\"versionEndExcluding\":\"5.12.13\",\"matchCriteriaId\":\"7806E7E5-6D4F-4E18-81C1-79B3C60EE855\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:5.13:rc1:*:*:*:*:*:*\",\"matchCriteriaId\":\"0CBAD0FC-C281-4666-AB2F-F8E6E1165DF7\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:5.13:rc2:*:*:*:*:*:*\",\"matchCriteriaId\":\"96AC23B2-D46A-49D9-8203-8E1BEDCA8532\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:5.13:rc3:*:*:*:*:*:*\",\"matchCriteriaId\":\"DA610E30-717C-4700-9F77-A3C9244F3BFD\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:5.13:rc4:*:*:*:*:*:*\",\"matchCriteriaId\":\"1ECD33F5-85BE-430B-8F86-8D7BD560311D\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:5.13:rc5:*:*:*:*:*:*\",\"matchCriteriaId\":\"CF351855-2437-4CF5-AD7C-BDFA51F27683\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:5.13:rc6:*:*:*:*:*:*\",\"matchCriteriaId\":\"25A855BA-2118-44F2-90EF-EBBB12AF51EF\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/002665dcba4bbec8c82f0aeb4bd3f44334ed2c14\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/a7748e021b9fb7739e3cb88449296539de0b6817\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/d8778e393afa421f1f117471144f8ce6deb6953a\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/002665dcba4bbec8c82f0aeb4bd3f44334ed2c14\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/a7748e021b9fb7739e3cb88449296539de0b6817\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/d8778e393afa421f1f117471144f8ce6deb6953a\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Patch\"]}]}}",
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://git.kernel.org/stable/c/a7748e021b9fb7739e3cb88449296539de0b6817\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/002665dcba4bbec8c82f0aeb4bd3f44334ed2c14\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/d8778e393afa421f1f117471144f8ce6deb6953a\", \"tags\": [\"x_transferred\"]}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2024-08-04T05:32:07.454Z\"}}, {\"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2021-47226\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-05-21T15:36:03.024870Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-05-23T19:01:25.194Z\"}, \"title\": \"CISA ADP Vulnrichment\"}], \"cna\": {\"title\": \"x86/fpu: Invalidate FPU state after a failed XRSTOR from a user buffer\", \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"1d731e731c4c\", \"lessThan\": \"a7748e021b9f\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"1d731e731c4c\", \"lessThan\": \"002665dcba4b\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"1d731e731c4c\", \"lessThan\": \"d8778e393afa\", \"versionType\": \"git\"}], \"programFiles\": [\"arch/x86/kernel/fpu/signal.c\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"5.2\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"5.2\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"5.10.46\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.10.*\"}, {\"status\": \"unaffected\", \"version\": \"5.12.13\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.12.*\"}, {\"status\": \"unaffected\", \"version\": \"5.13\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"arch/x86/kernel/fpu/signal.c\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/a7748e021b9fb7739e3cb88449296539de0b6817\"}, {\"url\": \"https://git.kernel.org/stable/c/002665dcba4bbec8c82f0aeb4bd3f44334ed2c14\"}, {\"url\": \"https://git.kernel.org/stable/c/d8778e393afa421f1f117471144f8ce6deb6953a\"}], \"x_generator\": {\"engine\": \"bippy-c8e10e5f6187\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nx86/fpu: Invalidate FPU state after a failed XRSTOR from a user buffer\\n\\nBoth Intel and AMD consider it to be architecturally valid for XRSTOR to\\nfail with #PF but nonetheless change the register state.  The actual\\nconditions under which this might occur are unclear [1], but it seems\\nplausible that this might be triggered if one sibling thread unmaps a page\\nand invalidates the shared TLB while another sibling thread is executing\\nXRSTOR on the page in question.\\n\\n__fpu__restore_sig() can execute XRSTOR while the hardware registers\\nare preserved on behalf of a different victim task (using the\\nfpu_fpregs_owner_ctx mechanism), and, in theory, XRSTOR could fail but\\nmodify the registers.\\n\\nIf this happens, then there is a window in which __fpu__restore_sig()\\ncould schedule out and the victim task could schedule back in without\\nreloading its own FPU registers. This would result in part of the FPU\\nstate that __fpu__restore_sig() was attempting to load leaking into the\\nvictim task\u0027s user-visible state.\\n\\nInvalidate preserved FPU registers on XRSTOR failure to prevent this\\nsituation from corrupting any state.\\n\\n[1] Frequent readers of the errata lists might imagine \\\"complex\\n    microarchitectural conditions\\\".\"}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2024-11-04T11:37:08.579Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2021-47226\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2024-11-04T11:37:08.579Z\", \"dateReserved\": \"2024-04-10T18:59:19.529Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-05-21T14:19:30.864Z\", \"assignerShortName\": \"Linux\"}",
      "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 observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.