CVE-2026-68139: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-6jxm-mj96-cq7j
Share
Published
Advisory Summary

CVE-2026-68139 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-68139 at a Glance

CVE Identifier CVE-2026-68139
GHSA Identifier GHSA-6jxm-mj96-cq7j
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-68139

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-68139, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

References

NVD — CVE-2026-68139 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-68139
git.kernel.org/stable/c/40f9a124eb... WEB
https://git.kernel.org/stable/c/40f9a124ebbe0d60fe165fb3f87515c35b2d72f5
git.kernel.org/stable/c/a60c81f168... WEB
https://git.kernel.org/stable/c/a60c81f168c9fe4f5d84302d1e32b717f5a8a933
git.kernel.org/stable/c/c698b27356... WEB
https://git.kernel.org/stable/c/c698b2735613f1f35c55688bd2252f75f31c49ad
git.kernel.org/stable/c/e32649b4ba... WEB
https://git.kernel.org/stable/c/e32649b4bad90a6216d8e93cd7dd050af8ac9740

Frequently Asked Questions

What is CVE-2026-68139?
CVE-2026-68139 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-68139?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-68139?
CVE-2026-68139 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-68139?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-6jxm-mj96-cq7j",
  "modified" : "2026-08-10T15:33:37Z",
  "published" : "2026-08-10T15:33:37Z",
  "aliases" : [ "CVE-2026-68139" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Use sender devcom for MPV master-up\n\nAfter PCIe DPC recovery, mlx5 reloads the affected functions and\nreplays multiport affiliation events. In the reported failure, the\nfirst relevant device error was:\n\n  pcieport 0000:10:01.1: DPC: containment event\n  pcieport 0000:10:01.1: PCIe Bus Error: severity=Uncorrected (Fatal)\n  pcieport 0000:10:01.1:    [ 5] SDES                   (First)\n\nmlx5 recovered the PCI functions and resumed 0000:11:00.1. During\nthat resume, RDMA multiport binding replayed\nMLX5_DRIVER_EVENT_AFFILIATION_DONE and mlx5e sent\nMPV_DEVCOM_MASTER_UP. The host then panicked with:\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000010\n  RIP: mlx5_devcom_comp_set_ready+0x5/0x40 [mlx5_core]\n  RDI: 0000000000000000\n\nCall trace included:\n\n  mlx5_devcom_comp_set_ready\n  mlx5e_devcom_event_mpv\n  mlx5_devcom_send_event\n  mlx5_ib_bind_slave_port\n  mlx5r_mp_probe\n  mlx5_pci_resume\n\nMPV devcom registration publishes mlx5e private data to the component\npeer list before mlx5e_devcom_init_mpv() stores the returned component\ndevice in priv->devcom. A concurrent master-up event can therefore\nreach a peer whose private data is visible but whose priv->devcom\nbackpointer is still NULL.\n\nMPV_DEVCOM_MASTER_UP already carries the sender/master mlx5e private\ndata as event_data. The ready bit is stored on the shared devcom\ncomponent, not on an individual peer. Use the sender devcom when\nmarking the MPV component ready.\n\nThis preserves the readiness transition while avoiding a NULL\ndereference of the peer devcom pointer during affiliation replay after\nPCI error recovery.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-68139"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/40f9a124ebbe0d60fe165fb3f87515c35b2d72f5"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a60c81f168c9fe4f5d84302d1e32b717f5a8a933"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c698b2735613f1f35c55688bd2252f75f31c49ad"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e32649b4bad90a6216d8e93cd7dd050af8ac9740"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-08-10T13:19:59Z"
  }
}