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-37938tracing: Verify event formats that have "%*p.."

Description

In the Linux kernel, the following vulnerability has been resolved: tracing: Verify event formats that have "%*p.." The trace event verifier checks the formats of trace events to make sure that they do not point at memory that is not in the trace event itself or in data that will never be freed. If an event references data that was allocated when the event triggered and that same data is freed before the event is read, then the kernel can crash by reading freed memory. The verifier runs at boot up (or module load) and scans the print formats of the events and checks their arguments to make sure that dereferenced pointers are safe. If the format uses "%*p.." the verifier will ignore it, and that could be dangerous. Cover this case as well. Also add to the sample code a use case of "%*pbl".

Timeline

  1. ID reserved

    By Linux

  2. · 34 days later

    Published

  3. · 17 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-37938, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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.21% · top 89% of all CVEs (19 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.1.

Affected products

  • Linux · Linux

    • affected 5013f454a352cce8e62162976026a9c472595e42 – < 6854c87ac823181c810f8c07489ba543260c0023
    • affected 5013f454a352cce8e62162976026a9c472595e42 – < 4d11fac941d83509be4e6a21038281d6d96da50c
    • affected 5013f454a352cce8e62162976026a9c472595e42 – < 03127354027508d076073b020d3070990fd6a958
    • affected 5013f454a352cce8e62162976026a9c472595e42 – < 04b80d45ecfaf780981d6582899e3ab205e4aa08
    • affected 5013f454a352cce8e62162976026a9c472595e42 – < c7204fd1758c0caf1938e8a59809a1fdf28a8114
    • affected 5013f454a352cce8e62162976026a9c472595e42 – < ea8d7647f9ddf1f81e2027ed305299797299aa03
  • Linux · Linux

    • affected 5.13
    • unaffected < 5.13
    • unaffected 6.1.136 – ≤ 6.1.*
    • unaffected 6.6.89 – ≤ 6.6.*
    • unaffected 6.12.26 – ≤ 6.12.*
    • unaffected 6.13.11 – ≤ 6.13.*
    • unaffected 6.14.2 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .