Vulnerability-Lookup

CVE-2023-52514 (GCVE-0-2023-52514)

Vulnerability from cvelistv5 – Published: 2024-03-02 21:52 – Updated: 2024-03-11 16:11

This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

Show details on NVD website

{
  "containers": {
    "cna": {
      "providerMetadata": {
        "dateUpdated": "2024-03-11T16:11:44.266Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "rejectedReasons": [
        {
          "lang": "en",
          "value": "This CVE ID has been rejected or withdrawn by its CVE Numbering Authority."
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2023-52514",
    "datePublished": "2024-03-02T21:52:25.221Z",
    "dateRejected": "2024-03-11T16:11:44.266Z",
    "dateReserved": "2024-02-20T12:30:33.316Z",
    "dateUpdated": "2024-03-11T16:11:44.266Z",
    "state": "REJECTED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.0",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2023-52514\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-03-02T22:15:47.777\",\"lastModified\":\"2024-03-11T16:15:07.720\",\"vulnStatus\":\"Rejected\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.\"}],\"metrics\":{},\"references\":[]}}",
    "vulnrichment": {
      "containers": "{\"cna\": {\"rejectedReasons\": [{\"lang\": \"en\", \"value\": \"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.\"}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2024-03-11T16:11:44.266Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2023-52514\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"state\": \"REJECTED\", \"assignerShortName\": \"Linux\", \"dateReserved\": \"2024-02-20T12:30:33.316Z\", \"datePublished\": \"2024-03-02T21:52:25.221Z\", \"dateUpdated\": \"2024-03-11T16:11:44.266Z\", \"dateRejected\": \"2024-03-11T16:11:44.266Z\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.0"
    }
  }
}

FKIE_CVE-2023-52514

Vulnerability from fkie_nvd - Published: 2024-03-02 22:15 - Updated: 2024-03-11 16:15

Severity ?

Summary

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

References

	URL	Tags

Impacted products

	Vendor	Product	Version

JSON

To clipboard

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority."
    }
  ],
  "id": "CVE-2023-52514",
  "lastModified": "2024-03-11T16:15:07.720",
  "metrics": {},
  "published": "2024-03-02T22:15:47.777",
  "references": [],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Rejected"
}

GHSA-766R-W9PC-FW69

Vulnerability from github – Published: 2024-03-03 00:30 – Updated: 2024-03-03 00:30

Details

In the Linux kernel, the following vulnerability has been resolved:

x86/reboot: VMCLEAR active VMCSes before emergency reboot

VMCLEAR active VMCSes before any emergency reboot, not just if the kernel may kexec into a new kernel after a crash. Per Intel's SDM, the VMX architecture doesn't require the CPU to flush the VMCS cache on INIT. If an emergency reboot doesn't RESET CPUs, cached VMCSes could theoretically be kept and only be written back to memory after the new kernel is booted, i.e. could effectively corrupt memory after reboot.

Opportunistically remove the setting of the global pointer to NULL to make checkpatch happy.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2023-52514"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-03-02T22:15:47Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nx86/reboot: VMCLEAR active VMCSes before emergency reboot\n\nVMCLEAR active VMCSes before any emergency reboot, not just if the kernel\nmay kexec into a new kernel after a crash.  Per Intel\u0027s SDM, the VMX\narchitecture doesn\u0027t require the CPU to flush the VMCS cache on INIT.  If\nan emergency reboot doesn\u0027t RESET CPUs, cached VMCSes could theoretically\nbe kept and only be written back to memory after the new kernel is booted,\ni.e. could effectively corrupt memory after reboot.\n\nOpportunistically remove the setting of the global pointer to NULL to make\ncheckpatch happy.",
  "id": "GHSA-766r-w9pc-fw69",
  "modified": "2024-03-03T00:30:31Z",
  "published": "2024-03-03T00:30:31Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52514"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/1375d9600c38c231163de584656b07aef9a27b0d"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/65edea77d7006140c6290e7f46009d75e02d3273"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b23c83ad2c638420ec0608a9de354507c41bec29"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

GSD-2023-52514

Vulnerability from gsd - Updated: 2024-02-21 06:01

Details

In the Linux kernel, the following vulnerability has been resolved: x86/reboot: VMCLEAR active VMCSes before emergency reboot VMCLEAR active VMCSes before any emergency reboot, not just if the kernel may kexec into a new kernel after a crash. Per Intel's SDM, the VMX architecture doesn't require the CPU to flush the VMCS cache on INIT. If an emergency reboot doesn't RESET CPUs, cached VMCSes could theoretically be kept and only be written back to memory after the new kernel is booted, i.e. could effectively corrupt memory after reboot. Opportunistically remove the setting of the global pointer to NULL to make checkpatch happy.

Aliases

CVE-2023-52514

JSON

To clipboard

{
  "gsd": {
    "metadata": {
      "exploitCode": "unknown",
      "remediation": "unknown",
      "reportConfidence": "confirmed",
      "type": "vulnerability"
    },
    "osvSchema": {
      "aliases": [
        "CVE-2023-52514"
      ],
      "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nx86/reboot: VMCLEAR active VMCSes before emergency reboot\n\nVMCLEAR active VMCSes before any emergency reboot, not just if the kernel\nmay kexec into a new kernel after a crash.  Per Intel\u0027s SDM, the VMX\narchitecture doesn\u0027t require the CPU to flush the VMCS cache on INIT.  If\nan emergency reboot doesn\u0027t RESET CPUs, cached VMCSes could theoretically\nbe kept and only be written back to memory after the new kernel is booted,\ni.e. could effectively corrupt memory after reboot.\n\nOpportunistically remove the setting of the global pointer to NULL to make\ncheckpatch happy.",
      "id": "GSD-2023-52514",
      "modified": "2024-02-21T06:01:53.415081Z",
      "schema_version": "1.4.0"
    }
  },
  "namespaces": {
    "cve.org": {
      "CVE_data_meta": {
        "ASSIGNER": "cve@kernel.org",
        "ID": "CVE-2023-52514",
        "STATE": "REJECT"
      },
      "data_format": "MITRE",
      "data_type": "CVE",
      "data_version": "4.0",
      "description": {
        "description_data": [
          {
            "lang": "eng",
            "value": "** REJECT ** This CVE ID has been rejected or withdrawn by its CVE Numbering Authority."
          }
        ]
      }
    },
    "nvd.nist.gov": {
      "cve": {
        "descriptions": [
          {
            "lang": "en",
            "value": "Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority."
          }
        ],
        "id": "CVE-2023-52514",
        "lastModified": "2024-03-11T16:15:07.720",
        "metrics": {},
        "published": "2024-03-02T22:15:47.777",
        "references": [],
        "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "vulnStatus": "Rejected"
      }
    }
  }
}

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.

Action not permitted

CVE-2023-52514 (GCVE-0-2023-52514)

FKIE_CVE-2023-52514

GHSA-766R-W9PC-FW69

GSD-2023-52514

Tags

Sightings

Nomenclature