CVE-2026-23141

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-02-14. 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

A fix is available — apply it.

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

btrfs: send: check for inline extents in range_is_hole_in_parent()

Before accessing the disk_bytenr field of a file extent item we need to check if we are dealing with an inline extent. This is because for inline extents their data starts at the offset of the disk_bytenr field. So accessing the disk_bytenr means we are accessing inline data or in case the inline data is less than 8 bytes we can actually cause an invalid memory access if this inline extent item is the first item in the leaf or access metadata from other items.

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

Published

February 14, 2026

Last Modified

June 17, 2026

Advisory Details (6)

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

btrfs: send: check for inline extents in range_is_hole_in_parent() - kernel/git/stable/linux.git - Linux kernel stable tree

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

btrfs: send: check for inline extents in range_is_hole_in_parent() - kernel/git/stable/linux.git - Linux kernel stable tree

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

btrfs: send: check for inline extents in range_is_hole_in_parent() - kernel/git/stable/linux.git - Linux kernel stable tree

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

btrfs: send: check for inline extents in range_is_hole_in_parent() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/901e581bfc44d181f7d9c3f11880dac3e89deb2e
generic

btrfs: send: check for inline extents in range_is_hole_in_parent() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/39f83f10772310ba4a77f2b5256aaf36994ef7e8
generic

btrfs: send: check for inline extents in range_is_hole_in_parent() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/08b096c1372cd69627f4f559fb47c9fb67a52b39

Vendor Advisories for CVE-2026-23141(1)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1054.57.1) @ noble2026-06-12ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1051.52~22.04.1) @ jammy2026-06-12ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-116.116+fips1) @ noble2026-06-12ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1024.24) @ noble2026-06-12ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1054.57~22.04.1) @ jammy2026-06-12ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1056.62) @ noble2026-06-12ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1059.65+fips1) @ noble2026-06-12ubuntu
linuxKernel @ 5.15.209—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 rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.69-1~bpo12+1 (10 versions)6.12.69-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (96 versions)6.18.8-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 5× in last 7d / 23× 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 177 total refreshes for this CVE.

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

Related CVEs

Related CVEs are temporarily unavailable — the same-product, same-vendor and same-CWE lists could not be loaded just now. That is not a sign that none exist; please retry shortly.

Frequently asked(5)

What is CVE-2026-23141?
CVE-2026-23141 is a medium vulnerability published on February 14, 2026. In the Linux kernel, the following vulnerability has been resolved: btrfs: send: check for inline extents in rangeisholeinparent() Before accessing the disk_bytenr field of a file extent item we need to check if we are dealing with an inline extent. This is because for inline extents their data…
When was CVE-2026-23141 disclosed?
CVE-2026-23141 was first published in the National Vulnerability Database on February 14, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23141 actively exploited?
CVE-2026-23141 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 97.3% of all scored CVEs.
What is the CVSS score of CVE-2026-23141?
CVE-2026-23141 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-23141?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23141, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-23141

Explore →

Is Your Infrastructure Affected by CVE-2026-23141?

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

Start Free Scan →Browse All CVEs