CVE EVIDENCE REVIEW
ReviewHighEvidence review

CVE-2026-74435 evidence review

Linux

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...

Open CVE record
Evidence review

This record remains available for product and version identification, but it is not presented as a complete remediation procedure. Confirm the affected range and the supported fix in a direct vendor advisory before changing production systems.

ProductLinux
Affected versions>= 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, >= 7.1
Fixed versionsNo verified fixed-version field is available yet
Priority basisReview · CVSS 7.5 · EPSS -
01

Identify the product and installed version

Record whether Linux is present, where it is installed, and which interfaces are exposed.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Compare the affected range

Use the current record as an identification aid: >= 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, >= 7.1. Resolve incomplete inventory results before deciding that an asset is unaffected.

03

Verify the authoritative remediation source

Open the linked source material and locate a direct vendor advisory for this CVE. Confirm the supported fixed release and product-specific update path before making a production change.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.