LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53266: arm64: acpi: Fix possible memory leak of ffh_ctxt

In the Linux kernel, the following vulnerability has been resolved: arm64: acpi: Fix possible memory leak of ffh_ctxt Allocated 'ffh_ctxt' memory leak is possible if the SMCCC version and conduit checks fail and -EOPNOTSUPP is returned without freeing the allocated memory. Fix the same by moving the allocation after the SMCCC version and conduit checks.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-53266 is a Linux kernel memory leak in ARM64 ACPI handling. Under specific failed platform checks, allocated memory may not be freed. The main business risk is local availability impact, not data theft or privilege escalation based on the supplied sources.

Executive priority

Handle through normal kernel patch management, with higher priority for ARM64 production systems where downtime has operational impact. There is no supplied evidence of active exploitation or confidentiality impact.

Technical view

In ARM64 ACPI code, ffh_ctxt could be allocated before SMCCC version and conduit checks. If those checks failed and returned -EOPNOTSUPP, the allocation was not freed. The kernel fix moves allocation after those checks. The issue is classified as CWE-401 with CVSS 5.5.

Likely exposure

Exposure appears limited to ARM64 Linux systems running affected kernel versions in the supplied range, especially environments using ACPI-related firmware paths. The source bundle does not identify affected distributions, cloud images, appliances, or default configurations.

Exploitation context

The CVSS vector indicates local access with low privileges and no user interaction. The supplied sources do not report public exploitation, weaponized exploit availability, or CISA KEV listing. Treat it as a local denial-of-service risk unless vendor advisories say otherwise.

Researcher notes

The evidence is concise and kernel-focused. Version data in the bundle is limited, so avoid broad product claims. Research should map downstream distribution kernels to the upstream stable commits and confirm whether the relevant ARM64 ACPI path exists.

Mitigation direction

  • Update affected Linux kernels through the operating system or appliance vendor.
  • Confirm vendor updates include the referenced upstream stable commits.
  • Prioritize ARM64 systems where availability matters, including production edge and infrastructure hosts.
  • Monitor vendor advisories for distribution-specific package names and fixed versions.

Validation and detection

  • Inventory ARM64 Linux hosts and record exact kernel versions.
  • Check vendor changelogs for CVE-2023-53266 or the referenced commit hashes.
  • Validate scanner findings against the actual running kernel, not only installed packages.
  • Review availability monitoring for unexplained memory pressure on affected systems.
Prepared
Confidence
high
Sources
4

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.

cwe · low confidence lookup

CWE-401: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-53266 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
5.5 (3.1)
Known Exploited
No
Published

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

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
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1d280ce099db396e092cac1aa9bf2ea8beee6d76, 1d280ce099db396e092cac1aa9bf2ea8beee6d76unaffected
LinuxLinux6.2, 0, 6.2.3, 6.3affected
Weakness

CWE details

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

CWE-401 · source CWE mapping

Missing Release of Memory after Effective Lifetime

Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.