LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26634: net: fix removing a namespace with conflicting altnames

In the Linux kernel, the following vulnerability has been resolved: net: fix removing a namespace with conflicting altnames Mark reports a BUG() when a net namespace is removed. kernel BUG at net/core/dev.c:11520! Physical interfaces moved outside of init_net get "refunded" to init_net when that namespace disappears. The main interface name may get overwritten in the process if it would have conflicted. We need to also discard all conflicting altnames. Recent fixes addressed ensuring that altnames get moved with the main interface, which surfaced this problem.

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 can trigger a kernel BUG when a network namespace is removed and physical interfaces return to the initial namespace with conflicting alternate names. The record points to stability or availability risk, not proven data theft or remote compromise. Severity is not scored in the provided sources.

Executive priority

Treat this as a kernel reliability issue needing routine but visible patch management. Escalate priority for container platforms, network appliances, or multi-tenant systems where namespace teardown failures could disrupt workloads. Current evidence does not justify emergency response based on exploitation alone.

Technical view

The fix discards conflicting interface altnames during net namespace teardown when devices are refunded to init_net. Recent altname movement fixes exposed a conflict path that can hit BUG() in net/core/dev.c. The bundle provides Linux kernel version data and stable commits, but no CVSS, CWE, or exploit mechanics.

Likely exposure

Exposure is most likely on Linux systems using affected kernel builds with network namespaces and physical interfaces moved between namespaces. Container, virtualization, or network automation hosts deserve closer review. The provided affected-version data is incomplete and should be validated against vendor kernel packages.

Exploitation context

The provided sources do not show active exploitation, and KEV is false. They describe a kernel BUG during namespace removal with conflicting alternate interface names. No public exploit status, attack preconditions, privilege requirements, or remote attack path is established in the supplied bundle.

Researcher notes

Key evidence is the Linux kernel fix narrative: conflicting alternate names must be discarded when interfaces return to init_net. The record lacks CVSS, CWE, exploitability detail, and precise distro package mapping, so validation should stay source-grounded and vendor-specific.

Mitigation direction

  • Identify deployed Linux kernel versions across production and container hosts.
  • Check vendor advisories for fixed packages matching the listed stable commits.
  • Prioritize updates on hosts using network namespaces or advanced interface naming.
  • Avoid relying on custom fixes unless they match vendor-supported kernel patches.
  • Track remediation through normal kernel patch and reboot workflows.

Validation and detection

  • Compare running kernel versions with the CVE record and vendor package advisories.
  • Review whether hosts use network namespaces with physical interface moves.
  • Check kernel logs for BUG entries referencing net/core/dev.c namespace removal.
  • Confirm patched kernels include one of the referenced stable fixes.
  • Document unresolved version ambiguity for vendor follow-up.
Prepared
Confidence
medium
Sources
6

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-26634 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
5Source 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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux673edcffa0960fc154085d639e10f80b6317d3bd, 7663d522099ecc464512164e660bc771b2ff7b64, 7663d522099ecc464512164e660bc771b2ff7b64, 7663d522099ecc464512164e660bc771b2ff7b64, f7a69786fe5ec75d1cdd71b465e74a1adc68ef40, 6.1.60, 6.5.9unaffected
LinuxLinux6.6, 0, 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.