LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26610: wifi: iwlwifi: fix a memory corruption

In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: fix a memory corruption iwl_fw_ini_trigger_tlv::data is a pointer to a __le32, which means that if we copy to iwl_fw_ini_trigger_tlv::data + offset while offset is in bytes, we'll write past the buffer.

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-26610 is a Linux kernel memory corruption bug in the Intel iwlwifi wireless driver. The public record says a byte offset was applied to a 32-bit pointer, causing writes past the intended buffer. Severity and exploitation impact are not provided in the source bundle.

Executive priority

Handle through normal kernel patch governance, with higher priority for Linux laptops and workstations using Intel Wi-Fi. The urgency is constrained by missing severity, impact, and exploitation evidence.

Technical view

The flaw is in iwl_fw_ini_trigger_tlv::data handling. The field is a __le32 pointer, but code copied to data + offset while treating offset as bytes. That pointer arithmetic can move the write beyond the buffer. Linux stable commits are listed as fixes across supported kernel lines.

Likely exposure

Exposure is most relevant to Linux systems using the Intel iwlwifi Wi-Fi driver on affected kernel versions. Servers without Intel wireless hardware or without this driver loaded are less likely to be exposed, based on the provided description.

Exploitation context

The bundle does not cite active exploitation, public exploit use, KEV inclusion, CVSS, or a proven impact path. Treat exploitability as unconfirmed rather than absent.

Researcher notes

The core issue is incorrect pointer arithmetic against a __le32 pointer. The public data identifies the defect and fix commits, but not attacker requirements, reachable trigger conditions, privilege impact, or crash-versus-code-execution outcome.

Mitigation direction

  • Identify Linux systems using the iwlwifi driver.
  • Apply kernel updates that include the listed Linux stable fixes.
  • Review Debian LTS guidance for Debian-managed systems.
  • Check vendor distribution advisories before assuming a specific fixed package version.
  • Prioritize mobile and workstation fleets with Intel Wi-Fi hardware.

Validation and detection

  • Confirm kernel version and distribution patch level.
  • Check whether the iwlwifi module is present or loaded.
  • Map systems against vendor advisories and stable fix commits.
  • Verify updated kernels are installed and booted.
  • Document exceptions where wireless hardware is absent.
Prepared
Confidence
medium
Sources
9

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-26610 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
8Source 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxcf29c5b66b9f83939367d90679eb68cdfa2f0356, cf29c5b66b9f83939367d90679eb68cdfa2f0356, cf29c5b66b9f83939367d90679eb68cdfa2f0356, cf29c5b66b9f83939367d90679eb68cdfa2f0356, cf29c5b66b9f83939367d90679eb68cdfa2f0356, cf29c5b66b9f83939367d90679eb68cdfa2f0356unaffected
LinuxLinux5.5, 0, 5.10.210, 5.15.149, 6.1.76, 6.6.15, 6.7.3, 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.