CVE-2023-54217
Last modified
CVE-2023-54217 is a vulnerability of currently unknown severity. 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/. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
Description
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/
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 643b7d0869cc7f1f7a5ac7ca6bd25d88f54e31d0, < 9078b434587722a6f2958dc1d536af6e39634db9; >= 643b7d0869cc7f1f7a5ac7ca6bd25d88f54e31d0, < dfa70344d1b5f5ff08525a8c872c8dd5e82fc5d9 |
| Linux | Linux | 6.3 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2023-54217?
How severe is CVE-2023-54217?
How do I fix CVE-2023-54217?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-54211In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54212Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2023-54213In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54214In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2023-54215In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54216In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-54218In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54219In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2023-5422The functions to fetch e-mail via POP3 or IMAP as well as se…9.1
- CVE-2023-54220In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2023-54221In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54222In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2023-54217?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
