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

Published Jul 19, 2026
·
Updated

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

firmware: armffa: 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.

Affected Software

7 affected components
Linux Linux kernel
Linux Linux kernel>=6.15<6.18.34
Linux Linux kernel>=6.19<7.0.11
Linux Linux kernel=7.1-rc1
Linux Linux kernel=7.1-rc2
Linux Linux kernel=7.1-rc3
Linux Linux kernel=7.1-rc4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    In the firmware notification parsing path, validate the reported offset and size before using them for both kmemdup() and the UUID, ensuring malformed firmware data cannot cause out-of-bounds reads or oversized allocations; parse the UUID using the validated layout rather than reading it from the middle of the message header.

    Linux kernel (firmware: arm_ffa framework notification parsing) Use validated offset and size for kmemdup() and UUID; validate reported offset/size before use; reject malformed firmware data = enforce_validation

Event History

Jul 19, 2026
CVE Published
via MITRE·03:39 PM
Data Sourced
via MITRE·03:39 PM
DescriptionSeverity
Data Sourced
via NVD·04:17 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What conditions are required to trigger this issue?

The issue is triggered when the kernel processes a malformed framework notification whose indirect message in the shared RX buffer reports an invalid offset or size. The vulnerable processing could use that firmware-provided data for an out-of-bounds read or an oversized allocation.

2

Is local access or authentication required to exploit it?

The supplied CVSS vector rates the attack vector as local and lists no privileges or user interaction requirements. The available data does not specify how an attacker would cause malicious firmware notification data to be delivered.

3

What should be checked to determine whether a system is exposed?

Identify systems running the Linux kernel that use Arm FF-A firmware notifications with indirect messages in the shared RX buffer. Then verify whether the installed kernel includes one of the referenced stable fixes; no affected or fixed version numbers are provided.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203