LiveActive security incident?Get immediate response
CVE Record

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

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).

MediumCVSS 4.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects ARM64 systems using Cortex-A520 cores. A processor erratum can let speculative execution expose small amounts of privileged data through cache behavior. It is not listed as actively exploited, but it matters for devices where sensitive workloads run on affected hardware.

Executive priority

Treat this as a targeted medium-priority kernel remediation item. It is hardware-specific and not reported as actively exploited, but affected ARM64 systems handling sensitive data should be patched through normal kernel maintenance windows.

Technical view

CVE-2023-52481 addresses ARM Cortex-A520 erratum 2966298 in the Linux kernel. A speculatively executed unprivileged load may leak data from a privileged load via a cache side channel within the same translation regime. The kernel fix adds a TLBI workaround before returning to EL0.

Likely exposure

Exposure is most likely on Linux ARM64 systems with Cortex-A520 cores running affected kernel builds. The provided version metadata is limited and somewhat ambiguous, so kernel source, distro advisories, and hardware inventory should drive final scope.

Exploitation context

The source bundle does not show KEV listing or active exploitation. The CVSS vector indicates high privileges are required. Practical risk depends on affected CPU presence, kernel version, workload sensitivity, and whether patched vendor kernels are deployed.

Researcher notes

The issue is constrained to loads within the same translation regime, such as the same ASID and VMID, and affects return to EL0. The described workaround executes a non-shareable TLBI before returning to EL0 after privileged-data loads.

Mitigation direction

  • Identify Linux ARM64 systems using Cortex-A520 cores.
  • Apply vendor or distro kernels containing the referenced stable fixes.
  • Prioritize shared, multi-tenant, or sensitive ARM64 workloads.
  • Check vendor guidance if no fixed kernel is available.
  • Avoid manual erratum backports unless kernel engineering validates them.

Validation and detection

  • Confirm whether hardware uses ARM Cortex-A520 cores.
  • Verify running kernels include the referenced stable commits.
  • Check distro advisories for CVE-2023-52481 status.
  • Confirm patched systems rebooted into the fixed kernel.
  • Document any affected systems awaiting vendor fixes.
Prepared
Confidence
medium
Sources
5

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-2023-52481 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
Medium
CVSS
4.7 (3.1)
Known Exploited
No
Published

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

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.7CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L1.23.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.7Medium
CVSS 3.1 vector shape for CVE-2023-52481Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0be7320a635c2e434e8b67e0e9474a85ceb421c4, 0be7320a635c2e434e8b67e0e9474a85ceb421c4, 0be7320a635c2e434e8b67e0e9474a85ceb421c4unaffected
LinuxLinux3.7, 0, 6.1.57, 6.5.7, 6.6affected
Weakness

CWE details

No CWE listed

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