{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-68790 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-68790 is an use after free vulnerability in Linux, published on 13 Jan 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-2025-68790 and fix it if it is affected.\n\nWhat it is: CVE-2025-68790 is an use after free vulnerability in Linux, published on 13 Jan 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-2025-68790 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-2025-68790/ (Markdown: https://insights.sbomify.com/CVE-2025-68790/index.md)","id":"CVE-2025-68790","markdown":"https://insights.sbomify.com/CVE-2025-68790/index.md","name":"CVE-2025-68790","record":{"aliases":["BELL-CVE-2025-68790","GHSA-r4v9-6rcf-whc8","UBUNTU-CVE-2025-68790"],"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 use-after-free in the Linux kernel mlx5 driver causes kernel panics during PCI error recovery, leading to denial of service.","user_interaction":"not_required","vuln_class":"use_after_free"},"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/mlx5: Fix double unregister of HCA_PORTS component\n\nClear hca_devcom_comp in device's private data after unregistering it in\nLAG teardown. Otherwise a slightly lagging second pass through\nmlx5_unload_one() might try to unregister it again and trip over\nuse-after-free.\n\nOn s390 almost all PCI level recovery events trigger two passes through\nmxl5_unload_one() - one through the poll_health() method and one through\nmlx5_pci_err_detected() as callback from generic PCI error recovery.\nWhile testing PCI error recovery paths with more kernel debug features\nenabled, this issue reproducibly led to kernel panics with the following\ncall chain:\n\n Unable to handle kernel pointer dereference in virtual kernel address space\n Failing address: 6b6b6b6b6b6b6000 TEID: 6b6b6b6b6b6b6803 ESOP-2 FSI\n Fault in home space mode while using kernel ASCE.\n AS:00000000705c4007 R3:0000000000000024\n Oops: 0038 ilc:3 [#1]SMP\n\n CPU: 14 UID: 0 PID: 156 Comm: kmcheck Kdump: loaded Not tainted\n      6.18.0-20251130.rc7.git0.16131a59cab1.300.fc43.s390x+debug #1 PREEMPT\n\n Krnl PSW : 0404e00180000000 0000020fc86aa1dc (__lock_acquire+0x5c/0x15f0)\n            R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3\n Krnl GPRS: 0000000000000000 0000020f00000001 6b6b6b6b6b6b6c33 0000000000000000\n            0000000000000000 0000000000000000 0000000000000001 0000000000000000\n            0000000000000000 0000020fca28b820 0000000000000000 0000010a1ced8100\n            0000010a1ced8100 0000020fc9775068 0000018fce14f8b8 0000018fce14f7f8\n Krnl Code: 0000020fc86aa1cc: e3b003400004        lg      %r11,832\n            0000020fc86aa1d2: a7840211           brc     8,0000020fc86aa5f4\n           *0000020fc86aa1d6: c09000df0b25       larl    %r9,0000020fca28b820\n           \u003e0000020fc86aa1dc: d50790002000       clc     0(8,%r9),0(%r2)\n            0000020fc86aa1e2: a7840209           brc     8,0000020fc86aa5f4\n            0000020fc86aa1e6: c0e001100401       larl    %r14,0000020fca8aa9e8\n            0000020fc86aa1ec: c01000e25a00       larl    %r1,0000020fca2f55ec\n            0000020fc86aa1f2: a7eb00e8           aghi    %r14,232\n\n Call Trace:\n  __lock_acquire+0x5c/0x15f0\n  lock_acquire.part.0+0xf8/0x270\n  lock_acquire+0xb0/0x1b0\n  down_write+0x5a/0x250\n  mlx5_detach_device+0x42/0x110 [mlx5_core]\n  mlx5_unload_one_devl_locked+0x50/0xc0 [mlx5_core]\n  mlx5_unload_one+0x42/0x60 [mlx5_core]\n  mlx5_pci_err_detected+0x94/0x150 [mlx5_core]\n  zpci_event_attempt_error_recovery+0xcc/0x388","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/mlx5: Fix double unregister of HCA_PORTS component","id":"CVE-2025-68790","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"fuse: missing copy_finish in fuse-over-io-uring argument copies","id":"CVE-2025-68791"},"packages":[],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2025-68789"},"products":["Linux"],"published":"2026-01-13","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-05-11","vendors":["Linux"]},"summary":"A use-after-free in the Linux kernel mlx5 driver causes kernel panics during PCI error recovery, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2025-68790/"}