Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-48771

drm/vmwgfx: Fix stale file descriptors on failed usercopy

High7.8EPSS 0.21%
Published
Updated
Reserved
Assigned by
Linux

Description

In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: Fix stale file descriptors on failed usercopy A failing usercopy of the fence_rep object will lead to a stale entry in the file descriptor table as put_unused_fd() won't release it. This enables userland to refer to a dangling 'file' object through that still valid file descriptor, leading to all kinds of use-after-free exploitation scenarios. Fix this by deferring the call to fd_install() until after the usercopy has succeeded.

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-2022-48771, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (7 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: High 7.8.

Weakness

Affected products

  • Linux · Linux

    • affected c906965dee22d5e95d0651759ba107b420212a9f – < e8d092a62449dcfc73517ca43963d2b8f44d0516
    • affected c906965dee22d5e95d0651759ba107b420212a9f – < 0008a0c78fc33a84e2212a7c04e6b21a36ca6f4d
    • affected c906965dee22d5e95d0651759ba107b420212a9f – < 84b1259fe36ae0915f3d6ddcea6377779de48b82
    • affected c906965dee22d5e95d0651759ba107b420212a9f – < ae2b20f27732fe92055d9e7b350abc5cdf3e2414
    • affected c906965dee22d5e95d0651759ba107b420212a9f – < 6066977961fc6f437bc064f628cf9b0e4571c56c
    • affected c906965dee22d5e95d0651759ba107b420212a9f – < 1d833b27fb708d6fdf5de9f6b3a8be4bd4321565
    • affected c906965dee22d5e95d0651759ba107b420212a9f – < a0f90c8815706981c483a652a6aefca51a5e191c
  • Linux · Linux

    • affected 4.14
    • unaffected < 4.14
    • unaffected 4.14.264 – ≤ 4.14.*
    • unaffected 4.19.227 – ≤ 4.19.*
    • unaffected 5.4.175 – ≤ 5.4.*
    • unaffected 5.10.95 – ≤ 5.10.*
    • unaffected 5.15.18 – ≤ 5.15.*
    • unaffected 5.16.4 – ≤ 5.16.*
    • unaffected 5.17 – ≤ *

References (7)

Sources

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

Badge for a README or a ticket

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

Record last updated .