LiveActive security incident?Get immediate response
CVE Record

CVE-2026-64081: firmware: arm_ffa: Validate framework notification message layout

In the Linux kernel, the following vulnerability has been resolved: firmware: arm_ffa: Validate framework notification message layout Framework notifications carry an indirect message in the shared RX buffer. Validate the reported offset and size before using them, reject zero-length payloads, and ensure that any non-header payload starts at the UUID field rather than in the middle of the message header. Use the validated offset and size values for both kmemdup() and the UUID parsing path so malformed firmware data cannot drive an out-of-bounds read or an oversized allocation.

HighCVSS 8.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects ARM FF-A firmware notification handling. Malformed firmware-provided notification metadata can cause the kernel to read outside expected memory bounds or attempt an oversized allocation. The rated impact is high, but the bundle does not show active exploitation.

Executive priority

Treat as high priority for ARM Linux fleets, especially appliances, cloud infrastructure, and embedded platforms. Patch through vendor-supported kernel updates once available; do not assume exposure on non-ARM systems without FF-A.

Technical view

The ARM FF-A firmware driver failed to validate indirect framework notification offset and size fields in the shared RX buffer. The fix rejects zero-length payloads, validates bounds, and requires non-header payloads to begin at the UUID field before kmemdup() and UUID parsing.

Likely exposure

Likely exposure is limited to Linux systems using affected kernel versions on ARM platforms where the ARM FF-A firmware interface and framework notifications are present. Exact affected version ranges in the bundle are incomplete or ambiguous, so kernel vendor advisories should be checked.

Exploitation context

No KEV listing is indicated and no provided source claims active exploitation. The CVSS vector is local, low complexity, no privileges, no user interaction, with high confidentiality, integrity, and availability impact.

Researcher notes

The issue is a bounds-validation flaw in firmware-supplied notification layout metadata. The bundle supports out-of-bounds read and oversized allocation risk, but does not provide proof of exploitation, concrete attack paths, or complete downstream version mapping.

Mitigation direction

  • Apply Linux kernel stable updates containing the referenced fixes.
  • Prioritize ARM systems using FF-A firmware interfaces.
  • Check distribution or device-vendor advisories for backported fixes.
  • If patching is delayed, ask vendors for supported mitigations.
  • Track fleet kernel versions against vendor fixed builds.

Validation and detection

  • Inventory ARM Linux systems and running kernel versions.
  • Confirm whether ARM FF-A firmware support is enabled or loaded.
  • Compare installed kernels with vendor advisories and stable commits.
  • Verify patched code validates notification offset and size fields.
  • Monitor kernel logs for abnormal FF-A firmware notification errors.
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-2026-64081 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
High
CVSS
8.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/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
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
8.4CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.55.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

8.4High
CVSS 3.1 vector shape for CVE-2026-64081Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux285a5ea0f542db94c3ed11e01a71abb47d15cbf5, 285a5ea0f542db94c3ed11e01a71abb47d15cbf5, 285a5ea0f542db94c3ed11e01a71abb47d15cbf5unaffected
LinuxLinux6.15, 0, 6.18.34, 7.0.11, 7.1affected
Weakness

CWE details

No CWE listed

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