LiveActive security incident?Get immediate response
CVE Record

CVE-2024-27410: wifi: nl80211: reject iftype change with mesh ID change

In the Linux kernel, the following vulnerability has been resolved: wifi: nl80211: reject iftype change with mesh ID change It's currently possible to change the mesh ID when the interface isn't yet in mesh mode, at the same time as changing it into mesh mode. This leads to an overwrite of data in the wdev->u union for the interface type it currently has, causing cfg80211_change_iface() to do wrong things when switching. We could probably allow setting an interface to mesh while setting the mesh ID at the same time by doing a different order of operations here, but realistically there's no userspace that's going to do this, so just disallow changes in iftype when setting mesh ID.

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-27410 is a Linux kernel Wi-Fi mesh handling flaw. A specific nl80211 interface change could overwrite internal interface state and make the kernel perform the wrong operation during a switch. Public sources do not provide a CVSS score, confirmed impact, or active exploitation evidence.

Executive priority

Treat this as a kernel maintenance item with uncertain severity. Prioritize patching where Wi-Fi or mesh capabilities are present, but do not escalate as actively exploited based on the provided evidence.

Technical view

The issue is in Linux kernel cfg80211/nl80211 handling when changing interface type while also setting a mesh ID. The kernel could overwrite data in the wdev->u union for the current interface type, leading cfg80211_change_iface() to behave incorrectly. Stable kernel commits reject this combined change.

Likely exposure

Exposure is most relevant to Linux systems using Wi-Fi stack functionality where nl80211 interface type changes and mesh mode configuration are possible. The source bundle lists Linux kernel versions as affected but does not define required attacker privileges or deployment prerequisites.

Exploitation context

The source bundle does not cite active exploitation, and KEV status is false. It describes a kernel state corruption condition reachable through interface configuration behavior, but does not provide public exploit status, attacker model, or impact classification.

Researcher notes

Key evidence is the upstream Linux fix rationale: reject simultaneous interface type change and mesh ID setting because it can corrupt the wdev union state. Missing details include CVSS, CWE, exploitability, privilege requirements, and concrete security impact.

Mitigation direction

  • Apply vendor Linux kernel updates that include the referenced stable fixes.
  • For Debian LTS systems, review the linked Debian LTS advisories.
  • Prioritize systems with wireless hardware and mesh-capable configurations.
  • Check distribution guidance before assuming a backport commit is present.

Validation and detection

  • Inventory Linux kernel versions across wireless-capable systems.
  • Confirm whether vendor packages include the stable fix commits.
  • Review Wi-Fi mesh and nl80211 usage on exposed systems.
  • Track remediation through normal kernel package compliance reporting.
Prepared
Confidence
medium
Sources
12

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-27410 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
11Source 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
LinuxLinux7b0a0e3c3a88260b6fcb017e49f198463aa62ed1, 7b0a0e3c3a88260b6fcb017e49f198463aa62ed1, 7b0a0e3c3a88260b6fcb017e49f198463aa62ed1, 7b0a0e3c3a88260b6fcb017e49f198463aa62ed1, 7a53ad13c09150076b7ddde96c2dfc5622c90b45, 5.19.2unaffected
LinuxLinux6.0, 0, 6.1.81, 6.6.21, 6.7.9, 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.