Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-49901drm/msm/adreno: Assign msm_gpu->pdev earlier to avoid nullptrs

Description

In the Linux kernel, the following vulnerability has been resolved: drm/msm/adreno: Assign msm_gpu->pdev earlier to avoid nullptrs There are some cases, such as the one uncovered by Commit 46d4efcccc68 ("drm/msm/a6xx: Avoid a nullptr dereference when speedbin setting fails") where msm_gpu_cleanup() : platform_set_drvdata(gpu->pdev, NULL); is called on gpu->pdev == NULL, as the GPU device has not been fully initialized yet. Turns out that there's more than just the aforementioned path that causes this to happen (e.g. the case when there's speedbin data in the catalog, but opp-supported-hw is missing in DT). Assigning msm_gpu->pdev earlier seems like the least painful solution to this, therefore do so. Patchwork: https://patchwork.freedesktop.org/patch/602742/

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-49901, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 0cf6c71d70d8aa39b8fd0e39c9009602a0e0d300 – < 4a48e2e501267c8d0a9a10ada41d960ddb2dae22
    • affected 0cf6c71d70d8aa39b8fd0e39c9009602a0e0d300 – < 542e679cd4ec93c959b014df9c31b4888e92bac8
    • affected 0cf6c71d70d8aa39b8fd0e39c9009602a0e0d300 – < 24168aae5a5010fa7d5068a318366e847ec3ad1e
    • affected 0cf6c71d70d8aa39b8fd0e39c9009602a0e0d300 – < 9288a9676c529ad9c856096db68fad812499bc4a
    • affected 0cf6c71d70d8aa39b8fd0e39c9009602a0e0d300 – < 9773737375b20070ea935203fd66cb9fa17c5acb
    • affected 0cf6c71d70d8aa39b8fd0e39c9009602a0e0d300 – < e8ac2060597a5768e4699bb61d604b4c09927b85
    • affected 0cf6c71d70d8aa39b8fd0e39c9009602a0e0d300 – < 16007768551d5bfe53426645401435ca8d2ef54f
  • Linux · Linux

    • affected 3.12
    • unaffected < 3.12
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.55 – ≤ 6.6.*
    • unaffected 6.10.14 – ≤ 6.10.*
    • unaffected 6.11.3 – ≤ 6.11.*
    • unaffected 6.12 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-49901 badge
[![CVE-2024-49901](https://cveledger.app/badge/CVE-2024-49901.svg)](https://cveledger.app/cve/CVE-2024-49901)

Record last updated .