CVE-2021-47354

Home/CVE/In the Linux kernel, the following vulnerability has been resolved: drm/sched: Avoid data corruptions Wait for all dep

CVE

In the Linux kernel, the following vulnerability has been resolved: drm/sched: Avoid data corruptions Wait for all dep

In the Linux kernel, the following vulnerability has been resolved: drm/sched: Avoid data corruptions Wait for all dependencies of a job to complete before killing it to avoid data corruptions.

CRITICAL · CVSS 9.1 EPSS 0.00059

Schedule remediation

SSVC automatable: yes - attacks can be scripted at scale
CVSS base score ≥ 7.0

Sigma rules0 YARA rules0

Look this up elsewhere - one-click external pivots

NVD CVE.org CISA Vulners Exploit-DB GitHub PoC VulnCheck KEV GreyNoise

▸ How to read a CVE - triage first, then detect and patch

This page is every public fact about CVE-2021-47354, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.

Triage: should I act now? Four signals, and they are not interchangeable:

CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.

How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.

Then what - two workflows:

Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.

Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).

View attack path from CVE-2021-47354

◆

ATT&CK techniques

Techniques this CVE enables - linked via CWECAPECATT&CK. High◆ = named directly in ATT&CK or Nuclei templates.

T1190 · Exploit Public-Facing Application

▤ Build a SIEM detection for these techniques

⬡

Weakness Classification

CWE-787Out-of-bounds Write

▤

Affected Products & Versions

linux kernel< 5.4.133
linux kernel>= 5.5 and < 5.10.51
linux kernel>= 5.11 and < 5.12.18
linux kernel>= 5.13 and < 5.13.3

▤

Affected Packages

Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.

Ubuntu:18.04:LTS linux-aws-5.4 fixed in 5.4.0-1056.59~18.04.1

Ubuntu:18.04:LTS linux-azure-5.4 fixed in 5.4.0-1058.60~18.04.1

Ubuntu:18.04:LTS linux-gcp-5.4 fixed in 5.4.0-1052.56~18.04.1

Ubuntu:18.04:LTS linux-hwe-5.4 fixed in 5.4.0-84.94~18.04.1

Ubuntu:18.04:LTS linux-ibm-5.4 fixed in 5.4.0-1010.11~18.04.2

Ubuntu:18.04:LTS linux-oracle-5.4 fixed in 5.4.0-1054.58~18.04.1

Ubuntu:18.04:LTS linux-raspi-5.4 fixed in 5.4.0-1043.47~18.04.1

Ubuntu:20.04:LTS linux fixed in 5.4.0-84.94

Ubuntu:20.04:LTS linux-aws fixed in 5.4.0-1056.59

Ubuntu:20.04:LTS linux-aws-5.11

Ubuntu:20.04:LTS linux-aws-5.13

Ubuntu:20.04:LTS linux-aws-5.15 fixed in 5.15.0-1014.18~20.04.1

Ubuntu:20.04:LTS linux-aws-5.8

Ubuntu:20.04:LTS linux-azure fixed in 5.4.0-1058.60

Ubuntu:20.04:LTS linux-azure-5.11

Ubuntu:20.04:LTS linux-azure-5.13

Ubuntu:20.04:LTS linux-azure-5.15 fixed in 5.15.0-1007.8~20.04.1

Ubuntu:20.04:LTS linux-azure-5.8

Ubuntu:20.04:LTS linux-azure-fde

Ubuntu:20.04:LTS linux-azure-fde-5.15 fixed in 5.15.0-1019.24~20.04.1.1

Ubuntu:20.04:LTS linux-bluefield fixed in 5.4.0-1019.22

Ubuntu:20.04:LTS linux-gcp fixed in 5.4.0-1052.56

Ubuntu:20.04:LTS linux-gcp-5.11

Ubuntu:20.04:LTS linux-gcp-5.13

Ubuntu:20.04:LTS linux-gcp-5.15 fixed in 5.15.0-1006.9~20.04.1

Ubuntu:20.04:LTS linux-gcp-5.8

Ubuntu:20.04:LTS linux-gke

Ubuntu:20.04:LTS linux-gke-5.15

