{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-39805 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-39805 is a medium-severity vulnerability in Linux kernel, published on 16 Sep 2025. 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-39805 and fix it if it is affected.\n\nWhat it is: CVE-2025-39805 is a medium-severity vulnerability in Linux kernel, published on 16 Sep 2025. 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-39805 in the wild and no public exploit code.\n\nAffected product: Linux kernel. 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-39805/ (Markdown: https://insights.sbomify.com/CVE-2025-39805/index.md)","id":"CVE-2025-39805","markdown":"https://insights.sbomify.com/CVE-2025-39805/index.md","name":"CVE-2025-39805","record":{"aliases":["AZL-67404","BELL-CVE-2025-39805","DEBIAN-CVE-2025-39805","GHSA-7fr9-7jpw-v2gm","ROOT-OS-DEBIAN-12-CVE-2025-39805","ROOT-OS-DEBIAN-13-CVE-2025-39805","ROOT-OS-UBUNTU-2404-CVE-2025-39805","UBUNTU-CVE-2025-39805"],"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":"low_privilege","summary":"A kernel warning and potential crash occur when removing a macb network device due to incorrect cleanup order, requiring a patch to fix.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet: macb: fix unregister_netdev call order in macb_remove()\n\nWhen removing a macb device, the driver calls phy_exit() before\nunregister_netdev(). This leads to a WARN from kernfs:\n\n  ------------[ cut here ]------------\n  kernfs: can not remove 'attached_dev', no directory\n  WARNING: CPU: 1 PID: 27146 at fs/kernfs/dir.c:1683\n  Call trace:\n    kernfs_remove_by_name_ns+0xd8/0xf0\n    sysfs_remove_link+0x24/0x58\n    phy_detach+0x5c/0x168\n    phy_disconnect+0x4c/0x70\n    phylink_disconnect_phy+0x6c/0xc0 [phylink]\n    macb_close+0x6c/0x170 [macb]\n    ...\n    macb_remove+0x60/0x168 [macb]\n    platform_remove+0x5c/0x80\n    ...\n\nThe warning happens because the PHY is being exited while the netdev\nis still registered. The correct order is to unregister the netdev\nbefore shutting down the PHY and cleaning up the MDIO bus.\n\nFix this by moving unregister_netdev() ahead of phy_exit() in\nmacb_remove().","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: macb: fix unregister_netdev call order in macb_remove()","id":"CVE-2025-39805","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"HID: multitouch: fix slab out-of-bounds access in mt_report_fixup()","id":"CVE-2025-39806"},"packages":[],"prev":{"headline":"lib/crypto: arm64/poly1305: Fix register corruption in no-SIMD contexts","id":"CVE-2025-39804"},"products":["Linux"],"published":"2025-09-16","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A kernel warning and potential crash occur when removing a macb network device due to incorrect cleanup order, requiring a patch to fix.","url":"https://insights.sbomify.com/CVE-2025-39805/"}