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-45998rxrpc: Fix potential UAF after skb_unshare() failure

Description

In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix potential UAF after skb_unshare() failure If skb_unshare() fails to unshare a packet due to allocation failure in rxrpc_input_packet(), the skb pointer in the parent (rxrpc_io_thread()) will be NULL'd out. This will likely cause the call to trace_rxrpc_rx_done() to oops. Fix this by moving the unsharing down to where rxrpc_input_call_event() calls rxrpc_input_call_packet(). There are a number of places prior to that where we ignore DATA packets for a variety of reasons (such as the call already being complete) for which an unshare is then avoided. And with that, rxrpc_input_packet() doesn't need to take a pointer to the pointer to the packet, so change that to just a pointer.

Timeline

  1. ID reserved

    By Linux

  2. · 14 days later

    Published

  3. · 5 months 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-45998, by who scored it
Scored byCVSSScoreVector
redhat-SADPADP (enrichment)3.1High7.0CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.14% · top 97% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 2d1faf7a0ca3c0b327cf064c80e4e775532c9319 – < e3bf143b1e98fb3d6d9e6825bcd683974d478e8c
    • affected 2d1faf7a0ca3c0b327cf064c80e4e775532c9319 – < bf20f46d94f1db38e6ffc0ca204a5fe0de01b495
    • affected 2d1faf7a0ca3c0b327cf064c80e4e775532c9319 – < 996b0487b3cdda4c91811dbb1c9564626bc840bd
    • affected 2d1faf7a0ca3c0b327cf064c80e4e775532c9319 – < 8fde6296c4d4da2be7ab761305ab7f232b94eefd
    • affected 2d1faf7a0ca3c0b327cf064c80e4e775532c9319 – < 1f2740150f904bfa60e4bad74d65add3ccb5e7f8
  • Linux · Linux

    • affected 6.2
    • unaffected < 6.2
    • unaffected 6.6.140 – ≤ 6.6.*
    • unaffected 6.12.86 – ≤ 6.12.*
    • unaffected 6.18.27 – ≤ 6.18.*
    • unaffected 7.0.4 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References14

Sources

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

Badge for a README or a ticket

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

Record last updated .