LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38585: tools/nolibc/stdlib: fix memory error in realloc()

In the Linux kernel, the following vulnerability has been resolved: tools/nolibc/stdlib: fix memory error in realloc() Pass user_p_len to memcpy() instead of heap->len to prevent realloc() from copying an extra sizeof(heap) bytes from beyond the allocated region.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-38585 is a Linux tools/nolibc realloc() memory error. The faulty code could copy bytes beyond the allocated buffer. The public record does not provide CVSS, CWE, concrete impact, or active exploitation evidence, so urgency depends on whether your Linux builds or tooling use the affected nolibc code.

Executive priority

Handle through normal Linux maintenance unless your organization builds or ships software using nolibc from affected Linux source trees. There is no active exploitation evidence in the bundle, but the missing severity score means teams should verify vendor patch status instead of ignoring it.

Technical view

The resolved Linux kernel issue changes tools/nolibc/stdlib realloc() to pass the user payload length to memcpy(), instead of heap->len. The prior length could copy an extra heap metadata-sized region beyond the allocation. Stable kernel commits are referenced as fixes, but the source bundle does not describe exploitability or downstream package status.

Likely exposure

Exposure is most likely in environments building or shipping Linux source versions that include the affected tools/nolibc implementation. Standard kernel version numbers alone may be insufficient because downstream vendors can backport fixes. The bundle lists affected Linux versions around 5.19 through 6.10 and stable fix commits.

Exploitation context

The CVE source bundle marks KEV as false and provides no cited evidence of active exploitation. It also does not describe a public proof of concept, attacker prerequisites, or reachable attack surface. Treat exploitation status as unconfirmed, not actively exploited.

Researcher notes

Evidence is limited to the CVE record and Linux stable commits. The bug is a realloc() over-read during memcpy length selection, not a fully described end-to-end attack. No CVSS, CWE, exploit conditions, privilege boundaries, or confidentiality impact are provided in the bundle.

Mitigation direction

  • Check your Linux vendor advisory or package changelog for CVE-2024-38585.
  • Update to a vendor kernel package containing the referenced stable fix.
  • For source builds, confirm tools/nolibc/stdlib realloc() uses the corrected memcpy length.
  • Prioritize custom static or embedded builds that include nolibc components.
  • Record any vendor backport evidence in vulnerability tracking.

Validation and detection

  • Inventory Linux kernel source and package versions in affected environments.
  • Compare downstream patches against the referenced git.kernel.org stable commits.
  • Review build manifests for projects using tools/nolibc or nolibc headers.
  • Confirm vulnerability scanners recognize vendor backports, not only upstream version numbers.
  • Document unresolved systems where vendor fix status is unknown.
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-2024-38585 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
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0e0ff638400be8f497a35b51a4751fd823f6bd6a, 0e0ff638400be8f497a35b51a4751fd823f6bd6a, 0e0ff638400be8f497a35b51a4751fd823f6bd6a, 0e0ff638400be8f497a35b51a4751fd823f6bd6a, 0e0ff638400be8f497a35b51a4751fd823f6bd6aunaffected
LinuxLinux5.19, 0, 6.1.93, 6.6.33, 6.8.12, 6.9.3, 6.10affected
Weakness

CWE details

No CWE listed

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