# CVE-2023-52481: arm64: errata: Add Cortex-A520 speculative unprivileged load workaround

> A speculative execution flaw in the Linux kernel on Cortex-A520 allows attackers to leak privileged data via cache side channels.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Feb 2024
- **Updated:** 15 Aug 2026
- **Also known as:** AZL-59471, BELL-CVE-2023-52481, DEBIAN-CVE-2023-52481, GHSA-3qpr-v3fc-q5q5, ROOT-OS-DEBIAN-11-CVE-2023-52481, ROOT-OS-UBUNTU-2204-CVE-2023-52481, UBUNTU-CVE-2023-52481

## What is CVE-2023-52481?

CVE-2023-52481 is a medium-severity vulnerability in Linux kernel, published on 29 Feb 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

arm64: errata: Add Cortex-A520 speculative unprivileged load workaround

Implement the workaround for ARM Cortex-A520 erratum 2966298. On an
affected Cortex-A520 core, a speculatively executed unprivileged load
might leak data from a privileged load via a cache side channel. The
issue only exists for loads within a translation regime with the same
translation (e.g. same ASID and VMID). Therefore, the issue only affects
the return to EL0.

The workaround is to execute a TLBI before returning to EL0 after all
loads of privileged data. A non-shareable TLBI to any address is
sufficient.

The workaround isn't necessary if page table isolation (KPTI) is
enabled, but for simplicity it will be. Page table isolation should
normally be disabled for Cortex-A520 as it supports the CSV3 feature
and the E0PD feature (used when KASLR is enabled).

## Which versions are affected by CVE-2023-52481?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2023-52481?

Apply the vendor's patch.

## Is CVE-2023-52481 being exploited?

There is no known exploitation of CVE-2023-52481 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-52481 and fix it if it is affected.

What it is: CVE-2023-52481 is a medium-severity vulnerability in Linux kernel, published on 29 Feb 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-52481 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-52481/ (Markdown: https://insights.sbomify.com/CVE-2023-52481/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-52481
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-52481
- OSV: https://osv.dev/vulnerability/CVE-2023-52481

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-52481/
Summaries are generated and may contain mistakes; the official description above is the record.