{"id":"CVE-2026-68139","summary":"net/mlx5e: Use sender devcom for MPV master-up","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-\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.","modified":"2026-08-18T03:31:01.450039766Z","published":"2026-08-10T11:59:02.768Z","database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/68xxx/CVE-2026-68139.json"},"references":[{"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"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/68xxx/CVE-2026-68139.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68139"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"bf11485f8419f90ffaa3804fd01d8468fcc56e23"},{"fixed":"c698b2735613f1f35c55688bd2252f75f31c49ad"},{"fixed":"40f9a124ebbe0d60fe165fb3f87515c35b2d72f5"},{"fixed":"a60c81f168c9fe4f5d84302d1e32b717f5a8a933"},{"fixed":"e32649b4bad90a6216d8e93cd7dd050af8ac9740"}]}],"database_specific":{"source":"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-68139.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.101"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.42"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"7.1.6"}]}],"database_specific":{"source":"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-68139.json"}}],"schema_version":"1.9.0"}