LiveActive security incident?Get immediate response
CVE Record

CVE-2024-58010: binfmt_flat: Fix integer overflow bug on 32 bit systems

In the Linux kernel, the following vulnerability has been resolved: binfmt_flat: Fix integer overflow bug on 32 bit systems Most of these sizes and counts are capped at 256MB so the math doesn't result in an integer overflow. The "relocs" count needs to be checked as well. Otherwise on 32bit systems the calculation of "full_data" could be wrong. full_data = data_len + relocs * sizeof(unsigned long);

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-58010 is a Linux kernel bug affecting 32-bit systems that use the flat binary loader. A crafted flat binary could make the kernel calculate memory sizing incorrectly. The source bundle confirms kernel stable fixes and Debian LTS advisories, but does not provide CVSS, CWE, impact severity, or active exploitation evidence.

Executive priority

Treat this as a targeted kernel maintenance issue rather than a broad emergency. Prioritize patch validation for 32-bit, embedded, legacy, and Debian LTS environments. The absence of CVSS and exploitation evidence lowers urgency, but kernel memory-calculation flaws still warrant timely remediation.

Technical view

The flaw is an integer overflow in binfmt_flat. The relocs count was not capped before calculating full_data as data_len plus relocs times sizeof(unsigned long). On 32-bit kernels this calculation can wrap, producing an incorrect size. The supplied references identify Linux stable commits and Debian LTS updates addressing the issue.

Likely exposure

Exposure is most likely on 32-bit Linux deployments where binfmt_flat support is present and flat-format binaries may be loaded. Standard 64-bit server fleets may have limited exposure, but embedded, legacy, or specialized 32-bit Linux systems should be checked carefully.

Exploitation context

The bundle does not show CISA KEV listing, public exploit activity, exploit code, or in-the-wild abuse. It also does not state the exact security impact beyond incorrect kernel size calculation, so exploitability and attacker prerequisites should be treated as not fully evidenced from these sources.

Researcher notes

Key unknowns are impact class, reachable attack surface, and affected configuration prevalence. Analysis should focus on 32-bit binfmt_flat behavior, relocs bounds checking, and whether local execution of flat binaries is required. Do not assume remote exploitability from the supplied evidence.

Mitigation direction

  • Apply vendor kernel updates that include the referenced Linux stable fixes.
  • Review Debian LTS advisories if running affected Debian-based kernels.
  • Inventory 32-bit Linux systems and embedded devices separately from standard servers.
  • Avoid running untrusted flat binaries until affected systems are updated.
  • Track distribution guidance for any configuration-specific mitigation or backport status.

Validation and detection

  • Identify systems running 32-bit Linux kernels.
  • Check whether deployed kernel versions include the referenced stable fixes.
  • Confirm distribution packages match the relevant Debian LTS or vendor advisory updates.
  • Review build configuration and runtime use of binfmt_flat where applicable.
  • Record exceptions where vendor fixes are unavailable and monitor vendor guidance.
Prepared
Confidence
medium
Sources
12

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-58010 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
1ADP providers
11Source 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.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc995ee28d29d6f256c3a8a6c4e66469554374f25, c995ee28d29d6f256c3a8a6c4e66469554374f25, c995ee28d29d6f256c3a8a6c4e66469554374f25, c995ee28d29d6f256c3a8a6c4e66469554374f25, c995ee28d29d6f256c3a8a6c4e66469554374f25, c995ee28d29d6f256c3a8a6c4e66469554374f25, c995ee28d29d6f256c3a8a6c4e66469554374f25, c995ee28d29d6f256c3a8a6c4e66469554374f25unaffected
LinuxLinux4.8, 0, 5.4.291, 5.10.235, 5.15.179, 6.1.129, 6.6.78, 6.12.14, 6.13.3, 6.14affected
Weakness

CWE details

No CWE listed

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