CVE-2022-46396
CVE-2022-46396 is a low-severity vulnerability in Arm Avalon Gpu Kernel Driver with a CVSS 3.x base score of 3.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-119.
Key facts
- Severity: Low (CVSS 3.x base score 3.3)
- EPSS exploit prediction: 0% (13th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-119
- Affected product: Arm Avalon Gpu Kernel Driver
- Published:
- Last modified:
Description
An issue was discovered in the Arm Mali Kernel Driver. A non-privileged user can make improper GPU memory processing operations to access a limited amount outside of buffer bounds. This affects Valhall r29p0 through r41p0 before r42p0 and Avalon r41p0 before r42p0.
Frequently asked questions
- What is CVE-2022-46396?
- An issue was discovered in the Arm Mali Kernel Driver. A non-privileged user can make improper GPU memory processing operations to access a limited amount outside of buffer bounds. This affects Valhall r29p0 through r41p0 before r42p0 and Avalon r41p0 before r42p0.
- How severe is CVE-2022-46396?
- CVE-2022-46396 has a CVSS 3.x base score of 3.3, rated low severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
- Is CVE-2022-46396 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (13th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2022-46396?
- CVE-2022-46396 primarily affects Arm Avalon Gpu Kernel Driver. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
- How do I fix CVE-2022-46396?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2022-46396 published?
- CVE-2022-46396 was published on 2023-04-11 and last updated on 2026-06-17.
References
Affected products (2)
- cpe:2.3:a:arm:avalon_gpu_kernel_driver:r41p0:*:*:*:*:*:*:*
- cpe:2.3:a:arm:valhall_gpu_kernel_driver:*:*:*:*:*:*:*:*
More vulnerabilities in Arm Avalon Gpu Kernel Driver
- CVE-2022-46394 — High (CVSS 8.8): An issue was discovered in the Arm Mali GPU Kernel Driver. A non-privileged user can make improper GPU processing…
- CVE-2022-46395 — High (CVSS 8.8): An issue was discovered in the Arm Mali GPU Kernel Driver. A non-privileged user can make improper GPU processing…
- CVE-2023-28469 — Medium (CVSS 5.5): An issue was discovered in the Arm Mali GPU Kernel Driver. A non-privileged user can make improper GPU processing…
- CVE-2023-28147 — Medium (CVSS 5.5): An issue was discovered in the Arm Mali GPU Kernel Driver. A non-privileged user can make improper GPU processing…
- CVE-2022-46781 — Low (CVSS 3.3): An issue was discovered in the Arm Mali GPU Kernel Driver. A non-privileged user can make improper GPU memory…
All CVEs affecting Arm Avalon Gpu Kernel Driver →
Other CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) vulnerabilities
- CVE-2026-77946 — Critical (CVSS 10.0): A vulnerability was determined in TRENDnet TEW-821DAP 2.2.01b05. Affected by this vulnerability is the function…
- CVE-2026-76008 — Critical (CVSS 10.0): A flaw has been found in Comfast CF-N1-S 2.6.0.1. This affects the function get_para_from_uri of the file…
- CVE-2026-75784 — Critical (CVSS 10.0): A vulnerability was detected in TRENDnet TEW-WLC100 1v2.07b01. Affected by this issue is the function FUN_0040da4c of…
- CVE-2026-74843 — Critical (CVSS 10.0): A vulnerability was determined in Wavlink WN531P3 and WN535M1 V250922. Affected by this vulnerability is the function…
- CVE-2026-16367 — Critical (CVSS 10.0): Sandbox escape due to invalid pointer in the Disability Access APIs component. This vulnerability was fixed in Firefox…
- CVE-2026-2778 — Critical (CVSS 10.0): Sandbox escape due to incorrect boundary conditions in the DOM: Core & HTML component. This vulnerability was fixed in…