ghsa-w492-g7j4-gr3w
Vulnerability from github
Published
2024-05-21 18:31
Modified
2024-05-21 18:31
Details
In the Linux kernel, the following vulnerability has been resolved:
soc: qcom: llcc: Handle a second device without data corruption
Usually there is only one llcc device. But if there were a second, even a failed probe call would modify the global drv_data pointer. So check if drv_data is valid before overwriting it.
{ "affected": [], "aliases": [ "CVE-2023-52871" ], "database_specific": { "cwe_ids": [], "github_reviewed": false, "github_reviewed_at": null, "nvd_published_at": "2024-05-21T16:15:23Z", "severity": null }, "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nsoc: qcom: llcc: Handle a second device without data corruption\n\nUsually there is only one llcc device. But if there were a second, even\na failed probe call would modify the global drv_data pointer. So check\nif drv_data is valid before overwriting it.", "id": "GHSA-w492-g7j4-gr3w", "modified": "2024-05-21T18:31:23Z", "published": "2024-05-21T18:31:23Z", "references": [ { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52871" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/1143bfb9b055897975aeaea254da148e19524493" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/3565684309e54fa998ea27f37028d67cc3e1dff2" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/5e5b85ea0f4bc484bfe4cc73ead51fa48d2366a0" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/995ee1e84e8db7fa5dcdde7dfe0bd7bb6f9bbb8c" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/cc1a1dcb411fe224f48553cfdcdfe6e61395b69c" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/f0ef883cae309bc5e8cdfcdbc1b4822732ce20a8" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/f1a1bc8775b26345aba2be278118999e7f661d3d" } ], "schema_version": "1.4.0", "severity": [] }
Loading...
Loading...
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.