LiveActive security incident?Get immediate response
CVE Record

CVE-2024-43890: tracing: Fix overflow in get_free_elt()

In the Linux kernel, the following vulnerability has been resolved: tracing: Fix overflow in get_free_elt() "tracing_map->next_elt" in get_free_elt() is at risk of overflowing. Once it overflows, new elements can still be inserted into the tracing_map even though the maximum number of elements (`max_elts`) has been reached. Continuing to insert elements after the overflow could result in the tracing_map containing "tracing_map->max_size" elements, leaving no empty entries. If any attempt is made to insert an element into a full tracing_map using `__tracing_map_insert()`, it will cause an infinite loop with preemption disabled, leading to a CPU hang problem. Fix this by preventing any further increments to "tracing_map->next_elt" once it reaches "tracing_map->max_elt".

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2024-43890 is a Linux kernel tracing bug that can make a CPU hang. The issue occurs when a tracing map counter overflows, allowing inserts after the intended maximum and potentially causing an infinite loop with preemption disabled. The documented impact is availability, not data theft or privilege escalation.

Executive priority

Treat this as a normal-priority kernel availability fix unless exposed assets are high-criticality or multi-tenant. There is no cited active exploitation, but a CPU hang risk in the kernel can still disrupt production systems.

Technical view

In get_free_elt(), tracing_map->next_elt could overflow after reaching max_elts. That allowed additional entries until the map became full. A later __tracing_map_insert() into the full tracing_map could loop indefinitely while preemption is disabled, causing a CPU hang. Linux stable commits address this by stopping next_elt increments once max_elt is reached.

Likely exposure

Exposure is likely limited to systems running affected Linux kernel versions or vendor products that embed them. The source bundle lists Linux kernel versions and stable backport commits, plus Debian LTS advisories. Confirm exposure by matching deployed kernel versions and vendor firmware advisories.

Exploitation context

The source bundle does not show KEV listing or active exploitation. It describes a kernel availability flaw in the tracing subsystem. No public exploit status, required privileges, or remotely reachable attack path is established in the provided evidence.

Researcher notes

The core condition is counter overflow in tracing_map allocation state, followed by insertion behavior when the map has no empty entries. Evidence supports a denial-of-service outcome through CPU hang. The bundle does not establish exploit prerequisites, reachability, or privilege requirements.

Mitigation direction

  • Update affected Linux kernels to vendor-supported fixed builds.
  • Apply relevant Debian LTS kernel updates where Debian is in use.
  • Check embedded-product vendor advisories before changing appliance firmware.
  • Prioritize systems where local users, agents, or workloads can exercise kernel tracing paths.
  • Monitor vendor guidance for any revised severity or exploitation information.

Validation and detection

  • Inventory kernel versions across servers, containers hosts, appliances, and build images.
  • Compare deployed versions with the CVE record and Linux stable fix commits.
  • Check Debian LTS advisory applicability for Debian-based systems.
  • Review vendor advisories for Siemens or other embedded Linux products in scope.
  • After updates, verify systems boot the expected fixed kernel version.
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-43890 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
3ADP providers
14Source 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

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux08d43a5fa063e03c860f2f391a30c388bcbc948e, 08d43a5fa063e03c860f2f391a30c388bcbc948e, 08d43a5fa063e03c860f2f391a30c388bcbc948e, 08d43a5fa063e03c860f2f391a30c388bcbc948e, 08d43a5fa063e03c860f2f391a30c388bcbc948e, 08d43a5fa063e03c860f2f391a30c388bcbc948e, 08d43a5fa063e03c860f2f391a30c388bcbc948e, 08d43a5fa063e03c860f2f391a30c388bcbc948eunaffected
LinuxLinux4.7, 0, 4.19.320, 5.4.282, 5.10.224, 5.15.165, 6.1.105, 6.6.46, 6.10.5, 6.11affected
Weakness

CWE details

No CWE listed

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