dbcve.org
5th Gen Gpu Architecture Kernel DriverApplication · Arm

CVE-2023-6363

MEDIUM · 5.1 CVSS v3.1 Published 2024-05-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Use After Free vulnerability in Arm Ltd Valhall GPU Kernel Driver, Arm Ltd Arm 5th Gen GPU Architecture Kernel Driver allows a local non-privileged user to make improper GPU memory processing operations. If the system’s memory is carefully prepared by the user, then this in turn could give them access to already freed memory. This issue affects Valhall GPU Kernel Driver: from r41p0 through r47p0; Arm 5th Gen GPU Architecture Kernel Driver: from r41p0 through r47p0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Use After Free vulnerability in Arm Ltd Valhall and Arm 5th Gen GPU Architecture Kernel Drivers allows a local non-privileged user to make improper GPU memory processing operations, potentially gaining access to already freed memory by carefully preparing the system's memory.

MitigationApply the vendor patch (r48p0 or later) to update the affected GPU kernel drivers. Until patched, limit local unprivileged access to systems with vulnerable drivers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
5th Gen Gpu Architecture Kernel DriverApplication
Affected:>= r41p0, < r48p0
Valhall Gpu Kernel DriverApplication
Affected:>= r41p0, < r48p0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Arm GPU kernel drivers are loaded
    Run 'lsmod | grep -i mali' or check /sys/class/drm/ for Arm GPU device nodes (e.g., /dev/dri/card* with mali vendor). Also check 'lspci | grep -i arm' for GPU hardware.
    Affected if No Arm Mali GPU drivers are loaded or present - the system does not use the affected drivers.
  2. Determine the Arm Valhall GPU driver version
    Use 'modinfo mali_kbase' or check 'cat /sys/module/mali_kbase/version' if the module is loaded. The version string typically contains 'rXXp0' format (e.g., r45p0).
    Affected if The driver version is present and falls within r41p0 <= version < r48p0.
  3. Determine the Arm 5th Gen GPU driver version
    Check the loaded module version via 'modinfo arm_mali' or 'cat /sys/module/arm_mali/version' if present. Look for version string in 'rXXp0' format.
    Affected if The driver version is present and falls within r41p0 <= version < r48p0.
  4. Check kernel message logs for driver version
    Run 'dmesg | grep -i mali' or 'dmesg | grep -i arm.*gpu' to find driver loading messages which often include the driver version at boot time.
    Affected if Log entries show a loaded driver version in the range r41p0 to r47p0 inclusive.

A system is affected if it runs any Arm Valhall or Arm 5th Gen GPU kernel driver with version r41p0 through r47p0 (versions less than r48p0).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch (r48p0 or later) to update the affected GPU kernel drivers. Until patched, limit local unprivileged access to systems with vulnerable drivers.

Recommended fix High confidence

r48p0

  1. Identify the current GPU driver version installed on the system using system utilities or driver management tools
  2. Obtain the updated Arm GPU kernel driver version r48p0 or later from Arm's official driver distribution (refer to developer.arm.com or your system/hardware vendor)
  3. Follow your distribution or system vendor's standard procedure to update the GPU kernel driver package
  4. Reboot the system to load the new kernel driver
  5. Verify the installed driver version is r48p0 or later to confirm the update was successful

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in 5th Gen Gpu Architecture Kernel Driver Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-6363 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-6363 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data