LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26723: lan966x: Fix crash when adding interface under a lag

In the Linux kernel, the following vulnerability has been resolved: lan966x: Fix crash when adding interface under a lag There is a crash when adding one of the lan966x interfaces under a lag interface. The issue can be reproduced like this: ip link add name bond0 type bond miimon 100 mode balance-xor ip link set dev eth0 master bond0 The reason is because when adding a interface under the lag it would go through all the ports and try to figure out which other ports are under that lag interface. And the issue is that lan966x can have ports that are NULL pointer as they are not probed. So then iterating over these ports it would just crash as they are NULL pointers. The fix consists in actually checking for NULL pointers before accessing something from the ports. Like we do in other places.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel crash issue in the lan966x network driver. A local user with enough privilege to change network interfaces could trigger a crash when adding a lan966x interface to a link aggregation group. Business impact is mainly availability loss on affected systems using this hardware and driver.

Executive priority

Treat as high priority for affected network appliances, embedded Linux devices, and operational systems using LAN966x networking. For standard servers without lan966x hardware, priority is lower after exposure is ruled out.

Technical view

The lan966x driver iterated over possible ports while handling LAG membership and dereferenced entries that could be NULL for unprobed ports. The kernel fix adds NULL checks before accessing port data. The CVSS vector is local, low complexity, low privilege, no user interaction, with high CIA impact.

Likely exposure

Exposure appears limited to Linux systems using the lan966x driver, especially where lan966x interfaces may be placed under LAG or bonding. General Linux systems without this hardware or driver path are less likely exposed.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The described trigger requires local access with privileges sufficient to modify network interface configuration, reducing internet-scale risk but leaving operational systems exposed to local misuse or accidents.

Researcher notes

Evidence is strongest for a NULL pointer crash in the lan966x LAG handling path. The CVE record names stable kernel commits but the bundle does not provide a distribution-specific package matrix. Avoid claiming remote exploitability or active exploitation from these sources.

Mitigation direction

  • Apply vendor kernel updates containing the referenced lan966x fix.
  • Check distribution advisories for the exact fixed kernel package.
  • Restrict who can modify network interfaces on affected systems.
  • Avoid LAG or bonding changes on lan966x interfaces until patched.
  • Prioritize appliances or embedded systems using Microchip LAN966x networking.

Validation and detection

  • Inventory kernels and confirm whether the lan966x driver is present or loaded.
  • Identify systems using LAN966x hardware or lan966x network interfaces.
  • Check whether affected hosts use bonding or LAG configuration.
  • Verify the running kernel includes one of the referenced stable fixes.
  • Review logs for kernel crashes around interface bonding changes.
Prepared
Confidence
high
Sources
6

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.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-26723 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-26723Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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
cvssV3_1other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxcabc9d49333df72fe0f6d58bdcf9057ba341e701, cabc9d49333df72fe0f6d58bdcf9057ba341e701, cabc9d49333df72fe0f6d58bdcf9057ba341e701, cabc9d49333df72fe0f6d58bdcf9057ba341e701unaffected
LinuxLinux6.1, 0, 6.1.79, 6.6.18, 6.7.6, 6.8affected
Weakness

CWE details

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

CWE-400 · source CWE mapping

Uncontrolled Resource Consumption

Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.