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-2022-48710drm/radeon: fix a possible null pointer dereference

Description

In the Linux kernel, the following vulnerability has been resolved: drm/radeon: fix a possible null pointer dereference In radeon_fp_native_mode(), the return value of drm_mode_duplicate() is assigned to mode, which will lead to a NULL pointer dereference on failure of drm_mode_duplicate(). Add a check to avoid npd. The failure status of drm_cvt_mode() on the other path is checked too.

Timeline

  1. ID reserved

    By Linux

  2. · 18 days later

    Published

  3. · 24 months 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-2022-48710, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.26% · top 82% of all CVEs (13 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 771fe6b912fca54f03e8a72eb63058b582775362 – < b33f7d99c9226892c7794dc2500fae35966020c9
    • affected 771fe6b912fca54f03e8a72eb63058b582775362 – < 16a0f0b63c4c7eb46fc4c3f00bf2836e6ee46a9f
    • affected 771fe6b912fca54f03e8a72eb63058b582775362 – < 8a89bfeef9abe93371e3ea8796377f2d132eee29
    • affected 771fe6b912fca54f03e8a72eb63058b582775362 – < 28fd384c78d7d8ed8af0d086d778c3e438ba7f60
    • affected 771fe6b912fca54f03e8a72eb63058b582775362 – < fee8ae0a0bb66eb7730c22f44fbd7203f63c2eab
    • affected 771fe6b912fca54f03e8a72eb63058b582775362 – < 7b7fba107b2c4ec7673d0f45bdbb9d1af697d9b9
    • affected 771fe6b912fca54f03e8a72eb63058b582775362 – < e938d24f0b7392e142b8aa434f18590d99dbe479
    • affected 771fe6b912fca54f03e8a72eb63058b582775362 – < 140d9807b96e1303f6f2675a7ae8710a2094bd17
    • affected 771fe6b912fca54f03e8a72eb63058b582775362 – < a2b28708b645c5632dc93669ab06e97874c8244f
  • Linux · Linux

    • affected 2.6.31
    • unaffected < 2.6.31
    • unaffected 4.9.318 – ≤ 4.9.*
    • unaffected 4.14.283 – ≤ 4.14.*
    • unaffected 4.19.247 – ≤ 4.19.*
    • unaffected 5.4.198 – ≤ 5.4.*
    • unaffected 5.10.122 – ≤ 5.10.*
    • unaffected 5.15.47 – ≤ 5.15.*
    • unaffected 5.17.15 – ≤ 5.17.*
    • unaffected 5.18.4 – ≤ 5.18.*
    • unaffected 5.19 – ≤ *

References

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .