CVE-2023-54217 (GCVE-0-2023-54217)
Vulnerability from cvelistv5 – Published: 2025-12-30 12:11 – Updated: 2025-12-30 12:11
VLAI?
Title
Revert "drm/msm: Add missing check and destroy for alloc_ordered_workqueue"
Summary
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/
Severity ?
No CVSS data available.
Assigner
References
Impacted products
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/msm/msm_drv.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "9078b434587722a6f2958dc1d536af6e39634db9",
"status": "affected",
"version": "643b7d0869cc7f1f7a5ac7ca6bd25d88f54e31d0",
"versionType": "git"
},
{
"lessThan": "dfa70344d1b5f5ff08525a8c872c8dd5e82fc5d9",
"status": "affected",
"version": "643b7d0869cc7f1f7a5ac7ca6bd25d88f54e31d0",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/gpu/drm/msm/msm_drv.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.3"
},
{
"lessThan": "6.3",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.3.*",
"status": "unaffected",
"version": "6.3.2",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.4",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.3.2",
"versionStartIncluding": "6.3",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.4",
"versionStartIncluding": "6.3",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "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/"
}
],
"providerMetadata": {
"dateUpdated": "2025-12-30T12:11:13.390Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/9078b434587722a6f2958dc1d536af6e39634db9"
},
{
"url": "https://git.kernel.org/stable/c/dfa70344d1b5f5ff08525a8c872c8dd5e82fc5d9"
}
],
"title": "Revert \"drm/msm: Add missing check and destroy for alloc_ordered_workqueue\"",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2023-54217",
"datePublished": "2025-12-30T12:11:13.390Z",
"dateReserved": "2025-12-30T12:06:44.501Z",
"dateUpdated": "2025-12-30T12:11:13.390Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"nvd": "{\"cve\":{\"id\":\"CVE-2023-54217\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-12-30T13:16:09.960\",\"lastModified\":\"2025-12-31T20:42:43.210\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"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/\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/9078b434587722a6f2958dc1d536af6e39634db9\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/dfa70344d1b5f5ff08525a8c872c8dd5e82fc5d9\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
}
}
Loading…
Loading…
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.
Loading…
Loading…