---
id: CVE-2026-90363
title: |-
  In the Linux kernel, the following vulnerability has been resolved:

  drm/msm: don't tear down KMS twice when KMS init fails

  When priv->kms_init() (mdp4_kms_init() / mdp5_kms_init()) fails partway
  through, both display drivers already te…
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  drm/msm: don't tear down KMS twice when KMS init fails

  When priv->kms_init() (mdp4_kms_init() / mdp5_kms_init()) fails partway
  through, both display drivers already te…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 506efcba31296e9cbc4f8f148eec1e4b29039931 <
    08827aa40f0ee9d37dcff8d6acb340b970051486
  - >-
    Linux >= 506efcba31296e9cbc4f8f148eec1e4b29039931 <
    e2a99fa93b400dfbb9598103249f71969501094a
  - >-
    Linux >= 506efcba31296e9cbc4f8f148eec1e4b29039931 <
    93c125e4ea98fb25f927ba5a334d85845127d667
  - Linux 6.7
published: '2026-09-17'
updated: '2026-09-17'
sourceUpdated: '2026-09-17T17:17:35.353'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-90363'
references:
  - url: 'https://git.kernel.org/stable/c/08827aa40f0ee9d37dcff8d6acb340b970051486'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/93c125e4ea98fb25f927ba5a334d85845127d667'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/e2a99fa93b400dfbb9598103249f71969501094a'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-17T16:21:47.811Z'
epss: 0.00206
epssPercentile: 0.09502
---

## Overview

In the Linux kernel, the following vulnerability has been resolved:

drm/msm: don't tear down KMS twice when KMS init fails

When priv->kms_init() (mdp4_kms_init() / mdp5_kms_init()) fails partway
through, both display drivers already tear their KMS state down via
mdp4_destroy() / mdp5_kms_destroy() before returning the error. The
common error path in msm_drm_init() then runs msm_drm_uninit() ->
msm_drm_kms_uninit(), which tries to destroy the very same KMS a second
time, which causes a use-after-free crash.

Bring MDP4/MDP5 in line with the DPU driver whose dpu_kms_init() doesn't
perform error cleanup on the failure. Let the common path own the
cleanup, instead of freeing the KMS from their error paths.

The crash trace for the reference:

  __lock_acquire from lock_acquire (kernel/locking/lockdep.c:5906 kernel/locking/lockdep.c:5863)
  lock_acquire from touch_wq_lockdep_map (kernel/workqueue.c:4094 (discriminator 1))
  touch_wq_lockdep_map from __flush_workqueue (kernel/workqueue.c:4136)
  __flush_workqueue from msm_drm_kms_uninit (drivers/gpu/drm/msm/msm_kms.c:243 (discriminator 33))
  msm_drm_kms_uninit from msm_drm_uninit (drivers/gpu/drm/msm/msm_drv.c:93)
  msm_drm_uninit from msm_drm_init (drivers/gpu/drm/msm/msm_drv.c:184)
  msm_drm_init from try_to_bring_up_aggregate_device (drivers/base/component.c:249 drivers/base/component.c:227)
  try_to_bring_up_aggregate_device from __component_add (drivers/base/component.c:269 drivers/base/component.c:748)
  __component_add from dsi_host_attach (drivers/gpu/drm/msm/dsi/dsi_host.c:1739)
  dsi_host_attach from mipi_dsi_attach (drivers/gpu/drm/drm_mipi_dsi.c:383)
  mipi_dsi_attach from sharp_nt_panel_probe (drivers/gpu/drm/panel/panel-sharp-ls043t1le01.c:247)

Patchwork: https://patchwork.freedesktop.org/patch/742068/

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.