Vulnerability-Lookup

OESA-2023-1146 (CVE-2023-0045)

Vulnerability from osv_openeuler – Published: 2023-03-04 11:05 – Updated: 2026-08-06 11:05 – Source website

Summary

kernel security update

Details

The Linux Kernel, the operating system core itself.

Security Fix(es):

The Linux kernel does not correctly mitigate SMT attacks, as discovered through a strange pattern in the kernel API using STIBP as a mitigation[1 <https://docs.kernel.org/userspace-api/spec_ctrl.html>], leaving the process exposed for a short period of time after a syscall. The kernel also does not issue an IBPB immediately during the syscall. The ib_prctl_set [2 <https://elixir.bootlin.com/linux/v5.15.56/source/arch/x86/kernel/cpu/bugs.c#L1467>]function updates the Thread Information Flags (TIFs) for the task and updates the SPEC_CTRL MSR on the function __speculation_ctrl_update [3 <https://elixir.bootlin.com/linux/v5.15.56/source/arch/x86/kernel/process.c#L557>], but the IBPB is only issued on the next schedule, when the TIF bits are checked. This leaves the victim vulnerable to values already injected on the BTB, prior to the prctl syscall. The behavior is only corrected after a reschedule of the task happens. Furthermore, the kernel entrance (due to the syscall itself), does not issue an IBPB in the default scenarios (i.e., when the kernel protects itself via retpoline or eIBRS).(CVE-2023-0045)

REMAP cmd of SVM driver can be used to remap read only memory as read-write, then cause read only memory/file modified..(CVE-2021-33639)

Severity

6.7 (Medium)


                    
                      CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

References

URL

Type

	https://www.openeuler.org/en/security/safety-bull…	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2023-0045	ADVISORY
	https://nvd.nist.gov/vuln/detail/CVE-2021-33639	ADVISORY

JSON

To clipboard

{
  "affected": [
    {
      "ecosystem_specific": {
        "aarch64": [
          "perf-debuginfo-4.19.90-2302.5.0.0190.oe1.aarch64.rpm",
          "kernel-debugsource-4.19.90-2302.5.0.0190.oe1.aarch64.rpm",
          "kernel-devel-4.19.90-2302.5.0.0190.oe1.aarch64.rpm",
          "bpftool-4.19.90-2302.5.0.0190.oe1.aarch64.rpm",
          "python2-perf-debuginfo-4.19.90-2302.5.0.0190.oe1.aarch64.rpm",
          "kernel-tools-debuginfo-4.19.90-2302.5.0.0190.oe1.aarch64.rpm",
          "kernel-tools-devel-4.19.90-2302.5.0.0190.oe1.aarch64.rpm",
          "python3-perf-4.19.90-2302.5.0.0190.oe1.aarch64.rpm",
          "bpftool-debuginfo-4.19.90-2302.5.0.0190.oe1.aarch64.rpm",
          "kernel-4.19.90-2302.5.0.0190.oe1.aarch64.rpm",
          "kernel-debuginfo-4.19.90-2302.5.0.0190.oe1.aarch64.rpm",
          "python3-perf-debuginfo-4.19.90-2302.5.0.0190.oe1.aarch64.rpm",
          "kernel-tools-4.19.90-2302.5.0.0190.oe1.aarch64.rpm",
          "kernel-source-4.19.90-2302.5.0.0190.oe1.aarch64.rpm",
          "python2-perf-4.19.90-2302.5.0.0190.oe1.aarch64.rpm",
          "perf-4.19.90-2302.5.0.0190.oe1.aarch64.rpm"
        ],
        "src": [
          "kernel-4.19.90-2302.5.0.0190.oe1.src.rpm"
        ],
        "x86_64": [
          "perf-debuginfo-4.19.90-2302.5.0.0190.oe1.x86_64.rpm",
          "perf-4.19.90-2302.5.0.0190.oe1.x86_64.rpm",
          "kernel-devel-4.19.90-2302.5.0.0190.oe1.x86_64.rpm",
          "kernel-tools-4.19.90-2302.5.0.0190.oe1.x86_64.rpm",
          "kernel-source-4.19.90-2302.5.0.0190.oe1.x86_64.rpm",
          "kernel-4.19.90-2302.5.0.0190.oe1.x86_64.rpm",
          "kernel-tools-devel-4.19.90-2302.5.0.0190.oe1.x86_64.rpm",
          "python2-perf-4.19.90-2302.5.0.0190.oe1.x86_64.rpm",
          "python2-perf-debuginfo-4.19.90-2302.5.0.0190.oe1.x86_64.rpm",
          "python3-perf-4.19.90-2302.5.0.0190.oe1.x86_64.rpm",
          "bpftool-debuginfo-4.19.90-2302.5.0.0190.oe1.x86_64.rpm",
          "kernel-tools-debuginfo-4.19.90-2302.5.0.0190.oe1.x86_64.rpm",
          "bpftool-4.19.90-2302.5.0.0190.oe1.x86_64.rpm",
          "python3-perf-debuginfo-4.19.90-2302.5.0.0190.oe1.x86_64.rpm",
          "kernel-debuginfo-4.19.90-2302.5.0.0190.oe1.x86_64.rpm",
          "kernel-debugsource-4.19.90-2302.5.0.0190.oe1.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:20.03-LTS-SP1",
        "name": "kernel",
        "purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-20.03-LTS-SP1"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "4.19.90-2302.5.0.0190.oe1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "severity": "Medium"
  },
  "details": "The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nThe Linux kernel does not correctly mitigate SMT attacks, as discovered\nthrough a strange pattern in the kernel API using STIBP as a mitigation[1\n\u0026lt;https://docs.kernel.org/userspace-api/spec_ctrl.html\u0026gt;], leaving the\nprocess exposed for a short period of time after a syscall. The kernel also\ndoes not issue an IBPB immediately during the syscall.\nThe ib_prctl_set [2\n\u0026lt;https://elixir.bootlin.com/linux/v5.15.56/source/arch/x86/kernel/cpu/bugs.c#L1467\u0026gt;]function\nupdates the Thread Information Flags (TIFs) for the task and updates the\nSPEC_CTRL MSR on the function __speculation_ctrl_update [3\n\u0026lt;https://elixir.bootlin.com/linux/v5.15.56/source/arch/x86/kernel/process.c#L557\u0026gt;],\nbut the IBPB is only issued on the next schedule, when the TIF bits are\nchecked. This leaves the victim vulnerable to values already injected on\nthe BTB, prior to the prctl syscall.\nThe behavior is only corrected after a reschedule of the task happens.\nFurthermore, the kernel entrance (due to the syscall itself), does not\nissue an IBPB in the default scenarios (i.e., when the kernel protects\nitself via retpoline or eIBRS).(CVE-2023-0045)\r\n\r\nREMAP cmd of SVM driver can be used to remap read only memory as read-write, then cause read only memory/file modified..(CVE-2021-33639)",
  "id": "OESA-2023-1146",
  "modified": "2026-08-06T11:05:37Z",
  "published": "2023-03-04T11:05:37Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2023-1146"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-0045"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-33639"
    }
  ],
  "schema_version": "1.7.2",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "kernel security update",
  "upstream": [
    "CVE-2023-0045",
    "CVE-2021-33639"
  ]
}

CVE-2021-33639 (GCVE-0-2021-33639)

Vulnerability from cvelistv5 – Published: 2023-03-08 00:00 – Updated: 2025-03-04 20:24

Summary

REMAP cmd of SVM driver can be used to remap read only memory as read-write, then cause read only memory/file modified.

Severity

7.5 (High)


                        
                          CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

SSVC

Exploitation: none Automatable: yes Technical Impact: partial

CISA Coordinator · CISA-ADP (v2.0.3)

Decision recorded 2025-03-04 20:23 UTC

CWE

CWE-749 - Exposed Dangerous Method or Function

Assigner

openEuler mitre root

References

1 reference

URL	Tags
https://gitee.com/openeuler/kernel/commit/e4d0684…

Impacted products

1 product

Vendor	Product	Version
n/a	kernel	Affected: <=4.19.90-2211.4.0.0177, <=5.10.0-60.67.0.92

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-03T23:58:21.572Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://gitee.com/openeuler/kernel/commit/e4d0684a3ce68e7f8e11408121e791cd80312b27"
          }
        ],
        "title": "CVE Program Container"
      },
      {
        "metrics": [
          {
            "cvssV3_1": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "NONE",
              "baseScore": 7.5,
              "baseSeverity": "HIGH",
              "confidentialityImpact": "NONE",
              "integrityImpact": "HIGH",
              "privilegesRequired": "NONE",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
              "version": "3.1"
            }
          },
          {
            "other": {
              "content": {
                "id": "CVE-2021-33639",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "yes"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2025-03-04T20:23:06.370820Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2025-03-04T20:24:10.590Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "kernel",
          "vendor": "n/a",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c=4.19.90-2211.4.0.0177, \u003c=5.10.0-60.67.0.92"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "REMAP cmd of SVM driver can be used to remap read only memory as read-write, then cause read only memory/file modified."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-749",
              "description": "CWE-749: Exposed Dangerous Method or Function",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2023-03-08T00:00:00.000Z",
        "orgId": "7e1ac599-2767-43fa-b3ea-f10178cc98f2",
        "shortName": "openEuler"
      },
      "references": [
        {
          "url": "https://gitee.com/openeuler/kernel/commit/e4d0684a3ce68e7f8e11408121e791cd80312b27"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "7e1ac599-2767-43fa-b3ea-f10178cc98f2",
    "assignerShortName": "openEuler",
    "cveId": "CVE-2021-33639",
    "datePublished": "2023-03-08T00:00:00.000Z",
    "dateReserved": "2021-05-28T00:00:00.000Z",
    "dateUpdated": "2025-03-04T20:24:10.590Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1"
}

CVE-2023-0045 (GCVE-0-2023-0045)

Vulnerability from cvelistv5 – Published: 2023-04-25 22:44 – Updated: 2025-02-13 16:38

Title

Incorrect indirect branch prediction barrier in the Linux Kernel

Summary

The current implementation of the prctl syscall does not issue an IBPB immediately during the syscall. The ib_prctl_set function updates the Thread Information Flags (TIFs) for the task and updates the SPEC_CTRL MSR on the function __speculation_ctrl_update, but the IBPB is only issued on the next schedule, when the TIF bits are checked. This leaves the victim vulnerable to values already injected on the BTB, prior to the prctl syscall. The patch that added the support for the conditional mitigation via prctl (ib_prctl_set) dates back to the kernel 4.9.176. We recommend upgrading past commit a664ec9158eeddd75121d39c9a0758016097fa96

Severity

4.7 (Medium)


                        
                          CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

SSVC

Exploitation: poc Automatable: no Technical Impact: partial

CISA Coordinator · CISA-ADP (v2.0.3)

Decision recorded 2025-02-03 17:52 UTC

CWE

CWE-610 - Externally Controlled Reference to a Resource in Another Sphere

Assigner

Google Google root

References

5 references

URL	Tags
https://git.kernel.org/tip/a664ec9158eeddd75121d3…
https://lists.debian.org/debian-lts-announce/2023…
https://lists.debian.org/debian-lts-announce/2023…
https://security.netapp.com/advisory/ntap-2023071…
https://github.com/google/security-research/secur…

Impacted products

1 product

Vendor	Product	Version
Linux	Linux Kernel	Affected: 9137bb27e60e , < a664ec9158eeddd75121d39c9a0758016097fa96 (git)

Date Public

2023-01-02 23:00

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-02T04:54:32.575Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/tip/a664ec9158eeddd75121d39c9a0758016097fa96"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://lists.debian.org/debian-lts-announce/2023/05/msg00005.html"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://lists.debian.org/debian-lts-announce/2023/05/msg00006.html"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://security.netapp.com/advisory/ntap-20230714-0001/"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://github.com/google/security-research/security/advisories/GHSA-9x5g-vmxf-4qj8"
          }
        ],
        "title": "CVE Program Container"
      },
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2023-0045",
                "options": [
                  {
                    "Exploitation": "poc"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2025-02-03T17:52:12.098510Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2025-02-03T17:52:16.463Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "packageName": "kernel",
          "product": "Linux Kernel",
          "repo": "https://git.kernel.org",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "a664ec9158eeddd75121d39c9a0758016097fa96",
              "status": "affected",
              "version": "9137bb27e60e",
              "versionType": "git"
            }
          ]
        }
      ],
      "datePublic": "2023-01-02T23:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cspan style=\"background-color: rgb(255, 255, 255);\"\u003eThe current implementation of the prctl syscall does not issue an IBPB immediately during the syscall. The ib_prctl_set \u0026nbsp;function updates the Thread Information Flags (TIFs) for the task and updates the SPEC_CTRL MSR on the function __speculation_ctrl_update, but the IBPB is only issued on the next schedule, when the TIF bits are checked. This leaves the victim vulnerable to values already injected on the BTB, prior to the prctl syscall. \u0026nbsp;The patch that added the support for the conditional mitigation via prctl (ib_prctl_set) dates back to the kernel 4.9.176.\u003cbr\u003e\u003cbr\u003e\u003c/span\u003eWe recommend upgrading past commit\u0026nbsp;a664ec9158eeddd75121d39c9a0758016097fa96\u003cbr\u003e\u003cbr\u003e"
            }
          ],
          "value": "The current implementation of the prctl syscall does not issue an IBPB immediately during the syscall. The ib_prctl_set \u00a0function updates the Thread Information Flags (TIFs) for the task and updates the SPEC_CTRL MSR on the function __speculation_ctrl_update, but the IBPB is only issued on the next schedule, when the TIF bits are checked. This leaves the victim vulnerable to values already injected on the BTB, prior to the prctl syscall. \u00a0The patch that added the support for the conditional mitigation via prctl (ib_prctl_set) dates back to the kernel 4.9.176.\n\nWe recommend upgrading past commit\u00a0a664ec9158eeddd75121d39c9a0758016097fa96"
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-131",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-131 Resource Leak Exposure"
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "LOCAL",
            "availabilityImpact": "NONE",
            "baseScore": 4.7,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "NONE",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N",
            "version": "3.1"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-610",
              "description": "CWE-610 Externally Controlled Reference to a Resource in Another Sphere",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2023-07-23T01:41:15.247Z",
        "orgId": "14ed7db2-1595-443d-9d34-6215bf890778",
        "shortName": "Google"
      },
      "references": [
        {
          "url": "https://git.kernel.org/tip/a664ec9158eeddd75121d39c9a0758016097fa96"
        },
        {
          "url": "https://lists.debian.org/debian-lts-announce/2023/05/msg00005.html"
        },
        {
          "url": "https://lists.debian.org/debian-lts-announce/2023/05/msg00006.html"
        },
        {
          "url": "https://security.netapp.com/advisory/ntap-20230714-0001/"
        },
        {
          "url": "https://github.com/google/security-research/security/advisories/GHSA-9x5g-vmxf-4qj8"
        }
      ],
      "source": {
        "discovery": "EXTERNAL"
      },
      "title": "Incorrect indirect branch prediction barrier in the Linux Kernel",
      "x_generator": {
        "engine": "Vulnogram 0.1.0-dev"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "14ed7db2-1595-443d-9d34-6215bf890778",
    "assignerShortName": "Google",
    "cveId": "CVE-2023-0045",
    "datePublished": "2023-04-25T22:44:57.262Z",
    "dateReserved": "2023-01-04T10:07:20.469Z",
    "dateUpdated": "2025-02-13T16:38:41.984Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1"
}

Sightings

Author	Source	Type	Date	Other

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.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted

OESA-2023-1146 (CVE-2023-0045)

CVE-2021-33639 (GCVE-0-2021-33639)

CVE-2023-0045 (GCVE-0-2023-0045)

Tags

Sightings

Nomenclature

Related by attack behaviour