Ubuntu:20.04:LTS linux-gkeop fixed in 5.4.0-1023.24

Ubuntu:20.04:LTS linux-gkeop-5.15 fixed in 5.15.0-1003.5~20.04.2

Ubuntu:20.04:LTS linux-hwe-5.11

Ubuntu:20.04:LTS linux-hwe-5.13

Ubuntu:20.04:LTS linux-hwe-5.15 fixed in 5.15.0-33.34~20.04.1

Ubuntu:20.04:LTS linux-hwe-5.8

Ubuntu:20.04:LTS linux-ibm fixed in 5.4.0-1004.5

Ubuntu:20.04:LTS linux-ibm-5.15 fixed in 5.15.0-1033.36~20.04.1

Ubuntu:20.04:LTS linux-intel-5.13

Ubuntu:20.04:LTS linux-intel-iotg-5.15 fixed in 5.15.0-1003.5~20.04.1

Ubuntu:20.04:LTS linux-iot fixed in 5.4.0-1001.3

Ubuntu:20.04:LTS linux-kvm fixed in 5.4.0-1046.48

📦

Fixed versions by distribution

The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
suse sle15kernel-64kb fixed in 0:5.3.18-150300.59.164.1
suse sle15kernel-default fixed in 0:5.3.18-150300.59.164.1
suse sle15kernel-default-base fixed in 0:5.3.18-150300.59.164.1.150300.18.96.1
suse sle15kernel-default-devel open
suse sle15kernel-default-livepatch fixed in 0:5.3.18-150200.24.194.1
suse sle15kernel-default-man open
suse sle15kernel-devel open
suse sle15kernel-docs fixed in 0:5.3.18-150300.59.164.1
suse sle15kernel-livepatch-5_3_18-150200_24_194-default fixed in 0:1-150200.5.3.1
suse sle15kernel-livepatch-5_3_18-150300_59_164-default fixed in 0:1-150300.7.3.1
suse sle15kernel-macros open
suse sle15kernel-obs-build fixed in 0:5.3.18-150300.59.164.1
suse sle15kernel-preempt fixed in 0:5.3.18-150200.24.194.1
suse sle15kernel-source fixed in 0:5.3.18-150200.24.194.1
suse sle15kernel-syms fixed in 0:5.3.18-150200.24.194.1
suse sle15kernel-zfcpdump fixed in 0:5.3.18-150300.59.164.1
suse sle15reiserfs-kmp-default fixed in 0:5.3.18-150300.59.164.1

▣

Scoring & Timeline

9.1

CRITICAL · CVSS v3.1 · 416baaa9-dc9f-4396-8d5f-8c081fb06d67

View on NVD

Attack Vector

Network Adjacent Local Physical

Attack Complexity

Low High

Privileges Required

None Low High

User Interaction

None Required

Scope

Unchanged Changed

Confidentiality

None Low High

Integrity

None Low High

Availability

None Low High

Published to NVD21 May 2024 · 03:15 PM

CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

SSVC triage · cisa-vulnrichment

Exploitation

none

Automatable

yes

Technical impact

partial

SSVC asks the questions that actually drive patch urgency: is it being exploited, can attacks be automated, and how total is the impact.

⚑

Vendor Advisories

suse-csafSUSE-SU-2024:2561-1
suse-csafSUSE-SU-2024:2381-1
suse-csafSUSE-SU-2024:2360-1
suse-csafSUSE-SU-2024:2183-1
suse-csafSUSE-SU-2024:2185-1
Show all 6 vendor advisoriessuse-csafSUSE-SU-2024:2010-1

🔗

References & Sources

Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.

https://git.kernel.org/stable/c/0687411e2a8858262de2fc4a1d576016fd77292ePatch

https://git.kernel.org/stable/c/0b10ab80695d61422337ede6ff496552d8ace99dPatch

https://git.kernel.org/stable/c/50d7e03ad487cc45fc85164a299b945a41756ac0Patch

https://git.kernel.org/stable/c/a8e23e3c1ff9ec598ab1b3a941ace6045027781fPatch

https://git.kernel.org/stable/c/c32d0f0e164ffab2a56c7cf8e612584b4b740e2ePatch