CVE-2025-21875

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-03-27. 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-8488 (ENISA EUVD) · GHSA-8p7r-x8qv-vv63 (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: always handle address removal under msk socket lock

Syzkaller reported a lockdep splat in the PM control path:

WARNING: CPU: 0 PID: 6693 at ./include/net/sock.h:1711 sock_owned_by_me include/net/sock.h:1711 [inline] WARNING: CPU: 0 PID: 6693 at ./include/net/sock.h:1711 msk_owned_by_me net/mptcp/protocol.h:363 [inline] WARNING: CPU: 0 PID: 6693 at ./include/net/sock.h:1711 mptcp_pm_nl_addr_send_ack+0x57c/0x610 net/mptcp/pm_netlink.c:788 Modules linked in: CPU: 0 UID: 0 PID: 6693 Comm: syz.0.205 Not tainted 6.14.0-rc2-syzkaller-00303-gad1b832bf1cf #0 Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024 RIP: 0010:sock_owned_by_me include/net/sock.h:1711 [inline] RIP: 0010:msk_owned_by_me net/mptcp/protocol.h:363 [inline] RIP: 0010:mptcp_pm_nl_addr_send_ack+0x57c/0x610 net/mptcp/pm_netlink.c:788 Code: 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc e8 ca 7b d3 f5 eb b9 e8 c3 7b d3 f5 90 0f 0b 90 e9 dd fb ff ff e8 b5 7b d3 f5 90 <0f> 0b 90 e9 3e fb ff ff 44 89 f1 80 e1 07 38 c1 0f 8c eb fb ff ff RSP: 0000:ffffc900034f6f60 EFLAGS: 00010283 RAX: ffffffff8bee3c2b RBX: 0000000000000001 RCX: 0000000000080000 RDX: ffffc90004d42000 RSI: 000000000000a407 RDI: 000000000000a408 RBP: ffffc900034f7030 R08: ffffffff8bee37f6 R09: 0100000000000000 R10: dffffc0000000000 R11: ffffed100bcc62e4 R12: ffff88805e6316e0 R13: ffff88805e630c00 R14: dffffc0000000000 R15: ffff88805e630c00 FS: 00007f7e9a7e96c0(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000001b2fd18ff8 CR3: 0000000032c24000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: mptcp_pm_remove_addr+0x103/0x1d0 net/mptcp/pm.c:59 mptcp_pm_remove_anno_addr+0x1f4/0x2f0 net/mptcp/pm_netlink.c:1486 mptcp_nl_remove_subflow_and_signal_addr net/mptcp/pm_netlink.c:1518 [inline] mptcp_pm_nl_del_addr_doit+0x118d/0x1af0 net/mptcp/pm_netlink.c:1629 genl_family_rcv_msg_doit net/netlink/genetlink.c:1115 [inline] genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline] genl_rcv_msg+0xb1f/0xec0 net/netlink/genetlink.c:1210 netlink_rcv_skb+0x206/0x480 net/netlink/af_netlink.c:2543 genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219 netlink_unicast_kernel net/netlink/af_netlink.c:1322 [inline] netlink_unicast+0x7f6/0x990 net/netlink/af_netlink.c:1348 netlink_sendmsg+0x8de/0xcb0 net/netlink/af_netlink.c:1892 sock_sendmsg_nosec net/socket.c:718 [inline] __sock_sendmsg+0x221/0x270 net/socket.c:733 ____sys_sendmsg+0x53a/0x860 net/socket.c:2573 ___sys_sendmsg net/socket.c:2627 [inline] __sys_sendmsg+0x269/0x350 net/socket.c:2659 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f7e9998cde9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f7e9a7e9038 EFLAGS: 00000246 ORIG_RAX: 000000000000002e RAX: ffffffffffffffda RBX: 00007f7e99ba5fa0 RCX: 00007f7e9998cde9 RDX: 000000002000c094 RSI: 0000400000000000 RDI: 0000000000000007 RBP: 00007f7e99a0e2a0 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 0000000000000000 R14: 00007f7e99ba5fa0 R15: 00007fff49231088

Indeed the PM can try to send a RM_ADDR over a msk without acquiring first the msk socket lock.

The bugged code-path comes from an early optimization: when there are no subflows, the PM should (usually) not send RM_ADDR notifications.

The above statement is incorrect, as without locks another process could concur ---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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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
13th
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 (model v2026.06.15, score date 2026-10-25). 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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

March 27, 2025

Last Modified

October 15, 2026

Advisory Details (10)

Auto-updated Jul 17, 2026
Patch available.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4193-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4178-1] linux security update

