medium CVSS 5.5

CVE-2021-47447·Kernel vulnerability

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.

Severity
medium
Software
Kernel
Fixed in
5.14.14
Published
2024-05-22

Affected versions

From: 5.11

Until: 5.14.14

Fixed in: 5.14.14

How to fix this CVE

Update your Linux kernel to version 5.14.14 or later to resolve improper error handling in the Adreno A3xx GPU driver initialization. This patch corrects error return values that were causing kernel panics when GPU initialization failed. Systems running kernel versions 5.11 through 5.14.13 should prioritize this update to prevent unexpected system crashes.

sudo dnf update kernel kernel-devel

Defensia detects this vulnerability

How to check if you are affected

  1. Step 1: Check your kernel version with `uname -r` and verify if it falls between 5.11 and 5.14.13
  2. Step 2: Confirm if you have Adreno A3xx GPU hardware by checking `lspci | grep -i adreno` or `cat /proc/devices | grep drm`
  3. Step 3: Search system logs for GPU-related kernel panics using `sudo dmesg | grep -i 'a3xx\|gpu_init\|oops'` or `sudo journalctl -xe | grep -i gpu`
  4. Step 4: After applying the patch, verify the new kernel version with `uname -r` and reboot to confirm the system boots without GPU initialization errors

FAQ

What is CVE-2021-47447?

This vulnerability affects the Adreno A3xx GPU driver in the Linux kernel where error handling functions incorrectly return positive values instead of negative error codes, causing kernel panics when GPU initialization encounters failures.

Is CVE-2021-47447 being actively exploited?

No, there is no evidence of active exploitation in the wild or available public exploits. This is a stability fix rather than a security vulnerability.

What versions of Kernel are affected by CVE-2021-47447?

Linux kernel versions 5.11 through 5.14.13 are vulnerable. Version 5.14.14 and later contain the fix.

How do I check if my server is vulnerable to CVE-2021-47447?

Run `uname -r` to check your kernel version. If the output shows version 5.11.x through 5.14.13, and your system has Adreno A3xx GPU hardware, you are vulnerable.

Does Defensia detect CVE-2021-47447?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2021-47447 will appear in your dashboard with remediation steps.

Related Kernel CVEs

CVE-2026-100075CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: RDMA/srpt: Fix srpt_alloc_rw_ctxs() unwind counters When srpt_alloc_rw_ctxs() fails partway through a multi-buffer indirect descriptor, the unwind path destroys RDMA contexts but leaves stale n_rw_ctx and n_rdma values (and a dangling rw_ctxs pointer). Later sq_wr_avail accounting in srpt_queue_response() or srpt_write_pending() can then subtract the wrong number of send queue credits. Reset the counters and clear rw_ctxs after freeing the heap allocation before returning an error.
CVE-2026-64439CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: crypto: krb5 - filter out async aead implementations at alloc krb5_aead_encrypt(), krb5_aead_decrypt() in rfc3961_simplified.c and rfc8009_encrypt(), rfc8009_decrypt() in rfc8009_aes2.c set a NULL completion callback and treat any negative return from crypto_aead_{encrypt,decrypt}() as terminal, falling through to kfree_sensitive(buffer). When the encrypt_name resolves to an async AEAD instance the request returns -EINPROGRESS, the buffer is freed while the backend's worker still holds a pointer, and the worker dereferences the freed slab on completion. KASAN report under UML+SLUB with a synthetic async aead backend bound to krb5->encrypt_name: BUG: KASAN: slab-use-after-free in t5_stub_complete+0x7d/0xc7 The helpers were written synchronously, so filter the async instances out at allocation time instead of plumbing crypto_wait_req() through every call site. Reachable via net/rxrpc/rxgk.c, fs/afs/cm_security.c and net/ceph/crypto.c on systems with an async AEAD provider bound to the krb5 enctype name.
CVE-2026-64066CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: netfs: Fix netfs_read_to_pagecache() to pause on subreq failure Fix netfs_read_to_pagecache() so that it pauses the generation of new subrequests if an already-issued subrequest fails.
CVE-2026-64383CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: smb: client: fix double-free in SMB2_flush() replay SMB2_flush() keeps its response buffer bookkeeping across replay attempts. If a replayable flush response is received and the retry then fails before cifs_send_recv() stores a replacement response, flush_exit will free the stale response pointer a second time. Reinitialize resp_buftype and rsp_iov at the top of the replay loop so cleanup only acts on response state produced by the current attempt. This fixes a double-free without changing replay handling for successful requests.
CVE-2026-64067CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: netfs: Fix missing barriers when accessing stream->subrequests locklessly The list of subrequests attached to stream->subrequests is accessed without locks by netfs_collect_read_results() and netfs_collect_write_results(), and then they access subreq->flags without taking a barrier after getting the subreq pointer from the list. Relatedly, the functions that build the list don't use any sort of write barrier when constructing the list to make sure that the NETFS_SREQ_IN_PROGRESS flag is perceived to be set first if no lock is taken. Fix this by: (1) Add a new list_add_tail_release() function that uses a release barrier to set the pointer to the new member of the list. (2) Add a new list_first_entry_or_null_acquire() function that uses an acquire barrier to read the pointer to the first member in a list (or return NULL). (3) Use list_add_tail_release() when adding a subreq to ->subrequests. (4) Use list_first_entry_or_null_acquire() when initially accessing the front of the list (when an item is removed, the pointer to the new front iterm is obtained under the same lock).

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2021-47447. Free for 1 server.

Get started free