LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54171: tracing: Fix memory leak of iter->temp when reading trace_pipe

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().

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel memory leak in tracing. Reading trace_pipe can allocate iter->temp and, before the fix, closing the pipe did not free it. The supplied sources describe resource leakage, not code execution or data theft. Severity is not scored in the bundle.

Executive priority

Treat this as routine-to-prioritized kernel maintenance, not an emergency based on supplied evidence. Raise priority for multi-user Linux systems or environments where tracing interfaces are exposed to untrusted workloads.

Technical view

The bug is in Linux kernel tracing_read_pipe behavior. trace_find_next_entry allocates or relocates iter->temp while reading trace_pipe, but tracing_release_pipe previously did not free that buffer on close. Stable kernel commits fix this by freeing iter->temp in tracing_release_pipe.

Likely exposure

Potentially exposed systems are Linux kernels in the affected version ranges listed in the CVE bundle, including 5.7 through noted stable branches up to 6.5. Exposure depends on whether local users or processes can read trace_pipe; the bundle does not state required privileges.

Exploitation context

The source bundle does not report active exploitation, and KEV is false. The described trigger is reading trace_pipe and closing it, causing a kernel memory leak. No public exploit status, attack prerequisites, or weaponized technique is provided in the supplied sources.

Researcher notes

Evidence supports a kernel memory leak fixed by stable commits. Missing details include CVSS, CWE, privilege requirements, distribution package mapping, and exploitability analysis. Avoid assuming denial-of-service impact beyond the documented leak without additional vendor evidence.

Mitigation direction

  • Apply vendor kernel updates containing the referenced stable fixes.
  • Prioritize systems where untrusted local users can access tracing interfaces.
  • Check distribution advisories for exact fixed package versions.
  • Review trace_pipe access policy until patched.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Compare running kernels with affected and fixed vendor versions.
  • Confirm whether trace_pipe is present and access-controlled.
  • Verify patch deployment after reboot into the updated kernel.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-54171 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
6Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxff895103a84abc85a5f43ecabc7f67cf36e1348f, ff895103a84abc85a5f43ecabc7f67cf36e1348f, ff895103a84abc85a5f43ecabc7f67cf36e1348f, ff895103a84abc85a5f43ecabc7f67cf36e1348f, ff895103a84abc85a5f43ecabc7f67cf36e1348funaffected
LinuxLinux5.7, 0, 5.10.188, 5.15.121, 6.1.40, 6.4.5, 6.5affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.