Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-23141btrfs: send: check for inline extents in range_is_hole_in_parent()

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 32 days later

    Published

  3. · 9 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-23141, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.15% · top 96% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 82bfb2e7b645c8f228dc3b6d3b27b0b10125ca4f – < 901e581bfc44d181f7d9c3f11880dac3e89deb2e
    • affected 82bfb2e7b645c8f228dc3b6d3b27b0b10125ca4f – < d948055bd46a9c14d1d4217aed65c5c258c32903
    • affected 82bfb2e7b645c8f228dc3b6d3b27b0b10125ca4f – < f2dc6ab3a14c2d2eb0b14783427eb9b03bf631c9
    • affected 82bfb2e7b645c8f228dc3b6d3b27b0b10125ca4f – < db00636643e66898d79f2530ac9c56ebd5eca369
    • affected 82bfb2e7b645c8f228dc3b6d3b27b0b10125ca4f – < 39f83f10772310ba4a77f2b5256aaf36994ef7e8
    • affected 82bfb2e7b645c8f228dc3b6d3b27b0b10125ca4f – < 08b096c1372cd69627f4f559fb47c9fb67a52b39
  • Linux · Linux

    • affected 4.11
    • unaffected < 4.11
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.167 – ≤ 6.1.*
    • unaffected 6.6.122 – ≤ 6.6.*
    • unaffected 6.12.67 – ≤ 6.12.*
    • unaffected 6.18.7 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-23141 badge
[![CVE-2026-23141](https://cveledger.app/badge/CVE-2026-23141.svg)](https://cveledger.app/cve/CVE-2026-23141)

Record last updated .