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-2025-38514rxrpc: Fix oops due to non-existence of prealloc backlog struct

Description

In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix oops due to non-existence of prealloc backlog struct If an AF_RXRPC service socket is opened and bound, but calls are preallocated, then rxrpc_alloc_incoming_call() will oops because the rxrpc_backlog struct doesn't get allocated until the first preallocation is made. Fix this by returning NULL from rxrpc_alloc_incoming_call() if there is no backlog struct. This will cause the incoming call to be aborted.

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 14 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-2025-38514, 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 · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.39% · top 66% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · 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.5.

Affected products

  • Linux · Linux

    • affected 248f219cb8bcbfbd7f132752d44afa2df7c241d1 – < bf0ca6a1bc4fb904b598137c6718785a107e3adf
    • affected 248f219cb8bcbfbd7f132752d44afa2df7c241d1 – < f7afb3ff01c42c49e8a143cdce400b95844bb506
    • affected 248f219cb8bcbfbd7f132752d44afa2df7c241d1 – < f5e72b7824d08c206ce106d30cb37c4642900ccc
    • affected 248f219cb8bcbfbd7f132752d44afa2df7c241d1 – < 0eef29385d715d4c7fd707b18d4a9b76c76dd5e6
    • affected 248f219cb8bcbfbd7f132752d44afa2df7c241d1 – < efc1b2b7c1a308b60df8f36bc2d7ce16d3999364
    • affected 248f219cb8bcbfbd7f132752d44afa2df7c241d1 – < d1ff5f9d2c5405681457262e23c720b08977c11f
    • affected 248f219cb8bcbfbd7f132752d44afa2df7c241d1 – < 2c2e9ebeb036f9b1b09325ec5cfdfe0e78f357c3
    • affected 248f219cb8bcbfbd7f132752d44afa2df7c241d1 – < 880a88f318cf1d2a0f4c0a7ff7b07e2062b434a4
  • Linux · Linux

    • affected 4.9
    • unaffected < 4.9
    • unaffected 5.4.296 – ≤ 5.4.*
    • unaffected 5.10.240 – ≤ 5.10.*
    • unaffected 5.15.189 – ≤ 5.15.*
    • unaffected 6.1.146 – ≤ 6.1.*
    • unaffected 6.6.99 – ≤ 6.6.*
    • unaffected 6.12.39 – ≤ 6.12.*
    • unaffected 6.15.7 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .