CVE-2025-38260

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-07-09. 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-20801 (ENISA EUVD) · GHSA-7r7h-hw2c-cp7q (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:

btrfs: handle csum tree error with rescue=ibadroots correctly

[BUG] There is syzbot based reproducer that can crash the kernel, with the following call trace: (With some debug output added)

DEBUG: rescue=ibadroots parsed BTRFS: device fsid 14d642db-7b15-43e4-81e6-4b8fac6a25f8 devid 1 transid 8 /dev/loop0 (7:0) scanned by repro (1010) BTRFS info (device loop0): first mount of filesystem 14d642db-7b15-43e4-81e6-4b8fac6a25f8 BTRFS info (device loop0): using blake2b (blake2b-256-generic) checksum algorithm BTRFS info (device loop0): using free-space-tree BTRFS warning (device loop0): checksum verify failed on logical 5312512 mirror 1 wanted 0xb043382657aede36608fd3386d6b001692ff406164733d94e2d9a180412c6003 found 0x810ceb2bacb7f0f9eb2bf3b2b15c02af867cb35ad450898169f3b1f0bd818651 level 0 DEBUG: read tree root path failed for tree csum, ret=-5 BTRFS warning (device loop0): checksum verify failed on logical 5328896 mirror 1 wanted 0x51be4e8b303da58e6340226815b70e3a93592dac3f30dd510c7517454de8567a found 0x51be4e8b303da58e634022a315b70e3a93592dac3f30dd510c7517454de8567a level 0 BTRFS warning (device loop0): checksum verify failed on logical 5292032 mirror 1 wanted 0x1924ccd683be9efc2fa98582ef58760e3848e9043db8649ee382681e220cdee4 found 0x0cb6184f6e8799d9f8cb335dccd1d1832da1071d12290dab3b85b587ecacca6e level 0 process 'repro' launched './file2' with NULL argv: empty string added DEBUG: no csum root, idatacsums=0 ibadroots=134217728 Oops: general protection fault, probably for non-canonical address 0xdffffc0000000041: 0000 [#1] SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000208-0x000000000000020f] CPU: 5 UID: 0 PID: 1010 Comm: repro Tainted: G OE 6.15.0-custom+ #249 PREEMPT(full) Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS unknown 02/02/2022 RIP: 0010:btrfs_lookup_csum+0x93/0x3d0 [btrfs] Call Trace: btrfs_lookup_bio_sums+0x47a/0xdf0 [btrfs] btrfs_submit_bbio+0x43e/0x1a80 [btrfs] submit_one_bio+0xde/0x160 [btrfs] btrfs_readahead+0x498/0x6a0 [btrfs] read_pages+0x1c3/0xb20 page_cache_ra_order+0x4b5/0xc20 filemap_get_pages+0x2d3/0x19e0 filemap_read+0x314/0xde0 __kernel_read+0x35b/0x900 bprm_execve+0x62e/0x1140 do_execveat_common.isra.0+0x3fc/0x520 __x64_sys_execveat+0xdc/0x130 do_syscall_64+0x54/0x1d0 entry_SYSCALL_64_after_hwframe+0x76/0x7e ---[ end trace 0000000000000000 ]---

[CAUSE] Firstly the fs has a corrupted csum tree root, thus to mount the fs we have to go "ro,rescue=ibadroots" mount option.

Normally with that mount option, a bad csum tree root should set BTRFS_FS_STATE_NO_DATA_CSUMS flag, so that any future data read will ignore csum search.

But in this particular case, we have the following call trace that caused NULL csum root, but not setting BTRFS_FS_STATE_NO_DATA_CSUMS:

load_global_roots_objectid():

ret = btrfs_search_slot(); /* Succeeded */ btrfs_item_key_to_cpu() found = true; /* We found the root item for csum tree. */ root = read_tree_root_path(); if (IS_ERR(root)) { if (!btrfs_test_opt(fs_info, IGNOREBADROOTS)) /* * Since we have rescue=ibadroots mount option, * @ret is still 0. */ break; if (!found || ret) { /* @found is true, @ret is 0, error handling for csum * tree is skipped. */ }

This means we completely skipped to set BTRFS_FS_STATE_NO_DATA_CSUMS if the csum tree is corrupted, which results unexpected later csum lookup.

[FIX] If read_tree_root_path() failed, always populate @ret to the error number.

As at the end of the function, we need @ret to determine if we need to do the extra error handling for csum tree.

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 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
5th
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-24). 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 (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.

The score's inputs: 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

July 9, 2025

Last Modified

December 18, 2025

Advisory Details (6)

Auto-updated Oct 23, 2026
Patch available.
Web pageMentions a patch (unverified)

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

https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Web page

btrfs: handle csum tree error with rescue=ibadroots correctly - kernel/git/stable/linux.git - Linux kernel stable tree

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

btrfs: handle csum tree error with rescue=ibadroots correctly - kernel/git/stable/linux.git - Linux kernel stable tree

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

btrfs: handle csum tree error with rescue=ibadroots correctly - kernel/git/stable/linux.git - Linux kernel stable tree

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

btrfs: handle csum tree error with rescue=ibadroots correctly - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/547e836661554dcfa15c212a3821664e85b4191a
Web page

btrfs: handle csum tree error with rescue=ibadroots correctly - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3f5c4a996f8f4fecd24a3eb344a307c50af895c2

Vendor Advisories for CVE-2025-38260(1)

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

Patch Availability(23)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-34.34) @ plucky2026-05-30ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-05-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-34.34~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-6.14 (6.14.0-1014.14) @ plucky2026-05-30ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-05-30ubuntu
ubuntulinux-tools-gcp-edge (6.14.0-1018.19~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-05-30ubuntu
ubuntulinux-tools-aws-edge (6.14.0-1015.15~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.14.0-1014.14~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1043.44) @ noble2026-05-30ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-05-30ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-05-30ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-05-30ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-05-30ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1044.44) @ noble2026-05-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-05-30ubuntu
linuxKernel @ 6.1.143 (fixes >=5.17.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.148-1~deb11u1 (11 versions)
  • every version up to 6.1.153-1~deb11u1: fixed in 6.1.153-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (41 versions)
  • every version up to 6.1.147-1: fixed in 6.1.147-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.37-1: fixed in 6.12.37-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.37-1: fixed in 6.12.37-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(22)

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 / 37× 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 98 of 186 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 88 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-38260?
CVE-2025-38260 is a medium-severity vulnerability; its CVE record was published on July 9, 2025. In the Linux kernel, the following vulnerability has been resolved: btrfs: handle csum tree error with rescue=ibadroots correctly [BUG] There is syzbot based reproducer that can crash the kernel, with the following call trace: (With some debug output added) DEBUG: rescue=ibadroots parsed BTRFS:…
When was the CVE record for CVE-2025-38260 published?
The CVE record for CVE-2025-38260 was published on July 9, 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 December 18, 2025; the record at its source may have been updated since.
Is CVE-2025-38260 actively exploited?
CVE-2025-38260 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-38260?
CVE-2025-38260 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-38260?
A fix for CVE-2025-38260 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-38260 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-38260

Explore →

Is Your Infrastructure Affected by CVE-2025-38260?

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

Book a Demo →Browse All CVEs