LiveActive security incident?Get immediate response
CVE Record

CVE-2026-43056: net: mana: fix use-after-free in add_adev() error path

In the Linux kernel, the following vulnerability has been resolved: net: mana: fix use-after-free in add_adev() error path If auxiliary_device_add() fails, add_adev() jumps to add_fail and calls auxiliary_device_uninit(adev). The auxiliary device has its release callback set to adev_release(), which frees the containing struct mana_adev. Since adev is embedded in struct mana_adev, the subsequent fall-through to init_fail and access to adev->id may result in a use-after-free. Fix this by saving the allocated auxiliary device id in a local variable before calling auxiliary_device_add(), and use that saved id in the cleanup path after auxiliary_device_uninit().

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Linux's MANA network driver can access memory after freeing it when auxiliary-device registration fails. Because this occurs in kernel code, the supplied CVSS assessment rates potential confidentiality, integrity, and availability impact as high. The vector requires local, low-privileged access; the evidence does not establish how reliably an attacker can trigger or exploit the failure.

Executive priority

Identify affected Linux systems using MANA and schedule vendor-supported kernel updates within the normal high-severity patch cycle. Escalate systems running untrusted local users or workloads. The supplied evidence does not justify emergency internet-wide action because it shows neither remote reachability nor active exploitation.

Technical view

In add_adev(), auxiliary_device_add() failure enters cleanup. auxiliary_device_uninit() invokes adev_release(), freeing the enclosing mana_adev containing adev. Cleanup then reads adev->id, causing a use-after-free. The fix saves the allocated ID before registration and uses that local value after uninitialization. CVSS 3.1 is 7.8: local, low complexity, low privileges, and no user interaction.

Likely exposure

Potential exposure exists on Linux kernels containing the affected MANA driver code and reaching its auxiliary-device registration failure cleanup. The bundle lists 6.2, 6.6.134, 6.12.81, 6.18.22, 6.19.12, and 7.0 as affected version markers, plus an unexplained “0.” Distribution backports may alter status, requiring package-level confirmation.

Exploitation context

The record is not in KEV, and no supplied source reports active or public exploitation. The CVSS vector describes local access with low privileges, so this is not evidenced as remotely reachable. Exploitation feasibility beyond reaching the registration failure path is not established by the bundle.

Researcher notes

Focus validation on branch-specific backports and the add_adev() cleanup lifetime. The supplied version data is ambiguous, especially the “0” entry, and does not identify exact fixed distribution packages. The referenced stable commits are the supplied remediation anchors. Do not infer practical exploitability solely from the 7.8 score.

Mitigation direction

  • Inventory Linux hosts containing the MANA driver and compare their kernels with vendor vulnerability guidance.
  • Apply a vendor-supported kernel update containing the applicable referenced stable fix, then reboot into the updated kernel.
  • If updating is delayed, consult the Linux distributor for supported mitigations; the bundle names no standalone workaround.

Validation and detection

  • Record the running kernel version and distributor build on each potentially exposed host.
  • Confirm the installed kernel includes the applicable referenced stable commit or an official vendor backport.
  • Verify systems rebooted into the remediated kernel and are not running the previous vulnerable build.
  • Review kernel logs for MANA auxiliary-device initialization failures; their absence does not prove the system is unaffected.
Prepared
Confidence
medium
Sources
7

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-2026-43056 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
0ADP providers
6Source links

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.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-43056Attack 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxa69839d4327d053b18d8e1b0e7ddeee78db78f4f, a69839d4327d053b18d8e1b0e7ddeee78db78f4f, a69839d4327d053b18d8e1b0e7ddeee78db78f4f, a69839d4327d053b18d8e1b0e7ddeee78db78f4f, a69839d4327d053b18d8e1b0e7ddeee78db78f4funaffected
LinuxLinux6.2, 0, 6.6.134, 6.12.81, 6.18.22, 6.19.12, 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.