LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23020: net: 3com: 3c59x: fix possible null dereference in vortex_probe1()

In the Linux kernel, the following vulnerability has been resolved: net: 3com: 3c59x: fix possible null dereference in vortex_probe1() pdev can be null and free_ring: can be called in 1297 with a null pdev.

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

Security readout for executives and security teams

Plain-English summary

CVE-2026-23020 is a Linux kernel defect in the 3Com 3c59x network driver. The provided record says a cleanup path can dereference a null device pointer. Business impact is not fully quantified, but this kind of kernel bug can plausibly affect system availability if the vulnerable path is reached.

Executive priority

Handle through the normal kernel vulnerability management process, with higher priority for legacy or specialized systems that may use 3Com 3c59x networking. There is no source-backed evidence of active exploitation in the provided bundle.

Technical view

The issue is in vortex_probe1() in the Linux kernel net/3com/3c59x driver. The CVE states pdev can be null and free_ring can be called with that null pdev. Stable kernel commits are referenced as fixes, but no CVSS, CWE, or detailed attack preconditions are provided.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions where the 3c59x driver is present and relevant. Systems without this driver built, loaded, or probed are less likely to be exposed, but the provided data does not fully define exploitability.

Exploitation context

The provided bundle does not show KEV listing or active exploitation. It also does not describe a public exploit, remote attack path, or privilege requirement. Treat exploitation status as unconfirmed.

Researcher notes

The record is sparse: severity is unknown, CVSS is absent, and impact is inferred only from a kernel null dereference description. Research should focus on exact affected version ranges, driver reachability, and whether the flaw is triggerable outside local hardware or probe conditions.

Mitigation direction

  • Check Linux distribution advisories for kernels containing the referenced stable fixes.
  • Prioritize systems using affected kernels with the 3c59x driver enabled or loaded.
  • Update affected kernels through the normal vendor-supported patch channel.
  • If patch timing is constrained, review vendor guidance for driver-specific risk reduction.

Validation and detection

  • Inventory kernel versions against the affected version data in the CVE record.
  • Identify whether the 3c59x driver is built, available, or loaded on Linux hosts.
  • Confirm patched kernels include one of the referenced stable commits or vendor backports.
  • Monitor vendor advisories for CVSS, impact clarification, and distribution-specific package names.
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-23020 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
8Source 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux55c82617c3e82210b7471e9334e8fc5df6a9961f, 55c82617c3e82210b7471e9334e8fc5df6a9961f, 55c82617c3e82210b7471e9334e8fc5df6a9961f, 55c82617c3e82210b7471e9334e8fc5df6a9961f, 55c82617c3e82210b7471e9334e8fc5df6a9961f, 55c82617c3e82210b7471e9334e8fc5df6a9961f, 55c82617c3e82210b7471e9334e8fc5df6a9961f, d30fdc02c49ad9965bba25015ae66c22dae967d1, 4.16.12unaffected
LinuxLinux4.17, 0, 5.10.248, 5.15.198, 6.1.161, 6.6.121, 6.12.66, 6.18.6, 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.