CVE-2025-38276

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

fs/dax: Fix "don't skip locked entries when scanning entries"

Commit 6be3e21d25ca ("fs/dax: don't skip locked entries when scanning entries") introduced a new function, wait_entry_unlocked_exclusive(), which waits for the current entry to become unlocked without advancing the XArray iterator state.

Waiting for the entry to become unlocked requires dropping the XArray lock. This requires calling xas_pause() prior to dropping the lock which leaves the xas in a suitable state for the next iteration. However this has the side-effect of advancing the xas state to the next index. Normally this isn't an issue because xas_for_each() contains code to detect this state and thus avoid advancing the index a second time on the next loop iteration.

However both callers of and wait_entry_unlocked_exclusive() itself subsequently use the xas state to reload the entry. As xas_pause() updated the state to the next index this will cause the current entry which is being waited on to be skipped. This caused the following warning to fire intermittently when running xftest generic/068 on an XFS filesystem with FS DAX enabled:

[ 35.067397] ------------[ cut here ]------------ [ 35.068229] WARNING: CPU: 21 PID: 1640 at mm/truncate.c:89 truncate_folio_batch_exceptionals+0xd8/0x1e0 [ 35.069717] Modules linked in: nd_pmem dax_pmem nd_btt nd_e820 libnvdimm [ 35.071006] CPU: 21 UID: 0 PID: 1640 Comm: fstest Not tainted 6.15.0-rc7+ #77 PREEMPT(voluntary) [ 35.072613] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/204 [ 35.074845] RIP: 0010:truncate_folio_batch_exceptionals+0xd8/0x1e0 [ 35.075962] Code: a1 00 00 00 f6 47 0d 20 0f 84 97 00 00 00 4c 63 e8 41 39 c4 7f 0b eb 61 49 83 c5 01 45 39 ec 7e 58 42 f68 [ 35.079522] RSP: 0018:ffffb04e426c7850 EFLAGS: 00010202 [ 35.080359] RAX: 0000000000000000 RBX: ffff9d21e3481908 RCX: ffffb04e426c77f4 [ 35.081477] RDX: ffffb04e426c79e8 RSI: ffffb04e426c79e0 RDI: ffff9d21e34816e8 [ 35.082590] RBP: ffffb04e426c79e0 R08: 0000000000000001 R09: 0000000000000003 [ 35.083733] R10: 0000000000000000 R11: 822b53c0f7a49868 R12: 000000000000001f [ 35.084850] R13: 0000000000000000 R14: ffffb04e426c78e8 R15: fffffffffffffffe [ 35.085953] FS: 00007f9134c87740(0000) GS:ffff9d22abba0000(0000) knlGS:0000000000000000 [ 35.087346] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 35.088244] CR2: 00007f9134c86000 CR3: 000000040afff000 CR4: 00000000000006f0 [ 35.089354] Call Trace: [ 35.089749] [ 35.090168] truncate_inode_pages_range+0xfc/0x4d0 [ 35.091078] truncate_pagecache+0x47/0x60 [ 35.091735] xfs_setattr_size+0xc7/0x3e0 [ 35.092648] xfs_vn_setattr+0x1ea/0x270 [ 35.093437] notify_change+0x1f4/0x510 [ 35.094219] ? do_truncate+0x97/0xe0 [ 35.094879] do_truncate+0x97/0xe0 [ 35.095640] path_openat+0xabd/0xca0 [ 35.096278] do_filp_open+0xd7/0x190 [ 35.096860] do_sys_openat2+0x8a/0xe0 [ 35.097459] __x64_sys_openat+0x6d/0xa0 [ 35.098076] do_syscall_64+0xbb/0x1d0 [ 35.098647] entry_SYSCALL_64_after_hwframe+0x77/0x7f [ 35.099444] RIP: 0033:0x7f9134d81fc1 [ 35.100033] Code: 75 57 89 f0 25 00 00 41 00 3d 00 00 41 00 74 49 80 3d 2a 26 0e 00 00 74 6d 89 da 48 89 ee bf 9c ff ff ff5 [ 35.102993] RSP: 002b:00007ffcd41e0d10 EFLAGS: 00000202 ORIG_RAX: 0000000000000101 [ 35.104263] RAX: ffffffffffffffda RBX: 0000000000000242 RCX: 00007f9134d81fc1 [ 35.105452] RDX: 0000000000000242 RSI: 00007ffcd41e1200 RDI: 00000000ffffff9c [ 35.106663] RBP: 00007ffcd41e1200 R08: 0000000000000000 R09: 0000000000000064 [ 35.107923] R10: 00000000000001a4 R11: 0000000000000202 R12: 0000000000000066 [ 35.109112] R13: 0000000000100000 R14: 0000000000100000 R15: 0000000000000400 [ 35.110357] [ 35.110769] irq event stamp: 8415587 [ 35.111486] hardirqs last enabled at (8415599): [] __up_console_se ---truncated---

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
2%
KEV
Not listed

Published

July 10, 2025

Last Modified

August 5, 2026

Advisory Details (2)

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

fs/dax: Fix "don't skip locked entries when scanning entries" - kernel/git/stable/linux.git - Linux kernel stable tree

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

fs/dax: Fix "don't skip locked entries when scanning entries" - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/61009dd2252ab4391d44a240e891f1e04c00b9ca

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.15.3osv

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 20× 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 118 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-38276?
CVE-2025-38276 is a medium vulnerability published on July 10, 2025. In the Linux kernel, the following vulnerability has been resolved: fs/dax: Fix "don't skip locked entries when scanning entries" Commit 6be3e21d25ca ("fs/dax: don't skip locked entries when scanning entries") introduced a new function, waitentryunlocked_exclusive(), which waits for the current…
When was CVE-2025-38276 disclosed?
CVE-2025-38276 was first published in the National Vulnerability Database on July 10, 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-38276 actively exploited?
CVE-2025-38276 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 98.5% of all scored CVEs.
What is the CVSS score of CVE-2025-38276?
CVE-2025-38276 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-38276?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-38276, 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-38276

Explore →

Is Your Infrastructure Affected by CVE-2025-38276?

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