Answer in brief
CVE-2026-64081 records a Unknown severity vulnerability in firmware: arm_ffa: Validate framework notification message layout. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=285a5ea0f542db94c3ed11e01a71abb47d15cbf5 <3c51d99449dc5a01c08a7fce6071d6721f5aac83 || >=285a5ea0f542db94c3ed11e01a71abb47d15cbf5 <76eb90e2b03de147e12ab68ea8afd8ea0342df0a || >=285a5ea0f542db94c3ed11e01a71abb47d15cbf5 <4a1cc9e96b311d2609a6f963a5e35bd4ae730d97 | 3c51d99449dc5a01c08a7fce6071d6721f5aac83, 76eb90e2b03de147e12ab68ea8afd8ea0342df0a, 4a1cc9e96b311d2609a6f963a5e35bd4ae730d97 |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64081 records a Unknown severity vulnerability in firmware: arm_ffa: Validate framework notification message layout. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=285a5ea0f542db94c3ed11e01a71abb47d15cbf5 <3c51d99449dc5a01c08a7fce6071d6721f5aac83 || >=285a5ea0f542db94c3ed11e01a71abb47d15cbf5 <76eb90e2b03de147e12ab68ea8afd8ea0342df0a || >=285a5ea0f542db94c3ed11e01a71abb47d15cbf5 <4a1cc9e96b311d2609a6f963a5e35bd4ae730d97 | 3c51d99449dc5a01c08a7fce6071d6721f5aac83, 76eb90e2b03de147e12ab68ea8afd8ea0342df0a, 4a1cc9e96b311d2609a6f963a5e35bd4ae730d97 |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Jul 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.