BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2021-47447High confidence

drm/msm/a3xx: fix error handling in a3xx_gpu_init()

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2021-34452

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: drm/msm/a3xx: fix error handling in a3xx_gpu_init() These error paths returned 1 on failure, instead of a negative error code. This would lead to an Oops in the caller. A second problem is that the check for "if (ret != -ENODATA)" did not work because "ret" was set to 1.

What

In the Linux kernel, the following vulnerability has been resolved: drm/msm/a3xx: fix error handling in a3xx_gpu_init() These error paths returned 1 on failure, instead of a negative error code. This would lead to an Oops in the caller. A second problem is that the check for "if (ret != -ENODATA)" did not work because "ret" was set to 1.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: drm/msm/a3xx: fix error handling in a3xx_gpu_init() These error paths returned 1 on failure, instead of a negative error code. This would lead to an Oops in the caller. A second problem is that the check for "if (ret != -ENODATA)" did not work because "ret" was set to 1.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2024-1197Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service und unspezifische Angriffe

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder unspezifische Angriffe durchzuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240529Security Bulletin 29 May 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 29 May 2024, published on 29 May 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0526Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2021-47438 Référence CVE CVE-2021-47439 https://www.cve.org/CVERecord?id=CVE-2021-47439 Référence CVE CVE-2021-47440 https://www.cve.org/CVERecord?id=CVE-2021-47440 Référence CVE CVE-2021-47441 https://www.cve.org/CVERecord?id=CVE-2021-47441 Référence CVE CVE-2021-47442 https://www.cve.org/CVERecord?id=CVE-2021-47442 Référence CVE CVE-2021-47443 https://www.cve.org/CVERecord?id=CVE-2021-47443 Référence CVE CVE-2021-47444 https://www.cve.org/CVERecord?id=CVE-2021-47444 Référence CVE CVE-2021-47445 https://www.cve.org/CVERecord?id=CVE-2021-47445 Référence CVE CVE-2021-47446 https://www.cve.org/CVERecord?id=CVE-2021-47446 Référence CVE CVE-2021-47447 https://www.cve.org/CVERecord?id=CVE-2021-47447 Référence CVE CVE-2021-47448 https://www.cve.org/CVERecord?id=CVE-2021-47448 Référence CVE CVE-2021-47449 https://www.cve.org/CVERecord?id=CVE-2021-47449 Référence CVE CVE-2021-47450 https://www.cve.org/CVERecord?id=CVE-2021-47450 Référence CVE CVE-2021-47451 https://www.cve.org/CVERecord?id=CVE-2021-47451 Référence CVE CVE-2021-47452 https://www.cve.org/CVERecord?id=CVE-2021-47452 Référence CVE CVE-2021-47453 https://www.cve.org/CVERecord?id=CVE-2021-47453 Référence CVE CVE-2021-47454 https://www.cve.org/CVERecord?id=CVE-2021-47454 Référence CVE CVE-2021-47455 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0496Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2021-47438 Référence CVE CVE-2021-47439 https://www.cve.org/CVERecord?id=CVE-2021-47439 Référence CVE CVE-2021-47440 https://www.cve.org/CVERecord?id=CVE-2021-47440 Référence CVE CVE-2021-47441 https://www.cve.org/CVERecord?id=CVE-2021-47441 Référence CVE CVE-2021-47442 https://www.cve.org/CVERecord?id=CVE-2021-47442 Référence CVE CVE-2021-47443 https://www.cve.org/CVERecord?id=CVE-2021-47443 Référence CVE CVE-2021-47444 https://www.cve.org/CVERecord?id=CVE-2021-47444 Référence CVE CVE-2021-47445 https://www.cve.org/CVERecord?id=CVE-2021-47445 Référence CVE CVE-2021-47446 https://www.cve.org/CVERecord?id=CVE-2021-47446 Référence CVE CVE-2021-47447 https://www.cve.org/CVERecord?id=CVE-2021-47447 Référence CVE CVE-2021-47448 https://www.cve.org/CVERecord?id=CVE-2021-47448 Référence CVE CVE-2021-47449 https://www.cve.org/CVERecord?id=CVE-2021-47449 Référence CVE CVE-2021-47450 https://www.cve.org/CVERecord?id=CVE-2021-47450 Référence CVE CVE-2021-47451 https://www.cve.org/CVERecord?id=CVE-2021-47451 Référence CVE CVE-2021-47452 https://www.cve.org/CVERecord?id=CVE-2021-47452 Référence CVE CVE-2021-47453 https://www.cve.org/CVERecord?id=CVE-2021-47453 Référence CVE CVE-2021-47454 https://www.cve.org/CVERecord?id=CVE-2021-47454 Référence CVE CVE-2021-47455 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-021951Linux の Linux Kernel における脆弱性

Linux の Linux Kernel には、不特定の脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Linux: 5785dd7a8ef0de8049f40a1a109de6a1bf17b479 < d59e44e7821a8f2bb6f2e846b9167397a5f01608, 5785dd7a8ef0de8049f40a1a109de6a1bf17b479 < 3eda901995371d390ef82d0b6462f4ea8efbcfdf, 5.11
Fixed
Linux: < 5.11, 5.14.14 ≤ 5.14.*, 5.15 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 22 May 2024 · Last source change 5 Aug 2026, 08:47 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2021-34452
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceUnavailable
NVD statusNVD modified after enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2021-34452↗CVE authority or vendor reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2021-47447 · cve.blacktree.nl