LiveActive security incident?Get immediate response
CVE Record

CVE-2026-43219: net: cpsw_new: Fix potential unregister of netdev that has not been registered yet

In the Linux kernel, the following vulnerability has been resolved: net: cpsw_new: Fix potential unregister of netdev that has not been registered yet If an error occurs during register_netdev() for the first MAC in cpsw_register_ports(), even though cpsw->slaves[0].ndev is set to NULL, cpsw->slaves[1].ndev would remain unchanged. This could later cause cpsw_unregister_ports() to attempt unregistering the second MAC. To address this, add a check for ndev->reg_state before calling unregister_netdev(). With this change, setting cpsw->slaves[i].ndev to NULL becomes unnecessary and can be removed accordingly.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2026-43219 is a Linux kernel defect in cpsw_new network driver cleanup. In a specific error path, the kernel may try to unregister a network device that was not successfully registered. Business impact is unclear from public data, but affected systems should take normal kernel update action.

Executive priority

Treat as a routine kernel maintenance item unless affected cpsw_new systems support critical operations. Escalate only if asset inventory confirms exposure and no vendor-fixed kernel is available.

Technical view

The flaw is in cpsw_register_ports() and cpsw_unregister_ports(). If register_netdev() fails for the first MAC, state for another MAC can remain set, causing unregister_netdev() to run against an unregistered netdev. The fix checks ndev->reg_state before unregistering.

Likely exposure

Exposure appears limited to Linux systems carrying the affected cpsw_new Ethernet driver code. The source bundle does not identify distributions, appliances, cloud images, or a complete affected hardware list.

Exploitation context

No active exploitation is stated. The CVE is not marked KEV. Public sources describe an error-handling bug, not a remote attack path or weaponized exploit.

Researcher notes

Evidence is limited to the CVE text and Linux stable commit references. No CVSS, CWE, exploit details, or downstream vendor impact is provided in the bundle.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable fixes.
  • Prioritize systems using kernels with the cpsw_new driver enabled.
  • Check distribution advisories for backported fixes before relying on version numbers.
  • Track unsupported or custom kernels for manual patch assessment.

Validation and detection

  • Inventory Linux kernel versions and custom kernel builds.
  • Confirm whether cpsw_new code is present, built, or loaded.
  • Compare deployed kernel source against the referenced stable commits.
  • Review vendor advisories for your distribution or device image.
Prepared
Confidence
medium
Sources
10

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-2026-43219 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
0ADP providers
9Source links

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxed3525eda4c4983fb8509e488de0a351788041ba, ed3525eda4c4983fb8509e488de0a351788041ba, ed3525eda4c4983fb8509e488de0a351788041ba, ed3525eda4c4983fb8509e488de0a351788041ba, ed3525eda4c4983fb8509e488de0a351788041ba, ed3525eda4c4983fb8509e488de0a351788041ba, ed3525eda4c4983fb8509e488de0a351788041ba, ed3525eda4c4983fb8509e488de0a351788041baunaffected
LinuxLinux5.5, 0, 5.10.260, 5.15.210, 6.1.176, 6.6.143, 6.12.93, 6.18.16, 6.19.6, 7.0affected
Weakness

CWE details

No CWE listed

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