Answer in brief
CVE-2026-64466 records a Unknown severity vulnerability in rust_binder: clear freeze listener on node removal. 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 | >=eafedbc7c050c44744fbdf80bdf3315e860b7513 <91b27f8172cdbf265240104772fd042a461a7767 || >=eafedbc7c050c44744fbdf80bdf3315e860b7513 <0644da3621ddd8e146280675a2a31d1e06634a1d || >=eafedbc7c050c44744fbdf80bdf3315e860b7513 <bc4a9828897871ff3e5a1f8a1d346decbf4ee95e | 91b27f8172cdbf265240104772fd042a461a7767, 0644da3621ddd8e146280675a2a31d1e06634a1d, bc4a9828897871ff3e5a1f8a1d346decbf4ee95e |
| Linux/Linuxgeneric | 6.18 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 17, 2026
In the Linux kernel, the following vulnerability has been resolved: rust_binder: clear freeze listener on node removal Generally userspace is supposed to explicitly clear freeze listeners before they drop the refcount on the node ref to zero, but there's nothing forcing that. Currently, in this scenario the freeze listener remains in the freeze_listeners rbtree and in the remote node's freeze listener list, even though the ref for which the listener is registered is gone. This could potentially lead to a memory leak due to a refcount cycle. Thus, remove the freeze listener in this scenario.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-64466 records a Unknown severity vulnerability in rust_binder: clear freeze listener on node removal. 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 | >=eafedbc7c050c44744fbdf80bdf3315e860b7513 <91b27f8172cdbf265240104772fd042a461a7767 || >=eafedbc7c050c44744fbdf80bdf3315e860b7513 <0644da3621ddd8e146280675a2a31d1e06634a1d || >=eafedbc7c050c44744fbdf80bdf3315e860b7513 <bc4a9828897871ff3e5a1f8a1d346decbf4ee95e | 91b27f8172cdbf265240104772fd042a461a7767, 0644da3621ddd8e146280675a2a31d1e06634a1d, bc4a9828897871ff3e5a1f8a1d346decbf4ee95e |
| Linux/Linuxgeneric | 6.18 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 17, 2026
In the Linux kernel, the following vulnerability has been resolved: rust_binder: clear freeze listener on node removal Generally userspace is supposed to explicitly clear freeze listeners before they drop the refcount on the node ref to zero, but there's nothing forcing that. Currently, in this scenario the freeze listener remains in the freeze_listeners rbtree and in the remote node's freeze listener list, even though the ref for which the listener is registered is gone. This could potentially lead to a memory leak due to a refcount cycle. Thus, remove the freeze listener in this scenario.
Quoted source text, attributed separately from HOL analysis.