LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47050: memory: renesas-rpc-if: fix possible NULL pointer dereference of resource

In the Linux kernel, the following vulnerability has been resolved: memory: renesas-rpc-if: fix possible NULL pointer dereference of resource The platform_get_resource_byname() can return NULL which would be immediately dereferenced by resource_size(). Instead dereference it after validating the resource. Addresses-Coverity: Dereference null return value

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel driver reliability flaw in the Renesas RPC-IF memory interface. A missing resource check could cause a NULL pointer dereference and crash affected systems during driver/resource handling. The public record does not provide CVSS, exploitation evidence, or broad product mapping, so urgency depends on whether your Linux fleet uses this driver or vendor kernels containing the vulnerable code.

Executive priority

Treat this as targeted kernel hygiene unless your organization runs Renesas-based embedded systems. There is no cited active exploitation or severity score, but kernel crashes on operational devices can still create business disruption. Fold remediation into the next kernel or firmware maintenance cycle after confirming exposure.

Technical view

The issue is in memory: renesas-rpc-if. platform_get_resource_byname() can return NULL, and vulnerable code dereferenced it through resource_size() before validation. The stable kernel references indicate the fix validates the resource before dereference. The source bundle lists affected Linux versions including 5.9, 5.10.37, 5.11.21, 5.12.4, and 5.13, but detailed downstream vendor impact is not provided.

Likely exposure

Most exposure appears limited to systems using Linux kernels with the Renesas RPC-IF driver path, commonly relevant to Renesas SoC or embedded deployments. General-purpose servers without this driver or hardware path may have low practical exposure, but vendor kernels should be checked because downstream backports can differ from upstream version labels.

Exploitation context

The bundle does not cite active exploitation, public exploit availability, or CISA KEV listing. The described impact is a possible kernel NULL pointer dereference, which usually points to availability risk rather than data theft. No source in the bundle proves remote reachability or privilege escalation.

Researcher notes

Evidence is concise: a Coverity-found NULL dereference fixed in Linux stable commits. The public bundle lacks CVSS, CWE, exploit preconditions, and downstream vendor matrices. Avoid broad claims beyond affected Linux kernel code and validate against exact source trees because stable backports may not match simple version comparisons.

Mitigation direction

  • Check your Linux vendor advisory for CVE-2021-47050 coverage.
  • Update to a kernel containing the referenced stable fix.
  • For embedded fleets, verify vendor BSPs include the backport.
  • Prioritize internet-facing or safety-critical devices only if they use this driver.

Validation and detection

  • Inventory kernel versions and downstream vendor kernel branches.
  • Check whether the Renesas RPC-IF driver is built or loaded.
  • Compare kernel source against the referenced stable commits.
  • Review device-tree/resource definitions for Renesas RPC-IF deployments.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2021-47050 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxca7d8b980b67f133317525c4273e144116ee1ae5, ca7d8b980b67f133317525c4273e144116ee1ae5, ca7d8b980b67f133317525c4273e144116ee1ae5, ca7d8b980b67f133317525c4273e144116ee1ae5unaffected
LinuxLinux5.9, 0, 5.10.37, 5.11.21, 5.12.4, 5.13affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.