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-23138tracing: Add recursion protection in kernel stack trace recording

Description

In the Linux kernel, the following vulnerability has been resolved: tracing: Add recursion protection in kernel stack trace recording A bug was reported about an infinite recursion caused by tracing the rcu events with the kernel stack trace trigger enabled. The stack trace code called back into RCU which then called the stack trace again. Expand the ftrace recursion protection to add a set of bits to protect events from recursion. Each bit represents the context that the event is in (normal, softirq, interrupt and NMI). Have the stack trace code use the interrupt context to protect against recursion. Note, the bug showed an issue in both the RCU code as well as the tracing stacktrace code. This only handles the tracing stack trace side of the bug. The RCU fix will be handled separately.

Timeline

  1. ID reserved

    By Linux

  2. · 32 days later

    Published

  3. · 9 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-23138, by who scored it
Scored byCVSSScoreVector
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.17% · top 93% 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: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 5f5fa7ea89dc82d34ed458f4d7a8634e8e9eefce – < 80fe242a6239778025ba3be8e7263e3d69c37947
    • affected 5f5fa7ea89dc82d34ed458f4d7a8634e8e9eefce – < 9b03768037d91ce727effb1c5d92d2c7781bf692
    • affected 5f5fa7ea89dc82d34ed458f4d7a8634e8e9eefce – < 19e18e6dabb1bbba76d2809ca7d8ae9e1f5975fe
    • affected 5f5fa7ea89dc82d34ed458f4d7a8634e8e9eefce – < 5b7f91acffd2c4c000971553d22efa1e1bb4feae
    • affected 5f5fa7ea89dc82d34ed458f4d7a8634e8e9eefce – < 5f1ef0dfcb5b7f4a91a9b0e0ba533efd9f7e2cdb
  • Linux · Linux

    • affected 5.8
    • unaffected < 5.8
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.130 – ≤ 6.6.*
    • unaffected 6.12.78 – ≤ 6.12.*
    • unaffected 6.18.6 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .