{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90363 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90363 is an use after free vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-90363 and fix it if it is affected.\n\nWhat it is: CVE-2026-90363 is an use after free vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-90363 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-90363/ (Markdown: https://insights.sbomify.com/CVE-2026-90363/index.md)","id":"CVE-2026-90363","markdown":"https://insights.sbomify.com/CVE-2026-90363/index.md","name":"CVE-2026-90363","record":{"aliases":["BELL-CVE-2026-90363","DEBIAN-CVE-2026-90363","GHSA-356c-wqmf-cf5h","UBUNTU-CVE-2026-90363"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A use-after-free vulnerability in the Linux kernel MSM DRM driver causes a crash when KMS initialization fails, leading to denial of service.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/msm: don't tear down KMS twice when KMS init fails\n\nWhen priv-\u003ekms_init() (mdp4_kms_init() / mdp5_kms_init()) fails partway\nthrough, both display drivers already tear their KMS state down via\nmdp4_destroy() / mdp5_kms_destroy() before returning the error. The\ncommon error path in msm_drm_init() then runs msm_drm_uninit() -\u003e\nmsm_drm_kms_uninit(), which tries to destroy the very same KMS a second\ntime, which causes a use-after-free crash.\n\nBring MDP4/MDP5 in line with the DPU driver whose dpu_kms_init() doesn't\nperform error cleanup on the failure. Let the common path own the\ncleanup, instead of freeing the KMS from their error paths.\n\nThe crash trace for the reference:\n\n  __lock_acquire from lock_acquire (kernel/locking/lockdep.c:5906 kernel/locking/lockdep.c:5863)\n  lock_acquire from touch_wq_lockdep_map (kernel/workqueue.c:4094 (discriminator 1))\n  touch_wq_lockdep_map from __flush_workqueue (kernel/workqueue.c:4136)\n  __flush_workqueue from msm_drm_kms_uninit (drivers/gpu/drm/msm/msm_kms.c:243 (discriminator 33))\n  msm_drm_kms_uninit from msm_drm_uninit (drivers/gpu/drm/msm/msm_drv.c:93)\n  msm_drm_uninit from msm_drm_init (drivers/gpu/drm/msm/msm_drv.c:184)\n  msm_drm_init from try_to_bring_up_aggregate_device (drivers/base/component.c:249 drivers/base/component.c:227)\n  try_to_bring_up_aggregate_device from __component_add (drivers/base/component.c:269 drivers/base/component.c:748)\n  __component_add from dsi_host_attach (drivers/gpu/drm/msm/dsi/dsi_host.c:1739)\n  dsi_host_attach from mipi_dsi_attach (drivers/gpu/drm/drm_mipi_dsi.c:383)\n  mipi_dsi_attach from sharp_nt_panel_probe (drivers/gpu/drm/panel/panel-sharp-ls043t1le01.c:247)\n\nPatchwork: https://patchwork.freedesktop.org/patch/742068/","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"drm/msm: don't tear down KMS twice when KMS init fails","id":"CVE-2026-90363","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"ACPI: processor: Unregister cpufreq notifier on init failure","id":"CVE-2026-90364"},"packages":[],"prev":{"headline":"drm/msm/dsi: Drop dev_pm_opp_set_rate(0)","id":"CVE-2026-90362"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A use-after-free vulnerability in the Linux kernel MSM DRM driver causes a crash when KMS initialization fails, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-90363/"}