CVE-2025-39831

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.5 from GitHub Security Advisory published 2025-09-16. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-29583 (ENISA EUVD) · GHSA-7j9w-q7j7-gqpq (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

fbnic: Move phylink resume out of service_task and into open/close

The fbnic driver was presenting with the following locking assert coming out of a PM resume: [ 42.208116][ T164] RTNL: assertion failed at drivers/net/phy/phylink.c (2611) [ 42.208492][ T164] WARNING: CPU: 1 PID: 164 at drivers/net/phy/phylink.c:2611 phylink_resume+0x190/0x1e0 [ 42.208872][ T164] Modules linked in: [ 42.209140][ T164] CPU: 1 UID: 0 PID: 164 Comm: bash Not tainted 6.17.0-rc2-virtme #134 PREEMPT(full) [ 42.209496][ T164] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-5.fc42 04/01/2014 [ 42.209861][ T164] RIP: 0010:phylink_resume+0x190/0x1e0 [ 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 <0f> 0b 90 90 e9 86 fe ff ff e8 42 ea 1f ff e9 e2 fe ff ff 48 89 ef [ 42.210708][ T164] RSP: 0018:ffffc90000affbd8 EFLAGS: 00010296 [ 42.210983][ T164] RAX: 0000000000000000 RBX: ffff8880078d8400 RCX: 0000000000000000 [ 42.211235][ T164] RDX: 0000000000000000 RSI: 1ffffffff4f10938 RDI: 0000000000000001 [ 42.211466][ T164] RBP: 0000000000000000 R08: ffffffffa2ae79ea R09: fffffbfff4b3eb84 [ 42.211707][ T164] R10: 0000000000000003 R11: 0000000000000000 R12: ffff888007ad8000 [ 42.211997][ T164] R13: 0000000000000002 R14: ffff888006a18800 R15: ffffffffa34c59e0 [ 42.212234][ T164] FS: 00007f0dc8e39740(0000) GS:ffff88808f51f000(0000) knlGS:0000000000000000 [ 42.212505][ T164] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 42.212704][ T164] CR2: 00007f0dc8e9fe10 CR3: 000000000b56d003 CR4: 0000000000772ef0 [ 42.213227][ T164] PKRU: 55555554 [ 42.213366][ T164] Call Trace: [ 42.213483][ T164] [ 42.213565][ T164] __fbnic_pm_attach.isra.0+0x8e/0xa0 [ 42.213725][ T164] pci_reset_function+0x116/0x1d0 [ 42.213895][ T164] reset_store+0xa0/0x100 [ 42.214025][ T164] ? pci_dev_reset_attr_is_visible+0x50/0x50 [ 42.214221][ T164] ? sysfs_file_kobj+0xc1/0x1e0 [ 42.214374][ T164] ? sysfs_kf_write+0x65/0x160 [ 42.214526][ T164] kernfs_fop_write_iter+0x2f8/0x4c0 [ 42.214677][ T164] ? kernfs_vma_page_mkwrite+0x1f0/0x1f0 [ 42.214836][ T164] new_sync_write+0x308/0x6f0 [ 42.214987][ T164] ? __lock_acquire+0x34c/0x740 [ 42.215135][ T164] ? new_sync_read+0x6f0/0x6f0 [ 42.215288][ T164] ? lock_acquire.part.0+0xbc/0x260 [ 42.215440][ T164] ? ksys_write+0xff/0x200 [ 42.215590][ T164] ? perf_trace_sched_switch+0x6d0/0x6d0 [ 42.215742][ T164] vfs_write+0x65e/0xbb0 [ 42.215876][ T164] ksys_write+0xff/0x200 [ 42.215994][ T164] ? __ia32_sys_read+0xc0/0xc0 [ 42.216141][ T164] ? do_user_addr_fault+0x269/0x9f0 [ 42.216292][ T164] ? rcu_is_watching+0x15/0xd0 [ 42.216442][ T164] do_syscall_64+0xbb/0x360 [ 42.216591][ T164] entry_SYSCALL_64_after_hwframe+0x4b/0x53 [ 42.216784][ T164] RIP: 0033:0x7f0dc8ea9986

A bit of digging showed that we were invoking the phylink_resume as a part of the fbnic_up path when we were enabling the service task while not holding the RTNL lock. We should be enabling this sooner as a part of the ndo_open path and then just letting the service task come online later. This will help to enforce the correct locking and brings the phylink interface online at the same time as the network interface, instead of at a later time.

I tested this on QEMU to verify this was working by putting the system to sleep using "echo mem > /sys/power/state" to put the system to sleep in the guest and then using the command "system_wakeup" in the QEMU monitor.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 16, 2025

Last Modified

October 19, 2026

References (3)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 6.12.45 (fixes >=6.11.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1, 6.12.41-1, 6.12.43-1, 6.12.43-1~bpo12+1
  • every version up to 6.12.48-1: fixed in 6.12.48-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.16~rc7-1~exp1 (63 versions)
  • every version up to 6.16.5-1: fixed in 6.16.5-1
—

Data Freshness Timeline

(refreshed 7× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 190 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 92 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-06 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-11-05 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-11-04 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  4. 2026-11-03 16:44 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  5. 2026-11-02 16:42 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  8. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  9. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-10-28 13:55 UTCOSV refresh
  12. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-10-25 16:28 UTCEG score recompute
  16. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  19. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  20. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  21. 2026-10-19 21:47 UTCEG score recompute
  22. 2026-10-19 21:46 UTCGHSA enrichmentGHSA-7j9w-q7j7-gqpq · GitHub CVSS 5.5
  23. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  24. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  25. 2026-10-18 05:35 UTCEG score recompute
Show 73 more
  1. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-10-16 16:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  4. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  5. 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-10-12 17:06 UTCEG score recompute
  7. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  8. 2026-10-11 20:39 UTCEG score recompute
  9. 2026-10-11 18:50 UTCEG score recompute
  10. 2026-10-11 15:27 UTCEG score recompute
  11. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-10-08 17:09 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  19. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  20. 2026-10-02 04:40 UTCOSV refresh
  21. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  22. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  23. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-09-26 00:24 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  26. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  27. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  28. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  29. 2026-09-17 19:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  30. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  31. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  32. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  33. 2026-09-12 23:06 UTCOSV refresh
  34. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  35. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  36. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  37. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  38. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  39. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  40. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  41. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  42. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  43. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  44. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  45. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  46. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  47. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  48. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  49. 2026-08-25 03:26 UTCOSV refresh
  50. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  51. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  52. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  53. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  54. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  55. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  56. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  57. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  58. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  59. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  60. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  61. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  62. 2026-08-08 20:55 UTCOSV refresh
  63. 2026-08-08 16:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  64. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  65. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  66. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  67. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  68. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  69. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  70. 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  71. 2026-07-30 16:27 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  72. 2026-07-30 01:29 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  73. 2026-07-28 15:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile

Frequently asked(5)

What is CVE-2025-39831?
CVE-2025-39831 is a medium-severity vulnerability; its CVE record was published on September 16, 2025. In the Linux kernel, the following vulnerability has been resolved: fbnic: Move phylink resume out of service_task and into open/close The fbnic driver was presenting with the following locking assert coming out of a PM resume: [ 42.208116][ T164] RTNL: assertion failed at drivers/net/phy/phylink.c…
When was the CVE record for CVE-2025-39831 published?
The CVE record for CVE-2025-39831 was published on September 16, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2025-39831 actively exploited?
CVE-2025-39831 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-39831?
CVE-2025-39831 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-39831?
A fix for CVE-2025-39831 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-39831

Explore →

Is Your Infrastructure Affected by CVE-2025-39831?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs