{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-39831 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-39831 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-39831 and fix it if it is affected.\n\nWhat it is: CVE-2025-39831 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-39831 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-39831/ (Markdown: https://insights.sbomify.com/CVE-2025-39831/index.md)","id":"CVE-2025-39831","markdown":"https://insights.sbomify.com/CVE-2025-39831/index.md","name":"CVE-2025-39831","record":{"aliases":["BELL-CVE-2025-39831","DEBIAN-CVE-2025-39831","GHSA-7j9w-q7j7-gqpq","ROOT-OS-DEBIAN-13-CVE-2025-39831","UBUNTU-CVE-2025-39831"],"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 locking assertion failure in the fbnic network driver during power management resume can cause a kernel warning or potential denial of service.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":5.5,"severity":"medium","source":"cisa-adp","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\nfbnic: Move phylink resume out of service_task and into open/close\n\nThe fbnic driver was presenting with the following locking assert coming\nout of a PM resume:\n[   42.208116][  T164] RTNL: assertion failed at drivers/net/phy/phylink.c (2611)\n[   42.208492][  T164] WARNING: CPU: 1 PID: 164 at drivers/net/phy/phylink.c:2611 phylink_resume+0x190/0x1e0\n[   42.208872][  T164] Modules linked in:\n[   42.209140][  T164] CPU: 1 UID: 0 PID: 164 Comm: bash Not tainted 6.17.0-rc2-virtme #134 PREEMPT(full)\n[   42.209496][  T164] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014\n[   42.209861][  T164] RIP: 0010:phylink_resume+0x190/0x1e0\n[   42.210057][  T164] Code: 83 e5 01 0f 85 b0 fe ff ff c6 05 1c cd 3e 02 01 90 ba 33 0a 00 00 48 c7 c6 20 3a 1d a5 48 c7 c7 e0 3e 1d a5 e8 21 b8 90 fe 90 \u003c0f\u003e 0b 90 90 e9 86 fe ff ff e8 42 ea 1f ff e9 e2 fe ff ff 48 89 ef\n[   42.210708][  T164] RSP: 0018:ffffc90000affbd8 EFLAGS: 00010296\n[   42.210983][  T164] RAX: 0000000000000000 RBX: ffff8880078d8400 RCX: 0000000000000000\n[   42.211235][  T164] RDX: 0000000000000000 RSI: 1ffffffff4f10938 RDI: 0000000000000001\n[   42.211466][  T164] RBP: 0000000000000000 R08: ffffffffa2ae79ea R09: fffffbfff4b3eb84\n[   42.211707][  T164] R10: 0000000000000003 R11: 0000000000000000 R12: ffff888007ad8000\n[   42.211997][  T164] R13: 0000000000000002 R14: ffff888006a18800 R15: ffffffffa34c59e0\n[   42.212234][  T164] FS:  00007f0dc8e39740(0000) GS:ffff88808f51f000(0000) knlGS:0000000000000000\n[   42.212505][  T164] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[   42.212704][  T164] CR2: 00007f0dc8e9fe10 CR3: 000000000b56d003 CR4: 0000000000772ef0\n[   42.213227][  T164] PKRU: 55555554\n[   42.213366][  T164] Call Trace:\n[   42.213483][  T164]  \u003cTASK\u003e\n[   42.213565][  T164]  __fbnic_pm_attach.isra.0+0x8e/0xa0\n[   42.213725][  T164]  pci_reset_function+0x116/0x1d0\n[   42.213895][  T164]  reset_store+0xa0/0x100\n[   42.214025][  T164]  ? pci_dev_reset_attr_is_visible+0x50/0x50\n[   42.214221][  T164]  ? sysfs_file_kobj+0xc1/0x1e0\n[   42.214374][  T164]  ? sysfs_kf_write+0x65/0x160\n[   42.214526][  T164]  kernfs_fop_write_iter+0x2f8/0x4c0\n[   42.214677][  T164]  ? kernfs_vma_page_mkwrite+0x1f0/0x1f0\n[   42.214836][  T164]  new_sync_write+0x308/0x6f0\n[   42.214987][  T164]  ? __lock_acquire+0x34c/0x740\n[   42.215135][  T164]  ? new_sync_read+0x6f0/0x6f0\n[   42.215288][  T164]  ? lock_acquire.part.0+0xbc/0x260\n[   42.215440][  T164]  ? ksys_write+0xff/0x200\n[   42.215590][  T164]  ? perf_trace_sched_switch+0x6d0/0x6d0\n[   42.215742][  T164]  vfs_write+0x65e/0xbb0\n[   42.215876][  T164]  ksys_write+0xff/0x200\n[   42.215994][  T164]  ? __ia32_sys_read+0xc0/0xc0\n[   42.216141][  T164]  ? do_user_addr_fault+0x269/0x9f0\n[   42.216292][  T164]  ? rcu_is_watching+0x15/0xd0\n[   42.216442][  T164]  do_syscall_64+0xbb/0x360\n[   42.216591][  T164]  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n[   42.216784][  T164] RIP: 0033:0x7f0dc8ea9986\n\nA bit of digging showed that we were invoking the phylink_resume as a part\nof the fbnic_up path when we were enabling the service task while not\nholding the RTNL lock. We should be enabling this sooner as a part of the\nndo_open path and then just letting the service task come online later.\nThis will help to enforce the correct locking and brings the phylink\ninterface online at the same time as the network interface, instead of at a\nlater time.\n\nI tested this on QEMU to verify this was working by putting the system to\nsleep using \"echo mem \u003e /sys/power/state\" to put the system to sleep in the\nguest and then using the command \"system_wakeup\" in the QEMU monitor.","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":"fbnic: Move phylink resume out of service_task and into open/close","id":"CVE-2025-39831","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"race_condition","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"net/mlx5: Fix lockdep assertion on sync reset unload event","id":"CVE-2025-39832"},"packages":[],"prev":{"headline":"net/mlx5: HWS, Fix memory leak in hws_pool_buddy_init error path","id":"CVE-2025-39830"},"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A locking assertion failure in the fbnic network driver during power management resume can cause a kernel warning or potential denial of service.","url":"https://insights.sbomify.com/CVE-2025-39831/"}