CVE-2025-38525

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

rxrpc: Fix irq-disabled in local_bh_enable()

The rxrpc_assess_MTU_size() function calls down into the IP layer to find out the MTU size for a route. When accepting an incoming call, this is called from rxrpc_new_incoming_call() which holds interrupts disabled across the code that calls down to it. Unfortunately, the IP layer uses local_bh_enable() which, config dependent, throws a warning if IRQs are enabled:

WARNING: CPU: 1 PID: 5544 at kernel/softirq.c:387 __local_bh_enable_ip+0x43/0xd0 ... RIP: 0010:__local_bh_enable_ip+0x43/0xd0 ... Call Trace: rt_cache_route+0x7e/0xa0 rt_set_nexthop.isra.0+0x3b3/0x3f0 __mkroute_output+0x43a/0x460 ip_route_output_key_hash+0xf7/0x140 ip_route_output_flow+0x1b/0x90 rxrpc_assess_MTU_size.isra.0+0x2a0/0x590 rxrpc_new_incoming_peer+0x46/0x120 rxrpc_alloc_incoming_call+0x1b1/0x400 rxrpc_new_incoming_call+0x1da/0x5e0 rxrpc_input_packet+0x827/0x900 rxrpc_io_thread+0x403/0xb60 kthread+0x2f7/0x310 ret_from_fork+0x2a/0x230 ret_from_fork_asm+0x1a/0x30 ... hardirqs last enabled at (23): _raw_spin_unlock_irq+0x24/0x50 hardirqs last disabled at (24): _raw_read_lock_irq+0x17/0x70 softirqs last enabled at (0): copy_process+0xc61/0x2730 softirqs last disabled at (25): rt_add_uncached_list+0x3c/0x90

Fix this by moving the call to rxrpc_assess_MTU_size() out of rxrpc_init_peer() and further up the stack where it can be done without interrupts disabled.

It shouldn't be a problem for rxrpc_new_incoming_call() to do it after the locks are dropped as pmtud is going to be performed by the I/O thread - and we're in the I/O thread at this point.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

August 16, 2025

Last Modified

August 5, 2026

Advisory Details (2)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic

rxrpc: Fix irq-disabled in local_bh_enable() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e4d2878369d590bf8455e3678a644e503172eafa
generic

rxrpc: Fix irq-disabled in local_bh_enable() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2029f21f10dedb88c0f86abffcf8d6c21dcf6040

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-36.36) @ plucky2026-05-30ubuntu
ubuntulinux-tools-oracle-edge (6.14.0-1017.17~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-oem-6.14 (6.14.0-1016.16) @ noble2026-05-30ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.14.0-1016.16~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-raspi-6.14 (6.14.0-1018.18) @ plucky2026-05-30ubuntu
ubuntulinux-tools-azure-6.14 (6.14.0-1017.17) @ plucky2026-05-30ubuntu
linuxKernel @ 6.15.8—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.

All Vendor Advisories

(6)

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 10× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 106 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-38525?
CVE-2025-38525 is a medium vulnerability published on August 16, 2025. In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix irq-disabled in localbhenable() The rxrpcassessMTU_size() function calls down into the IP layer to find out the MTU size for a route. When accepting an incoming call, this is called from rxrpcnewincoming_call() which…
When was CVE-2025-38525 disclosed?
CVE-2025-38525 was first published in the National Vulnerability Database on August 16, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-38525 actively exploited?
CVE-2025-38525 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.4% of all scored CVEs.
What is the CVSS score of CVE-2025-38525?
CVE-2025-38525 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-38525?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-38525, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-38525

Explore →

Is Your Infrastructure Affected by CVE-2025-38525?

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

Start Free Scan →Browse All CVEs