CVE-2021-47490 json
drm/ttm: fix memleak in ttm_transfered_destroy
published 2024-05-22 2 y ago modified 2026-06-17 4 mo ago also EUVD-2021-34494
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 10%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
drm/ttm: fix memleak in ttm_transfered_destroy
We need to cleanup the fences for ghost objects as well.
Bug: https://bugzilla.kernel.org/show_bug.cgi?id=214029 Bug: https://bugzilla.kernel.org/show_bug.cgi?id=214447
Patch / fix
- Linux Linux 5.14.16, 5.15
- linux Debian 14, Debian 13, Debian 12 5.15.3-1
debian advisories DEBIAN-CVE-2021-47490
- dtb-aarch64 openSUSE Leap 15.5 5.14.21-150500.55.68.1
- kernel-64kb SLE Module for Basesystem 15 SP5, openSUSE Leap 15.5 5.14.21-150500.55.68.1
- kernel-syms SLE Module for Development Tools 15 SP5, openSUSE Leap 15.5 5.14.21-150500.55.68.1
- kernel-obs-qa openSUSE Leap 15.5 5.14.21-150500.55.68.1
- kernel-source SLE Module for Development Tools 15 SP5, SLE Module for Basesystem 15 SP5, openSUSE Leap 15.5 5.14.21-150500.55.68.1
- kernel-default SLE Workstation Extension 15 SP5, SLE Module for Legacy 15 SP5, SLE Module for Basesystem 15 SP5 +4 more 5.14.21-150500.55.68.1
- kernel-kvmsmall openSUSE Leap 15.5 5.14.21-150500.55.68.1
- kernel-zfcpdump SLE Module for Basesystem 15 SP5, openSUSE Leap 15.5 5.14.21-150500.55.68.1
suse advisories SUSE-SU-2024:2190-1SUSE-SU-2024:2189-1SUSE-SU-2024:2019-1SUSE-SU-2024:2011-1SUSE-SU-2024:2008-1
- git.kernel.org/stable/c/132a3d998d6753047f22152731fba2b0d6b463dd commit
- git.kernel.org/stable/c/0db55f9a1bafbe3dac750ea669de9134922389b5 commit
- git.kernel.org/stable/c/bd99782f3ca491879e8524c89b1c0f40071903bd commit
- git.kernel.org/stable/c/960b1fdfc39aba8f41e9e27b2de0c925c74182d9 commit
- git.kernel.org/stable/c/c21b4002214c1c7e7b627b9b53375612f7aab6db commit
- git.kernel.org/stable/c/bbc920fb320f1c241cc34ac85edaa0058922246a commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2021-47490 updated cvss 4.1
kernel: drm/ttm: fix memleak in ttm_transfered_destroy
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 moreaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-401 Missing Release of Memory after Effective Lifetime
- Technology feeds
References
-
git.kernel.org
/stable/c/132a3d998d6753047f22152731fba2b0d6b463dd
patch
-
git.kernel.org
/stable/c/0db55f9a1bafbe3dac750ea669de9134922389b5
patch
-
git.kernel.org
/stable/c/bd99782f3ca491879e8524c89b1c0f40071903bd
patch
-
git.kernel.org
/stable/c/960b1fdfc39aba8f41e9e27b2de0c925c74182d9
patch
-
git.kernel.org
/stable/c/c21b4002214c1c7e7b627b9b53375612f7aab6db
patch
-
git.kernel.org
/stable/c/bbc920fb320f1c241cc34ac85edaa0058922246a
patch
Sources
- CVE List CVE-2021-47490
- NVD CVE-2021-47490
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.