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-2023-54171tracing: Fix memory leak of iter->temp when reading trace_pipe

Description

In the Linux kernel, the following vulnerability has been resolved: tracing: Fix memory leak of iter->temp when reading trace_pipe kmemleak reports: unreferenced object 0xffff88814d14e200 (size 256): comm "cat", pid 336, jiffies 4294871818 (age 779.490s) hex dump (first 32 bytes): 04 00 01 03 00 00 00 00 08 00 00 00 00 00 00 00 ................ 0c d8 c8 9b ff ff ff ff 04 5a ca 9b ff ff ff ff .........Z...... backtrace: [<ffffffff9bdff18f>] __kmalloc+0x4f/0x140 [<ffffffff9bc9238b>] trace_find_next_entry+0xbb/0x1d0 [<ffffffff9bc9caef>] trace_print_lat_context+0xaf/0x4e0 [<ffffffff9bc94490>] print_trace_line+0x3e0/0x950 [<ffffffff9bc95499>] tracing_read_pipe+0x2d9/0x5a0 [<ffffffff9bf03a43>] vfs_read+0x143/0x520 [<ffffffff9bf04c2d>] ksys_read+0xbd/0x160 [<ffffffff9d0f0edf>] do_syscall_64+0x3f/0x90 [<ffffffff9d2000aa>] entry_SYSCALL_64_after_hwframe+0x6e/0xd8 when reading file 'trace_pipe', 'iter->temp' is allocated or relocated in trace_find_next_entry() but not freed before 'trace_pipe' is closed. To fix it, free 'iter->temp' in tracing_release_pipe().

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 4 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (18 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected ff895103a84abc85a5f43ecabc7f67cf36e1348f – < 1a1e793e021d75cd0accd8f329ec9456e5cd105e
    • affected ff895103a84abc85a5f43ecabc7f67cf36e1348f – < 954792db9f61b6c0b8a94b8831fed5f146014029
    • affected ff895103a84abc85a5f43ecabc7f67cf36e1348f – < be970e22c53d5572b2795b79da9716ada937023b
    • affected ff895103a84abc85a5f43ecabc7f67cf36e1348f – < 3f42d57a76e7e96585f08855554e002218cbca0c
    • affected ff895103a84abc85a5f43ecabc7f67cf36e1348f – < d5a821896360cc8b93a15bd888fabc858c038dc0
  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • unaffected 5.10.188 – ≤ 5.10.*
    • unaffected 5.15.121 – ≤ 5.15.*
    • unaffected 6.1.40 – ≤ 6.1.*
    • unaffected 6.4.5 – ≤ 6.4.*
    • unaffected 6.5 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .