LiveActive security incident?Get immediate response
CVE Record

CVE-2024-46825: wifi: iwlwifi: mvm: use IWL_FW_CHECK for link ID check

In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: use IWL_FW_CHECK for link ID check The lookup function iwl_mvm_rcu_fw_link_id_to_link_conf() is normally called with input from the firmware, so it should use IWL_FW_CHECK() instead of WARN_ON().

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects the Intel iwlwifi MVM Wi-Fi driver. Firmware-provided link IDs were checked with a kernel warning path instead of a firmware-aware check. The public record does not state business impact, exploitability, or observed attacks, so urgency depends on whether affected Linux kernels and Intel Wi-Fi hardware are present.

Executive priority

Treat this as a targeted kernel maintenance item, not an emergency based on current evidence. Prioritize normal patch cycles for Linux endpoints using Intel Wi-Fi, and escalate only if vendor advisories later identify material impact or exploitation.

Technical view

CVE-2024-46825 changes iwl_mvm_rcu_fw_link_id_to_link_conf() to use IWL_FW_CHECK() rather than WARN_ON() because the link ID input normally comes from firmware. The source bundle identifies Linux kernel affected versions and stable commits, but provides no CVSS, CWE, exploit details, or explicit impact statement.

Likely exposure

Likely limited to Linux systems running affected kernel versions with the iwlwifi MVM driver active for Intel Wi-Fi hardware. Servers without this driver or hardware are less likely exposed, but confirm from kernel version and loaded drivers.

Exploitation context

The bundle does not show active exploitation. KEV is false, and no cited source states public exploitation, exploit availability, or a proven remote attack path.

Researcher notes

The record is sparse: severity, CVSS, CWE, and concrete impact are absent. Analysis should stay focused on the driver logic change and affected kernel lineage. Do not infer memory corruption, privilege escalation, or remote compromise from the supplied sources alone.

Mitigation direction

  • Check distribution or kernel vendor advisories for fixed kernel packages.
  • Prioritize updates on laptops or endpoints using Intel Wi-Fi with iwlwifi MVM.
  • If patching is delayed, assess whether affected Wi-Fi hardware or driver use can be reduced.
  • Track the referenced stable kernel commits for backport status in your distribution.

Validation and detection

  • Inventory Linux kernel versions across endpoints and fleet images.
  • Identify systems with Intel Wi-Fi hardware and the iwlwifi driver loaded.
  • Compare installed kernels against vendor advisories and referenced stable fixes.
  • Review security tooling for kernel package update status and exceptions.
Prepared
Confidence
medium
Sources
5

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-46825 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
4Source 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd464550bb2e9cce2c377ed39c7e327e7db6e2be9, d464550bb2e9cce2c377ed39c7e327e7db6e2be9, d464550bb2e9cce2c377ed39c7e327e7db6e2be9unaffected
LinuxLinux6.5, 0, 6.6.51, 6.10.10, 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.