LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26920: tracing/trigger: Fix to return error if failed to alloc snapshot

In the Linux kernel, the following vulnerability has been resolved: tracing/trigger: Fix to return error if failed to alloc snapshot Fix register_snapshot_trigger() to return error code if it failed to allocate a snapshot instead of 0 (success). Unless that, it will register snapshot trigger without an error.

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-26920 is a Linux kernel tracing bug. If the kernel fails to allocate a tracing snapshot, it can still report success and register the snapshot trigger. The public record does not provide severity, CVSS, impact detail, or evidence of exploitation.

Executive priority

Track this as a kernel maintenance item, not an emergency, unless a vendor advisory for your environment raises severity. The current public evidence lacks impact scoring and exploitation confirmation, so priority should be driven by asset criticality and vendor guidance.

Technical view

The flaw is in the Linux kernel tracing trigger path. register_snapshot_trigger() returned success after snapshot allocation failure, allowing a snapshot trigger to be registered in an inconsistent error state. Kernel stable commits are listed as remediation references, but the bundle does not describe attacker requirements or security impact.

Likely exposure

Exposure is limited to systems running affected Linux kernel versions or downstream products that include those kernels. The bundle lists affected Linux versions and kernel stable fixes, but does not identify distributions, appliances, or configurations beyond Linux and a Siemens advisory reference.

Exploitation context

The source bundle does not report active exploitation, public exploit availability, or KEV listing. Because no CVSS or CWE is provided, exploitation likelihood and business impact cannot be reliably rated from these sources alone.

Researcher notes

The key behavior is incorrect success handling after snapshot allocation failure in tracing triggers. Sources do not define privilege prerequisites, reachable interfaces, or resulting impact. Avoid assuming code execution, privilege escalation, or denial of service without additional vendor or upstream analysis.

Mitigation direction

  • Identify systems running affected Linux kernel versions or vendor-derived builds.
  • Apply vendor kernel updates that include the referenced stable fixes.
  • For appliances, follow the relevant vendor advisory before changing kernels.
  • Prioritize internet-facing or security-sensitive Linux workloads for vendor confirmation.

Validation and detection

  • Inventory kernel versions across servers, endpoints, containers hosts, and appliances.
  • Compare installed kernels against vendor advisories and referenced stable commits.
  • Check whether downstream vendors have shipped fixed kernel packages.
  • Document unresolved systems where vendor fix status is unclear.
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-26920 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0bbe7f719985efd9adb3454679ecef0984cb6800, 0bbe7f719985efd9adb3454679ecef0984cb6800, 0bbe7f719985efd9adb3454679ecef0984cb6800, 0bbe7f719985efd9adb3454679ecef0984cb6800, 7c6feb347a4bb1f02e55f6814c93b5f7fab887a8, a289fd864722dcf5363fec66a35965d4964df515, 7054f86f268c0d9d62b52a4497dd0e8c10a7e5c7, 57f2a2ad73e99a7594515848f4da987326a15981, 0026e356e51ab3b54322eeb445c75a087ede5b9d, ffa70d104691aa609a18a9a6692049deb35f431f, 733c611a758c68894a4480fb999637476118a8fc, 4.4.220, 4.9.220, 4.14.177, 4.19.117, 5.4.34, 5.5.19, 5.6.6unaffected
LinuxLinux5.7, 0, 6.1.79, 6.6.18, 6.7.6, 6.8affected
Weakness

CWE details

No CWE listed

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