Arm 5Th Gen Gpu Architecture Kernel Driver
Monthly
Race condition exploitation in Arm's Bifrost, Valhall, and 5th Gen GPU Architecture Kernel Drivers allows any local non-privileged process to perform improper GPU memory operations, yielding kernel-level sensitive information disclosure or denial of service. All three driver families are affected across broad version ranges spanning multiple major release trains - Bifrost from r12p0, Valhall from r19p0, and 5th Gen from r41p0 - covering a large installed base of Mali GPU-equipped devices. No public exploit or active exploitation has been confirmed at time of analysis; the low EPSS score (0.11%, percentile 1%) reflects limited observed exploitation interest.
Use-after-free in Arm's Bifrost, Valhall, and 5th Gen GPU Architecture Kernel Drivers enables a local unprivileged process to access deallocated kernel memory through valid GPU memory processing operations, resulting in full confidentiality, integrity, and availability compromise (CVSS C:H/I:H/A:H). The flaw spans broad version ranges across all three driver families from r44p0 through r54p3/r55p0, affecting a large population of devices built on Arm Mali GPU hardware. No active exploitation is confirmed at time of analysis (EPSS 0.14%, no CISA KEV listing), but UAF vulnerabilities in kernel-mode GPU drivers are a well-established and historically weaponized local privilege escalation vector on Android and Linux platforms.
Use-after-free in Arm's Bifrost, Valhall, and 5th Gen GPU Architecture kernel drivers allows a local non-privileged process to access freed GPU memory, yielding full confidentiality, integrity, and availability impact within the kernel driver context. Affected revisions span a wide range across all three driver families - from r49p3 through r55p0 depending on the product line - placing a large population of Android and embedded Arm devices in scope. No public exploit code exists at time of analysis, and EPSS sits at 0.14% (4th percentile), though the low-complexity local attack surface characteristic of GPU driver UAFs has historically attracted sophisticated actors targeting mobile platforms.
Use-after-free in Arm's Valhall and 5th Gen GPU Architecture kernel drivers allows a local non-privileged process to access freed kernel memory by submitting valid GPU processing operations, with potential for full system compromise across confidentiality, integrity, and availability (CVSS C:H/I:H/A:H). Both driver families are affected from r50p0 through r54p3 and at r55p0, covering a wide swath of devices - notably Android smartphones and embedded SoCs - that rely on these GPU drivers. No active exploitation is confirmed (EPSS 0.14%, 4th percentile; no CISA KEV listing) at time of analysis.
Sensitive kernel memory is exposed to local non-privileged user processes through improper GPU memory processing operations in Arm's Valhall GPU Kernel Driver and 5th Gen GPU Architecture Kernel Driver. The flaw spans a wide driver revision range - Valhall from r29p0 through r55p0 and 5th Gen from r41p0 through r55p0 - covering Mali-G series and Immortalis GPU generations deployed across hundreds of millions of Android and embedded devices. No public exploit code has been identified and EPSS sits at 0.14% (4th percentile), but the kernel-level confidentiality impact and the OEM-dependent patch delivery path make timely remediation structurally difficult.
Use-after-free in Arm's Bifrost, Valhall, and 5th Gen GPU Architecture Kernel Drivers allows a local non-privileged process to access already-freed GPU memory through otherwise-valid GPU memory processing operations. The flaw spans a wide range of driver releases across all three GPU families - covering most modern Arm Mali GPU generations deployed in Android SoCs from r41p0 onward. No public exploit code or active exploitation has been identified; EPSS sits at 0.14% (4th percentile), and the vulnerability is not listed in the CISA KEV catalog.
Use-after-free in Arm's Bifrost, Valhall, and 5th Gen GPU Architecture kernel drivers allows an unprivileged local process to access already freed kernel memory, leaking limited sensitive data. The flaw is triggered through valid GPU memory processing operations, requiring no special privileges beyond local code execution - a realistic threat on mobile devices running affected Mali GPU firmware. With EPSS at 0.14% and no public exploit or KEV listing, active exploitation is not currently observed, but the breadth of affected versions across three GPU families and many Android SoC generations elevates overall exposure.
Use-after-free in Arm's Bifrost, Valhall, and 5th Gen GPU kernel drivers allows a local unprivileged process to access already-freed GPU memory through valid GPU memory processing operations, resulting in limited confidentiality and integrity impact against the kernel driver. The flaw spans a wide range of driver versions across all three GPU architectures, affecting the enormous ecosystem of Android and embedded devices powered by Arm Mali GPUs. No public exploit or active exploitation has been identified; SSVC rates technical impact as partial and exploitation as none at time of analysis.
Race condition exploitation in Arm's Bifrost, Valhall, and 5th Gen GPU Architecture Kernel Drivers allows any local non-privileged process to perform improper GPU memory operations, yielding kernel-level sensitive information disclosure or denial of service. All three driver families are affected across broad version ranges spanning multiple major release trains - Bifrost from r12p0, Valhall from r19p0, and 5th Gen from r41p0 - covering a large installed base of Mali GPU-equipped devices. No public exploit or active exploitation has been confirmed at time of analysis; the low EPSS score (0.11%, percentile 1%) reflects limited observed exploitation interest.
Use-after-free in Arm's Bifrost, Valhall, and 5th Gen GPU Architecture Kernel Drivers enables a local unprivileged process to access deallocated kernel memory through valid GPU memory processing operations, resulting in full confidentiality, integrity, and availability compromise (CVSS C:H/I:H/A:H). The flaw spans broad version ranges across all three driver families from r44p0 through r54p3/r55p0, affecting a large population of devices built on Arm Mali GPU hardware. No active exploitation is confirmed at time of analysis (EPSS 0.14%, no CISA KEV listing), but UAF vulnerabilities in kernel-mode GPU drivers are a well-established and historically weaponized local privilege escalation vector on Android and Linux platforms.
Use-after-free in Arm's Bifrost, Valhall, and 5th Gen GPU Architecture kernel drivers allows a local non-privileged process to access freed GPU memory, yielding full confidentiality, integrity, and availability impact within the kernel driver context. Affected revisions span a wide range across all three driver families - from r49p3 through r55p0 depending on the product line - placing a large population of Android and embedded Arm devices in scope. No public exploit code exists at time of analysis, and EPSS sits at 0.14% (4th percentile), though the low-complexity local attack surface characteristic of GPU driver UAFs has historically attracted sophisticated actors targeting mobile platforms.
Use-after-free in Arm's Valhall and 5th Gen GPU Architecture kernel drivers allows a local non-privileged process to access freed kernel memory by submitting valid GPU processing operations, with potential for full system compromise across confidentiality, integrity, and availability (CVSS C:H/I:H/A:H). Both driver families are affected from r50p0 through r54p3 and at r55p0, covering a wide swath of devices - notably Android smartphones and embedded SoCs - that rely on these GPU drivers. No active exploitation is confirmed (EPSS 0.14%, 4th percentile; no CISA KEV listing) at time of analysis.
Sensitive kernel memory is exposed to local non-privileged user processes through improper GPU memory processing operations in Arm's Valhall GPU Kernel Driver and 5th Gen GPU Architecture Kernel Driver. The flaw spans a wide driver revision range - Valhall from r29p0 through r55p0 and 5th Gen from r41p0 through r55p0 - covering Mali-G series and Immortalis GPU generations deployed across hundreds of millions of Android and embedded devices. No public exploit code has been identified and EPSS sits at 0.14% (4th percentile), but the kernel-level confidentiality impact and the OEM-dependent patch delivery path make timely remediation structurally difficult.
Use-after-free in Arm's Bifrost, Valhall, and 5th Gen GPU Architecture Kernel Drivers allows a local non-privileged process to access already-freed GPU memory through otherwise-valid GPU memory processing operations. The flaw spans a wide range of driver releases across all three GPU families - covering most modern Arm Mali GPU generations deployed in Android SoCs from r41p0 onward. No public exploit code or active exploitation has been identified; EPSS sits at 0.14% (4th percentile), and the vulnerability is not listed in the CISA KEV catalog.
Use-after-free in Arm's Bifrost, Valhall, and 5th Gen GPU Architecture kernel drivers allows an unprivileged local process to access already freed kernel memory, leaking limited sensitive data. The flaw is triggered through valid GPU memory processing operations, requiring no special privileges beyond local code execution - a realistic threat on mobile devices running affected Mali GPU firmware. With EPSS at 0.14% and no public exploit or KEV listing, active exploitation is not currently observed, but the breadth of affected versions across three GPU families and many Android SoC generations elevates overall exposure.
Use-after-free in Arm's Bifrost, Valhall, and 5th Gen GPU kernel drivers allows a local unprivileged process to access already-freed GPU memory through valid GPU memory processing operations, resulting in limited confidentiality and integrity impact against the kernel driver. The flaw spans a wide range of driver versions across all three GPU architectures, affecting the enormous ecosystem of Android and embedded devices powered by Arm Mali GPUs. No public exploit or active exploitation has been identified; SSVC rates technical impact as partial and exploitation as none at time of analysis.