LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23084: be2net: Fix NULL pointer dereference in be_cmd_get_mac_from_list

In the Linux kernel, the following vulnerability has been resolved: be2net: Fix NULL pointer dereference in be_cmd_get_mac_from_list When the parameter pmac_id_valid argument of be_cmd_get_mac_from_list() is set to false, the driver may request the PMAC_ID from the firmware of the network card, and this function will store that PMAC_ID at the provided address pmac_id. This is the contract of this function. However, there is a location within the driver where both pmac_id_valid == false and pmac_id == NULL are being passed. This could result in dereferencing a NULL pointer. To resolve this issue, it is necessary to pass the address of a stub variable to the function.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

A flaw in Linux's be2net network driver can dereference an invalid NULL address while obtaining a network card identifier from firmware. The resulting driver or kernel fault could disrupt networking or system availability. The supplied evidence does not establish remote exploitability, confidentiality impact, or active exploitation.

Executive priority

Use accelerated routine patching for systems that actually depend on be2net, particularly critical servers and appliances. Available evidence does not justify an emergency internet-wide response, but potential kernel or network disruption warrants prompt inventory and vendor-supported remediation.

Technical view

be_cmd_get_mac_from_list() may write a firmware-provided PMAC_ID through pmac_id when pmac_id_valid is false. One caller supplies that combination with pmac_id set to NULL, creating a NULL-pointer dereference. The kernel fix supplies a valid stub variable address. Exact triggering conditions and resulting fault behavior are not detailed.

Likely exposure

Exposure is limited to Linux systems using the be2net driver and an affected kernel build. The supplied version data lists several releases but contains ambiguous entries, including “0” and a duplicated commit hash. Confirm applicability through distribution backport records rather than relying solely on version strings.

Exploitation context

The source bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public exploit. It also does not establish whether an untrusted remote party can reach the faulty path. Treat the primary plausible consequence as availability disruption, subject to vendor confirmation.

Researcher notes

The affected-version representation is insufficient for reliable branch-boundary analysis. Researchers should correlate distribution source packages with the seven referenced stable commits and inspect the corrected caller. The bundle provides no CVSS score, CWE assignment, trigger provenance, privilege requirement, or demonstrated security impact beyond the NULL-pointer condition.

Mitigation direction

  • Inventory Linux systems where the be2net driver is loaded or bound to hardware.
  • Install a distribution or vendor kernel update containing the applicable stable fix.
  • If updating is delayed, request supported temporary mitigation guidance from the Linux distribution or system vendor.
  • Prioritize availability-sensitive systems where failure of the affected network interface would cause material disruption.

Validation and detection

  • Record the running kernel build and determine whether be2net is loaded and actively bound.
  • Check distribution advisories or package changelogs for a backport of the referenced fix.
  • After updating, confirm the system boots the remediated kernel and the interface operates normally.
  • Review kernel logs for NULL dereferences, be2net faults, or unexplained interface failures.
Prepared
Confidence
medium
Sources
9

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-23084 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
9Source 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
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux95046b927a54f461766f83a212c6a93bc5fd2e67, 95046b927a54f461766f83a212c6a93bc5fd2e67, 95046b927a54f461766f83a212c6a93bc5fd2e67, 95046b927a54f461766f83a212c6a93bc5fd2e67, 95046b927a54f461766f83a212c6a93bc5fd2e67, 95046b927a54f461766f83a212c6a93bc5fd2e67, 95046b927a54f461766f83a212c6a93bc5fd2e67unaffected
LinuxLinux3.12, 0, 5.10.249, 5.15.199, 6.1.162, 6.6.122, 6.12.68, 6.18.8, 6.19affected
Weakness

CWE details

No CWE listed

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