CVE-2025-22105

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-04-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
Trending — 4 sources updated this week
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:

bonding: check xdp prog when set bond mode

Following operations can trigger a warning[1]:

ip netns add ns1 ip netns exec ns1 ip link add bond0 type bond mode balance-rr ip netns exec ns1 ip link set dev bond0 xdp obj af_xdp_kern.o sec xdp ip netns exec ns1 ip link set bond0 type bond mode broadcast ip netns del ns1

When delete the namespace, dev_xdp_uninstall() is called to remove xdp program on bond dev, and bond_xdp_set() will check the bond mode. If bond mode is changed after attaching xdp program, the warning may occur.

Some bond modes (broadcast, etc.) do not support native xdp. Set bond mode with xdp program attached is not good. Add check for xdp program when set bond mode.

[1] ------------[ cut here ]------------ WARNING: CPU: 0 PID: 11 at net/core/dev.c:9912 unregister_netdevice_many_notify+0x8d9/0x930 Modules linked in: CPU: 0 UID: 0 PID: 11 Comm: kworker/u4:0 Not tainted 6.14.0-rc4 #107 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.15.0-0-g2dd4b9b3f840-prebuilt.qemu.org 04/01/2014 Workqueue: netns cleanup_net RIP: 0010:unregister_netdevice_many_notify+0x8d9/0x930 Code: 00 00 48 c7 c6 6f e3 a2 82 48 c7 c7 d0 b3 96 82 e8 9c 10 3e ... RSP: 0018:ffffc90000063d80 EFLAGS: 00000282 RAX: 00000000ffffffa1 RBX: ffff888004959000 RCX: 00000000ffffdfff RDX: 0000000000000000 RSI: 00000000ffffffea RDI: ffffc90000063b48 RBP: ffffc90000063e28 R08: ffffffff82d39b28 R09: 0000000000009ffb R10: 0000000000000175 R11: ffffffff82d09b40 R12: ffff8880049598e8 R13: 0000000000000001 R14: dead000000000100 R15: ffffc90000045000 FS: 0000000000000000(0000) GS:ffff888007a00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000000d406b60 CR3: 000000000483e000 CR4: 00000000000006f0 Call Trace: ? __warn+0x83/0x130 ? unregister_netdevice_many_notify+0x8d9/0x930 ? report_bug+0x18e/0x1a0 ? handle_bug+0x54/0x90 ? exc_invalid_op+0x18/0x70 ? asm_exc_invalid_op+0x1a/0x20 ? unregister_netdevice_many_notify+0x8d9/0x930 ? bond_net_exit_batch_rtnl+0x5c/0x90 cleanup_net+0x237/0x3d0 process_one_work+0x163/0x390 worker_thread+0x293/0x3b0 ? __pfx_worker_thread+0x10/0x10 kthread+0xec/0x1e0 ? __pfx_kthread+0x10/0x10 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x2f/0x50 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 ---[ end trace 0000000000000000 ]---

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 intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
The EG Score, 5.5 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
9th
KEV
Not listed

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 (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

April 16, 2025

Last Modified

October 15, 2026

Advisory Details (6)

Auto-updated Oct 15, 2026
Patch available.
Web page

SSA-784472

https://cert-portal.siemens.com/productcert/html/ssa-784472.html
Web page

bonding: check xdp prog when set bond mode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/094ee6017ea09c11d6af187935a949df32803ce0
Web page

bonding: check xdp prog when set bond mode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0dd4fac43bdea23cfe4bb2a3eabb76d752ac32fb
Web page

bonding: check xdp prog when set bond mode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6f3af8055ee7ab69d1451f056fcd890df99c167e
Web page

bonding: check xdp prog when set bond mode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5106da73b01668a1aa5d0f352b95d2b832b5caa7
Web page

bonding: check xdp prog when set bond mode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/074de2f6706ea840bbf06599cdc194086fbae092

Vendor Advisories for CVE-2025-22105(4)

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

Patch Availability(16)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-22.22) @ plucky2026-05-30ubuntu
ubuntulinux-tools-azure (6.14.0-1007.7) @ plucky2026-05-30ubuntu
ubuntulinux-tools-oracle-64k (6.14.0-1007.7) @ plucky2026-05-30ubuntu
ubuntulinux-virtual-6.8 (6.8.0-106.106) @ noble2026-05-30ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1052.55+fips1) @ noble2026-05-30ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1049.52~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1045.46) @ noble2026-05-30ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1050.53~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1051.57) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2040.41) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1052.58+fips1) @ noble2026-05-30ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-05-30ubuntu
redhatkernel-0:5.14.0-687.5.1.el9_82026-05-19redhat
redhatkernel-0:6.12.0-124.8.1.el10_12025-11-11redhat
linuxKernel @ 6.1.175 (fixes >=5.15.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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)
  • every version up to 6.1.176-1~deb11u1: fixed in 6.1.176-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)
  • every version up to 6.1.176-1: fixed in 6.1.176-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.57-1~bpo12+1 (6 versions)
  • every version up to 6.12.57-1: fixed in 6.12.57-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.16~rc7-1~exp1 (62 versions)
  • every version up to 6.16.3-1: fixed in 6.16.3-1
—

Additional Vendor Advisories

(13)

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 16× in last 7d / 35× 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 93 of 174 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. 7 repeat rows among the latest 100 are merged into the row they repeat. The 81 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2025-22105?
CVE-2025-22105 is a medium-severity vulnerability; its CVE record was published on April 16, 2025. In the Linux kernel, the following vulnerability has been resolved: bonding: check xdp prog when set bond mode Following operations can trigger a warning[1]: ip netns add ns1 ip netns exec ns1 ip link add bond0 type bond mode balance-rr ip netns exec ns1 ip link set dev bond0 xdp obj afxdpkern.o…
When was the CVE record for CVE-2025-22105 published?
The CVE record for CVE-2025-22105 was published on April 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 15, 2026; the record at its source may have been updated since.
Is CVE-2025-22105 actively exploited?
CVE-2025-22105 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-22105?
CVE-2025-22105 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-22105?
A fix for CVE-2025-22105 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-22105 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-22105

Explore →

Is Your Infrastructure Affected by CVE-2025-22105?

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

Book a Demo →Browse All CVEs