Answer in brief
CVE-2026-74435 records a Unknown severity vulnerability in rxrpc: rxrpc_verify_data ensure rx_dec_buffer alloc. 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 | >=a05bf6d9e621fa71e89ccebe3047ba45218d7b38 <8bbede0afced346b24e4fbde0c68cf12980ba948 || >=b94a6ccbaf1104dd980150a65fdeb2f69d17d2f5 <6563b4eb38c35d75892445bcf8aacdc29914821c || >=46cb765e2e5ad52303ea157e10d370bb6b7acbbf <d3b642cf95d48234590cc91450d8705a9bf6b540 || >=d2bc90cf6c75cb96d2ce549be6c35efa3099d25b <a962bc8508592c4d51092edac68579bd8b18fe44 || >=d2bc90cf6c75cb96d2ce549be6c35efa3099d25b <16c8ae9735c5bd7e54dd7478d6348e0fc860842d || c580087743712112778a06d65a4074053072d7bf || >=6.6.143 <6.6.145 || >=6.12.93 <6.12.97 || >=6.18.35 <6.18.40 || >=7.0.11 <7.1 | 8bbede0afced346b24e4fbde0c68cf12980ba948, 6563b4eb38c35d75892445bcf8aacdc29914821c, d3b642cf95d48234590cc91450d8705a9bf6b540, a962bc8508592c4d51092edac68579bd8b18fe44, 16c8ae9735c5bd7e54dd7478d6348e0fc860842d, 6.6.145, 6.12.97, 6.18.40, 7.1 |
| Linux/Linuxgeneric | 7.1 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: rxrpc: rxrpc_verify_data ensure rx_dec_buffer alloc rxrpc_recvmsg_data() calls rxrpc_verify_data() whenever the rxrpc_call.rx_dec_buffer is unallocated and assumes that upon successful return that rx_dec_buffer must be allocated. However, rxrpc_verify_data() does not request an allocation if the rxrpc_skb_priv.len is zero. In addition, failure to allocate rx_dec_buffer will result in a call to skb_copy_bits() with a NULL destination which can trigger a NULL pointer dereference. To prevent these issues rxrpc_verify_data() is modified to always attempt to allocate the rxrpc_call.rx_dec_buffer if it is NULL. This issue was identified with assistance of a private sashiko instance.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-74435 records a Unknown severity vulnerability in rxrpc: rxrpc_verify_data ensure rx_dec_buffer alloc. 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 | >=a05bf6d9e621fa71e89ccebe3047ba45218d7b38 <8bbede0afced346b24e4fbde0c68cf12980ba948 || >=b94a6ccbaf1104dd980150a65fdeb2f69d17d2f5 <6563b4eb38c35d75892445bcf8aacdc29914821c || >=46cb765e2e5ad52303ea157e10d370bb6b7acbbf <d3b642cf95d48234590cc91450d8705a9bf6b540 || >=d2bc90cf6c75cb96d2ce549be6c35efa3099d25b <a962bc8508592c4d51092edac68579bd8b18fe44 || >=d2bc90cf6c75cb96d2ce549be6c35efa3099d25b <16c8ae9735c5bd7e54dd7478d6348e0fc860842d || c580087743712112778a06d65a4074053072d7bf || >=6.6.143 <6.6.145 || >=6.12.93 <6.12.97 || >=6.18.35 <6.18.40 || >=7.0.11 <7.1 | 8bbede0afced346b24e4fbde0c68cf12980ba948, 6563b4eb38c35d75892445bcf8aacdc29914821c, d3b642cf95d48234590cc91450d8705a9bf6b540, a962bc8508592c4d51092edac68579bd8b18fe44, 16c8ae9735c5bd7e54dd7478d6348e0fc860842d, 6.6.145, 6.12.97, 6.18.40, 7.1 |
| Linux/Linuxgeneric | 7.1 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: rxrpc: rxrpc_verify_data ensure rx_dec_buffer alloc rxrpc_recvmsg_data() calls rxrpc_verify_data() whenever the rxrpc_call.rx_dec_buffer is unallocated and assumes that upon successful return that rx_dec_buffer must be allocated. However, rxrpc_verify_data() does not request an allocation if the rxrpc_skb_priv.len is zero. In addition, failure to allocate rx_dec_buffer will result in a call to skb_copy_bits() with a NULL destination which can trigger a NULL pointer dereference. To prevent these issues rxrpc_verify_data() is modified to always attempt to allocate the rxrpc_call.rx_dec_buffer if it is NULL. This issue was identified with assistance of a private sashiko instance.
Quoted source text, attributed separately from HOL analysis.