{"id":"CVE-2026-68139","title":"net/mlx5e: Use sender devcom for MPV master-up","summary":"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 f…","severity":"none","vendor":"Linux","product":"Linux","affected":["Linux >= bf11485f8419f90ffaa3804fd01d8468fcc56e23 < c698b2735613f1f35c55688bd2252f75f31c49ad","Linux >= bf11485f8419f90ffaa3804fd01d8468fcc56e23 < 40f9a124ebbe0d60fe165fb3f87515c35b2d72f5","Linux >= bf11485f8419f90ffaa3804fd01d8468fcc56e23 < a60c81f168c9fe4f5d84302d1e32b717f5a8a933","Linux >= bf11485f8419f90ffaa3804fd01d8468fcc56e23 < e32649b4bad90a6216d8e93cd7dd050af8ac9740","Linux 6.7"],"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial","timestamp":"2026-11-06T16:43:05.137760Z"},"published":"2026-08-10","updated":"2026-11-06","sourceUpdated":"2026-11-06T16:44:59.480Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-68139","references":[{"url":"https://git.kernel.org/stable/c/c698b2735613f1f35c55688bd2252f75f31c49ad"},{"url":"https://git.kernel.org/stable/c/40f9a124ebbe0d60fe165fb3f87515c35b2d72f5"},{"url":"https://git.kernel.org/stable/c/a60c81f168c9fe4f5d84302d1e32b717f5a8a933"},{"url":"https://git.kernel.org/stable/c/e32649b4bad90a6216d8e93cd7dd050af8ac9740"}],"tags":["cve.org"],"epss":0.00175,"epssPercentile":0.07069,"ingestedAt":"2026-11-06T16:57:43.142Z","slug":"CVE-2026-68139","body":"## Overview\n\nIn 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.\n\n## Affected\n\n- `Linux >= bf11485f8419f90ffaa3804fd01d8468fcc56e23 < c698b2735613f1f35c55688bd2252f75f31c49ad`\n- `Linux >= bf11485f8419f90ffaa3804fd01d8468fcc56e23 < 40f9a124ebbe0d60fe165fb3f87515c35b2d72f5`\n- `Linux >= bf11485f8419f90ffaa3804fd01d8468fcc56e23 < a60c81f168c9fe4f5d84302d1e32b717f5a8a933`\n- `Linux >= bf11485f8419f90ffaa3804fd01d8468fcc56e23 < e32649b4bad90a6216d8e93cd7dd050af8ac9740`\n- `Linux 6.7`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":3,"depthScoreParts":{"impact":2.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}