CVE-2026-68139

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

net/mlx5e: Use sender devcom for MPV master-up

After PCIe DPC recovery, mlx5 reloads the affected functions and replays multiport affiliation events. In the reported failure, the first relevant device error was:

pcieport 0000:10:01.1: DPC: containment event pcieport 0000:10:01.1: PCIe Bus Error: severity=Uncorrected (Fatal) pcieport 0000:10:01.1: [ 5] SDES (First)

mlx5 recovered the PCI functions and resumed 0000:11:00.1. During that resume, RDMA multiport binding replayed MLX5_DRIVER_EVENT_AFFILIATION_DONE and mlx5e sent MPV_DEVCOM_MASTER_UP. The host then panicked with:

BUG: kernel NULL pointer dereference, address: 0000000000000010 RIP: mlx5_devcom_comp_set_ready+0x5/0x40 [mlx5_core] RDI: 0000000000000000

Call trace included:

mlx5_devcom_comp_set_ready mlx5e_devcom_event_mpv mlx5_devcom_send_event mlx5_ib_bind_slave_port mlx5r_mp_probe mlx5_pci_resume

MPV devcom registration publishes mlx5e private data to the component peer list before mlx5e_devcom_init_mpv() stores the returned component device in priv->devcom. A concurrent master-up event can therefore reach a peer whose private data is visible but whose priv->devcom backpointer is still NULL.

MPV_DEVCOM_MASTER_UP already carries the sender/master mlx5e private data as event_data. The ready bit is stored on the shared devcom component, not on an individual peer. Use the sender devcom when marking the MPV component ready.

This preserves the readiness transition while avoiding a NULL dereference of the peer devcom pointer during affiliation replay after PCI error recovery.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 17, 2026

References (4)

Vendor Advisories for CVE-2026-68139(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 12× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 06:32 UTCGHSA enrichment
  3. 2026-08-19 17:04 UTCEPSS rescore
  4. 2026-08-18 13:48 UTCEPSS rescore
  5. 2026-08-17 13:47 UTCEPSS rescore
  6. 2026-08-17 05:40 UTCGHSA enrichment
  7. 2026-08-17 05:26 UTCNVD update
  8. 2026-08-17 05:11 UTCGHSA enrichment
  9. 2026-08-17 05:05 UTCMITRE cvelistV5
  10. 2026-08-16 15:10 UTCGHSA enrichment
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-15 01:30 UTCEPSS rescore
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-13 14:19 UTCEG score recompute
  15. 2026-08-13 14:19 UTCGHSA enrichment
  16. 2026-08-12 13:51 UTCEPSS rescore
  17. 2026-08-10 13:24 UTCNVD update
  18. 2026-08-10 12:21 UTCEG score recompute
  19. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-68139?
CVE-2026-68139 is a publicly disclosed vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Use sender devcom for MPV master-up After PCIe DPC recovery, mlx5 reloads the affected functions and replays multiport affiliation events. In the reported failure, the first relevant device error was: pcieport…
When was CVE-2026-68139 disclosed?
CVE-2026-68139 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68139 actively exploited?
CVE-2026-68139 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.7% of all scored CVEs.
How do I remediate CVE-2026-68139?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68139, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-68139

Explore →

Is Your Infrastructure Affected by CVE-2026-68139?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs