{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68139 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68139 is a vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-68139 and fix it if it is affected.\n\nWhat it is: CVE-2026-68139 is a vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-68139 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-68139/ (Markdown: https://insights.sbomify.com/CVE-2026-68139/index.md)","id":"CVE-2026-68139","markdown":"https://insights.sbomify.com/CVE-2026-68139/index.md","name":"CVE-2026-68139","record":{"aliases":["BELL-CVE-2026-68139","DEBIAN-CVE-2026-68139","GHSA-6jxm-mj96-cq7j","UBUNTU-CVE-2026-68139"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A race condition in the mlx5 driver causes a kernel NULL pointer dereference and system crash during PCIe error recovery.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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-\u003edevcom. A concurrent master-up event can therefore\nreach a peer whose private data is visible but whose priv-\u003edevcom\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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"net/mlx5e: Use sender devcom for MPV master-up","id":"CVE-2026-68139","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"net/iucv: fix use-after-free of a severed iucv_path","id":"CVE-2026-68140"},"packages":[],"prev":{"headline":"net/sched: serialize qdisc_rtab_list against concurrent get/put","id":"CVE-2026-68138"},"products":["Linux"],"published":"2026-08-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A race condition in the mlx5 driver causes a kernel NULL pointer dereference and system crash during PCIe error recovery.","url":"https://insights.sbomify.com/CVE-2026-68139/"}