https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html
Web page

mptcp: always handle address removal under msk socket lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f865c24bc55158313d5779fc81116023a6940ca3
Web page

mptcp: always handle address removal under msk socket lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a05da2be18aae7e82572f8d795f41bb49f5dfc7d
Web page

mptcp: always handle address removal under msk socket lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8116fb4acd5d3f06cd37f84887dbe962b6703b1c
Web page

mptcp: always handle address removal under msk socket lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7cca31035c05819643ffb5d7518e9a331b3f6651
Web page

mptcp: always handle address removal under msk socket lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/494ec285535632732eaa5786297a9ae4f731b5ff
Web page

mptcp: always handle address removal under msk socket lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4124b782ec2b1e2e490cf0bbf10f53dfd3479890
Web page

mptcp: always handle address removal under msk socket lock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2c3de6dff4373f1036e003f49a32629359530bdb

Vendor Advisories for CVE-2025-21875(1)

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

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oracle-edge (5.15.0.1081.87~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-26.26) @ oracular2026-10-15ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1039.42.1) @ noble2026-10-15ubuntu
ubuntulinux-tools-lowlatency-hwe-24.04-edge (6.11.0-1014.15~24.04.1) @ noble2026-10-15ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.142.152~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-virtual-6.8 (6.8.0-84.84) @ noble2026-10-15ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-85.85~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1083.92~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-fips (5.15.0.140.80) @ jammy2026-10-15ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1078.76) @ jammy2026-10-15ubuntu
ubuntulinux-tools-gcp-lts-22.04 (5.15.0.1083.79) @ jammy2026-10-15ubuntu
ubuntulinux-tools-gcp-fips (5.15.0.1083.73) @ jammy2026-10-15ubuntu
ubuntulinux-tools-aws (6.11.0-1014.15) @ oracular2026-10-15ubuntu
ubuntulinux-tools-gke-5.15 (5.15.0.1081.80) @ jammy2026-10-15ubuntu
ubuntulinux-tools-azure-fips (5.15.0.1089.74) @ jammy2026-10-15ubuntu
ubuntulinux-tools-aws-fips (5.15.0.1084.80) @ jammy2026-10-15ubuntu
ubuntulinux-tools-nvidia-tegra-rt (5.15.0.1037.37) @ jammy2026-10-15ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1050.54) @ jammy2026-10-15ubuntu
ubuntulinux-tools-realtime (5.15.0.1084.88) @ jammy2026-10-15ubuntu
ubuntulinux-tools-aws-edge (5.15.0.1084.91~20.04.1) @ focal2026-10-15ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1040.42~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1034.35~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-84.84~22.04.1) @ jammy2026-10-15ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1034.35) @ noble2026-10-15ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1039.43) @ noble2026-10-15ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1037.37) @ noble2026-10-15ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2031.32) @ noble2026-10-15ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1038.44) @ noble2026-10-15ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1037.38) @ noble2026-10-15ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1037.38~22.04.1) @ jammy2026-10-15ubuntu
linuxKernel @ 5.10.235 (fixes >=5.10.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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (45 versions)
  • every version up to 5.10.237-1: fixed in 5.10.237-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.129-1~deb11u1 (7 versions)
  • every version up to 6.1.137-1~deb11u1: fixed in 6.1.137-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (36 versions)
  • every version up to 6.1.133-1: fixed in 6.1.133-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.19-1: fixed in 6.12.19-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.19-1: fixed in 6.12.19-1
—

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 43× 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 209 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 113 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-21875?
CVE-2025-21875 is a medium-severity vulnerability; its CVE record was published on March 27, 2025. In the Linux kernel, the following vulnerability has been resolved: mptcp: always handle address removal under msk socket lock Syzkaller reported a lockdep splat in the PM control path: WARNING: CPU: 0 PID: 6693 at ./include/net/sock.h:1711 sock_owned_by_me include/net/sock.h:1711 [inline] WARNING:…
When was the CVE record for CVE-2025-21875 published?
The CVE record for CVE-2025-21875 was published on March 27, 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 15, 2026; the record at its source may have been updated since.
Is CVE-2025-21875 actively exploited?
CVE-2025-21875 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-21875?
CVE-2025-21875 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-21875?
A fix for CVE-2025-21875 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-21875 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-21875

Explore →

Is Your Infrastructure Affected by CVE-2025-21875?

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