ghsa-gj73-539r-gfvc
Vulnerability from github
In the Linux kernel, the following vulnerability has been resolved:
Revert "drm/msm: Add missing check and destroy for alloc_ordered_workqueue"
This reverts commit 643b7d0869cc7f1f7a5ac7ca6bd25d88f54e31d0.
A recent patch that tried to fix up the msm_drm_init() paths with respect to the workqueue but only ended up making things worse:
First, the newly added calls to msm_drm_uninit() on early errors would trigger NULL-pointer dereferences, for example, as the kms pointer would not have been initialised. (Note that these paths were also modified by a second broken error handling patch which in effect cancelled out this part when merged.)
Second, the newly added allocation sanity check would still leak the previously allocated drm device.
Instead of trying to salvage what was badly broken (and clearly not tested), let's revert the bad commit so that clean and backportable fixes can be added in its place.
Patchwork: https://patchwork.freedesktop.org/patch/525107/
{
"affected": [],
"aliases": [
"CVE-2023-54217"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-12-30T13:16:09Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nRevert \"drm/msm: Add missing check and destroy for alloc_ordered_workqueue\"\n\nThis reverts commit 643b7d0869cc7f1f7a5ac7ca6bd25d88f54e31d0.\n\nA recent patch that tried to fix up the msm_drm_init() paths with\nrespect to the workqueue but only ended up making things worse:\n\nFirst, the newly added calls to msm_drm_uninit() on early errors would\ntrigger NULL-pointer dereferences, for example, as the kms pointer would\nnot have been initialised. (Note that these paths were also modified by\na second broken error handling patch which in effect cancelled out this\npart when merged.)\n\nSecond, the newly added allocation sanity check would still leak the\npreviously allocated drm device.\n\nInstead of trying to salvage what was badly broken (and clearly not\ntested), let\u0027s revert the bad commit so that clean and backportable\nfixes can be added in its place.\n\nPatchwork: https://patchwork.freedesktop.org/patch/525107/",
"id": "GHSA-gj73-539r-gfvc",
"modified": "2025-12-30T15:30:31Z",
"published": "2025-12-30T15:30:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-54217"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/9078b434587722a6f2958dc1d536af6e39634db9"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/dfa70344d1b5f5ff08525a8c872c8dd5e82fc5d9"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- 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.