LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54199: drm/msm/adreno: Fix null ptr access in adreno_gpu_cleanup()

In the Linux kernel, the following vulnerability has been resolved: drm/msm/adreno: Fix null ptr access in adreno_gpu_cleanup() Fix the below kernel panic due to null pointer access: [ 18.504431] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000048 [ 18.513464] Mem abort info: [ 18.516346] ESR = 0x0000000096000005 [ 18.520204] EC = 0x25: DABT (current EL), IL = 32 bits [ 18.525706] SET = 0, FnV = 0 [ 18.528878] EA = 0, S1PTW = 0 [ 18.532117] FSC = 0x05: level 1 translation fault [ 18.537138] Data abort info: [ 18.540110] ISV = 0, ISS = 0x00000005 [ 18.544060] CM = 0, WnR = 0 [ 18.547109] user pgtable: 4k pages, 39-bit VAs, pgdp=0000000112826000 [ 18.553738] [0000000000000048] pgd=0000000000000000, p4d=0000000000000000, pud=0000000000000000 [ 18.562690] Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP **Snip** [ 18.696758] Call trace: [ 18.699278] adreno_gpu_cleanup+0x30/0x88 [ 18.703396] a6xx_destroy+0xc0/0x130 [ 18.707066] a6xx_gpu_init+0x308/0x424 [ 18.710921] adreno_bind+0x178/0x288 [ 18.714590] component_bind_all+0xe0/0x214 [ 18.718797] msm_drm_bind+0x1d4/0x614 [ 18.722566] try_to_bring_up_aggregate_device+0x16c/0x1b8 [ 18.728105] __component_add+0xa0/0x158 [ 18.732048] component_add+0x20/0x2c [ 18.735719] adreno_probe+0x40/0xc0 [ 18.739300] platform_probe+0xb4/0xd4 [ 18.743068] really_probe+0xfc/0x284 [ 18.746738] __driver_probe_device+0xc0/0xec [ 18.751129] driver_probe_device+0x48/0x110 [ 18.755421] __device_attach_driver+0xa8/0xd0 [ 18.759900] bus_for_each_drv+0x90/0xdc [ 18.763843] __device_attach+0xfc/0x174 [ 18.767786] device_initial_probe+0x20/0x2c [ 18.772090] bus_probe_device+0x40/0xa0 [ 18.776032] deferred_probe_work_func+0x94/0xd0 [ 18.780686] process_one_work+0x190/0x3d0 [ 18.784805] worker_thread+0x280/0x3d4 [ 18.788659] kthread+0x104/0x1c0 [ 18.791981] ret_from_fork+0x10/0x20 [ 18.795654] Code: f9400408 aa0003f3 aa1f03f4 91142015 (f9402516) [ 18.801913] ---[ end trace 0000000000000000 ]--- [ 18.809039] Kernel panic - not syncing: Oops: Fatal exception Patchwork: https://patchwork.freedesktop.org/patch/515605/

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash a system when the Adreno GPU driver cleanup path dereferences a null pointer. The provided evidence shows a kernel panic, so the business concern is availability and device stability on affected Linux builds using this driver.

Executive priority

Treat this as an availability and platform-stability issue for Linux devices using affected Adreno GPU driver code. It is not currently supported as an actively exploited internet-facing threat by the supplied evidence.

Technical view

CVE-2023-54199 is a null pointer access in drm/msm/adreno, specifically adreno_gpu_cleanup(). The trace shows failure during Adreno GPU initialization and destruction paths, ending in a fatal kernel panic. Stable kernel commits are referenced as the fix lineage.

Likely exposure

Exposure appears limited to affected Linux kernel versions or commits that include the msm/adreno DRM driver path. Systems without this driver enabled or hardware path present are less likely exposed, but the source bundle does not provide a complete product matrix.

Exploitation context

The source bundle does not show active exploitation, and KEV is false. Evidence is a kernel panic trace tied to driver probe or cleanup behavior, not a remote attack path or privilege-escalation technique.

Researcher notes

The key evidence is the null dereference at adreno_gpu_cleanup() and the call trace through a6xx_destroy(), a6xx_gpu_init(), and adreno_bind(). No CVSS, CWE, exploitability analysis, or distribution-specific package status is provided.

Mitigation direction

  • Check whether deployed kernels include the affected drm/msm/adreno code path.
  • Update to a kernel containing the referenced stable fixes.
  • Prioritize devices where GPU driver crashes affect boot or service availability.
  • Monitor Linux vendor advisories for distribution-specific fixed kernel packages.
  • Avoid assuming a workaround if the vendor has not published one.

Validation and detection

  • Inventory kernel versions and compare them with affected and fixed versions.
  • Confirm whether the msm/adreno DRM driver is built or loaded.
  • Review boot logs for adreno_gpu_cleanup or related kernel panic traces.
  • Map vendor kernel packages to the referenced stable commit fixes.
  • Test fixed kernels on representative affected hardware before broad rollout.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-54199 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
7Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux594726c93841c9e6182d3af540c6f317464bc23d, 17e822f7591fb66162aca07685dc0b01468e5480, 17e822f7591fb66162aca07685dc0b01468e5480, 17e822f7591fb66162aca07685dc0b01468e5480, 17e822f7591fb66162aca07685dc0b01468e5480, 17e822f7591fb66162aca07685dc0b01468e5480unaffected
LinuxLinux5.9, 0, 5.10.173, 5.15.99, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.