CVE-2021-47280

drm: Fix use-after-free read in drm_getunique()

HIGH
7
CVSS Score
Published: May 21, 2024 at 02:20 PM UTC
Updated: June 17, 2026 at 04:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: drm: Fix use-after-free read in drm_getunique() There is a time-of-check-to-time-of-use error in drm_getunique() due to retrieving file_priv->master prior to locking the device's master mutex. An example can be seen in the crash report of the use-after-free error found by Syzbot: https://syzkaller.appspot.com/bug?id=148d2f1dfac64af52ffd27b661981a540724f803 In the report, the master pointer was used after being freed. This is because another process had acquired the device's master mutex in drm_setmaster_ioctl(), then overwrote fpriv->master in drm_new_set_master(). The old value of fpriv->master was subsequently freed before the mutex was unlocked. To fix this, we lock the device's master mutex before retrieving the pointer from from fpriv->master. This patch passes the Syzbot reproducer test.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 4.14.2374.11 ≤ v < 4.14.2374.11 ≤ v < 4.19.1954.11 ≤ v < 5.10.444.11 ≤ v < 5.12.114.11 ≤ v < 5.134.11 ≤ v < 5.4.1264.15 ≤ v < 4.19.1954.20 ≤ v < 5.4.1265.11 ≤ v < 5.12.115.5 ≤ v < 5.10.445.13 rc15.13 rc25.13 rc35.13 rc45.13 rc55acc614ac47465fee6375a9af4740f618830762d
Vendor states this is fixed in 17dab9326ff263c62dab1dbac4492e2938a049e4 (fixed)
Vendor states this is fixed in 491d52e0078860b33b6c14f0a7ac74ca1b603bd6 (fixed)
Vendor states this is fixed in 7d233ba700ceb593905ea82b42dadb4ec8ef85e9 (fixed)
Vendor states this is fixed in b246b4c70c1250e7814f409b243000f9c0bf79a3 (fixed)
Vendor states this is fixed in b436acd1cf7fac0ba987abd22955d98025c80c2b (fixed)
Vendor states this is fixed in f773f8cccac13c7e7bbd9182e7996c727742488e (fixed)
Vendor states this is fixed in 4.11 (unaffected)
Vendor states this is fixed in 4.14.237 (unaffected)
Vendor states this is fixed in 4.19.195 (unaffected)
Vendor states this is fixed in 5.10.44 (unaffected)
Vendor states this is fixed in 5.12.11 (unaffected)
Vendor states this is fixed in 5.13 (unaffected)
Vendor states this is fixed in 5.4.126 (unaffected)

References (6)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/17dab9326ff263c62dab1dbac4492e2938a049e4
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/491d52e0078860b33b6c14f0a7ac74ca1b603bd6
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/7d233ba700ceb593905ea82b42dadb4ec8ef85e9
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/b246b4c70c1250e7814f409b243000f9c0bf79a3
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/b436acd1cf7fac0ba987abd22955d98025c80c2b
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/f773f8cccac13c7e7bbd9182e7996c727742488e

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
HIGH
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-367CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card