Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-74435rxrpc: rxrpc_verify_data ensure rx_dec_buffer alloc

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-74435, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Received3.1High7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.63% · top 49% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.5.

Affected products

  • Linux · Linux

    • affected a05bf6d9e621fa71e89ccebe3047ba45218d7b38 – < 8bbede0afced346b24e4fbde0c68cf12980ba948
    • affected b94a6ccbaf1104dd980150a65fdeb2f69d17d2f5 – < 6563b4eb38c35d75892445bcf8aacdc29914821c
    • affected 46cb765e2e5ad52303ea157e10d370bb6b7acbbf – < d3b642cf95d48234590cc91450d8705a9bf6b540
    • affected d2bc90cf6c75cb96d2ce549be6c35efa3099d25b – < a962bc8508592c4d51092edac68579bd8b18fe44
    • affected d2bc90cf6c75cb96d2ce549be6c35efa3099d25b – < 16c8ae9735c5bd7e54dd7478d6348e0fc860842d
    • affected c580087743712112778a06d65a4074053072d7bf
    • affected 6.6.143 – < 6.6.145
    • affected 6.12.93 – < 6.12.97
    • affected 6.18.35 – < 6.18.40
    • affected 7.0.11 – < 7.1
  • Linux · Linux

    • affected 7.1
    • unaffected < 7.1
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.97 – ≤ 6.12.*
    • unaffected 6.18.40 – ≤ 6.18.*
    • unaffected 7.1.5 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-74435 badge
[![CVE-2026-74435](https://cveledger.app/badge/CVE-2026-74435.svg)](https://cveledger.app/cve/CVE-2026-74435)

Record last updated .