CVE-2025-21642

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-01-19. 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-2591 (ENISA EUVD) · GHSA-2g8f-3mwg-x245 (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.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

mptcp: sysctl: sched: avoid using current->nsproxy

Using the 'net' structure via 'current' is not recommended for different reasons.

First, if the goal is to use it to read or write per-netns data, this is inconsistent with how the "generic" sysctl entries are doing: directly by only using pointers set to the table entry, e.g. table->data. Linked to that, the per-netns data should always be obtained from the table linked to the netns it had been created for, which may not coincide with the reader's or writer's netns.

Another reason is that access to current->nsproxy->netns can oops if attempted when current->nsproxy had been dropped when the current task is exiting. This is what syzbot found, when using acct(2):

Oops: general protection fault, probably for non-canonical address 0xdffffc0000000005: 0000 [#1] PREEMPT SMP KASAN PTI KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f] CPU: 1 UID: 0 PID: 5924 Comm: syz-executor Not tainted 6.13.0-rc5-syzkaller-00004-gccb98ccef0e5 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 RIP: 0010:proc_scheduler+0xc6/0x3c0 net/mptcp/ctrl.c:125 Code: 03 42 80 3c 38 00 0f 85 fe 02 00 00 4d 8b a4 24 08 09 00 00 48 b8 00 00 00 00 00 fc ff df 49 8d 7c 24 28 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 cc 02 00 00 4d 8b 7c 24 28 48 8d 84 24 c8 00 00 RSP: 0018:ffffc900034774e8 EFLAGS: 00010206

RAX: dffffc0000000000 RBX: 1ffff9200068ee9e RCX: ffffc90003477620 RDX: 0000000000000005 RSI: ffffffff8b08f91e RDI: 0000000000000028 RBP: 0000000000000001 R08: ffffc90003477710 R09: 0000000000000040 R10: 0000000000000040 R11: 00000000726f7475 R12: 0000000000000000 R13: ffffc90003477620 R14: ffffc90003477710 R15: dffffc0000000000 FS: 0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fee3cd452d8 CR3: 000000007d116000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: proc_sys_call_handler+0x403/0x5d0 fs/proc/proc_sysctl.c:601 __kernel_write_iter+0x318/0xa80 fs/read_write.c:612 __kernel_write+0xf6/0x140 fs/read_write.c:632 do_acct_process+0xcb0/0x14a0 kernel/acct.c:539 acct_pin_kill+0x2d/0x100 kernel/acct.c:192 pin_kill+0x194/0x7c0 fs/fs_pin.c:44 mnt_pin_kill+0x61/0x1e0 fs/fs_pin.c:81 cleanup_mnt+0x3ac/0x450 fs/namespace.c:1366 task_work_run+0x14e/0x250 kernel/task_work.c:239 exit_task_work include/linux/task_work.h:43 [inline] do_exit+0xad8/0x2d70 kernel/exit.c:938 do_group_exit+0xd3/0x2a0 kernel/exit.c:1087 get_signal+0x2576/0x2610 kernel/signal.c:3017 arch_do_signal_or_restart+0x90/0x7e0 arch/x86/kernel/signal.c:337 exit_to_user_mode_loop kernel/entry/common.c:111 [inline] exit_to_user_mode_prepare include/linux/entry-common.h:329 [inline] __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline] syscall_exit_to_user_mode+0x150/0x2a0 kernel/entry/common.c:218 do_syscall_64+0xda/0x250 arch/x86/entry/common.c:89 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fee3cb87a6a Code: Unable to access opcode bytes at 0x7fee3cb87a40. RSP: 002b:00007fffcccac688 EFLAGS: 00000202 ORIG_RAX: 0000000000000037 RAX: 0000000000000000 RBX: 00007fffcccac710 RCX: 00007fee3cb87a6a RDX: 0000000000000041 RSI: 0000000000000000 RDI: 0000000000000003 RBP: 0000000000000003 R08: 00007fffcccac6ac R09: 00007fffcccacac7 R10: 00007fffcccac710 R11: 0000000000000202 R12: 00007fee3cd49500 R13: 00007fffcccac6ac R14: 0000000000000000 R15: 00007fee3cd4b000 Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010:proc_scheduler+0xc6/0x3c0 net/mptcp/ctrl.c:125 Code: 03 42 80 3c 38 00 0f 85 fe 02 00 00 4d 8b a4 24 08 09 00 00 48 b8 00 00 00 00 00 fc ---truncated---

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.2% × 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.2%
EPSS %ILE
16th
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.2% within 30 daysSource: FIRST EPSS. 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

January 19, 2025

Last Modified

October 1, 2025

References (3)

Vendor Advisories for CVE-2025-21642(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(17)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-21.21) @ oracular2026-10-24ubuntu
ubuntulinux-tools-lowlatency-hwe-24.04-edge (6.11.0-1011.12~24.04.1) @ noble2026-10-24ubuntu
ubuntulinux-tools-lowlatency-64k (6.11.0-1011.12) @ oracular2026-10-24ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1017.17) @ noble2026-10-24ubuntu
ubuntulinux-tools-raspi (6.11.0-1010.10) @ oracular2026-10-24ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1012.14) @ noble2026-10-24ubuntu
ubuntulinux-tools-raspi-realtime (6.8.0-2023.24) @ noble2026-10-24ubuntu
ubuntulinux-tools-gke (6.8.0-1025.29) @ noble2026-10-24ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1028.28) @ noble2026-10-24ubuntu
ubuntulinux-tools-raspi (6.8.0-1028.32) @ noble2026-10-24ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-60.63~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1026.27~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1016.17) @ noble2026-10-24ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1028.31.1) @ noble2026-10-24ubuntu
ubuntulinux-tools-realtime (6.8.1-1022.23) @ noble2026-10-24ubuntu
ubuntulinux-virtual (6.8.0-60.63) @ noble2026-10-24ubuntu
linuxKernel @ 6.6.72 (fixes >=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
linux—
  • every version up to 6.12.10-1: fixed in 6.12.10-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.10-1: fixed in 6.12.10-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(16)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 39× 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 96 of 199 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 103 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-21642?
CVE-2025-21642 is a medium-severity vulnerability; its CVE record was published on January 19, 2025. In the Linux kernel, the following vulnerability has been resolved: mptcp: sysctl: sched: avoid using current->nsproxy Using the 'net' structure via 'current' is not recommended for different reasons. First, if the goal is to use it to read or write per-netns data, this is inconsistent with how the…
When was the CVE record for CVE-2025-21642 published?
The CVE record for CVE-2025-21642 was published on January 19, 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 1, 2025; the record at its source may have been updated since.
Is CVE-2025-21642 actively exploited?
CVE-2025-21642 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-21642?
CVE-2025-21642 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-21642?
A fix for CVE-2025-21642 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-21642 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2025-21642?

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

Book a Demo →Browse All CVEs