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-43066ext4: fix iloc.bh leak in ext4_fc_replay_inode() error paths

Description

In the Linux kernel, the following vulnerability has been resolved: ext4: fix iloc.bh leak in ext4_fc_replay_inode() error paths During code review, Joseph found that ext4_fc_replay_inode() calls ext4_get_fc_inode_loc() to get the inode location, which holds a reference to iloc.bh that must be released via brelse(). However, several error paths jump to the 'out' label without releasing iloc.bh: - ext4_handle_dirty_metadata() failure - sync_dirty_buffer() failure - ext4_mark_inode_used() failure - ext4_iget() failure Fix this by introducing an 'out_brelse' label placed just before the existing 'out' label to ensure iloc.bh is always released. Additionally, make ext4_fc_replay_inode() propagate errors properly instead of always returning 0.

Timeline

  1. ID reserved

    By Linux

  2. · 4 days later

    Published

  3. · 6 days 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-43066, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.12% · top 98% of all CVEs (17 Nov 2026)
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 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 – < 0892f12cd49fde5d5db68137923db107f894f3a3
    • affected 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 – < 5a63033696e60b5d70816f1d119645ac5b0b0a03
    • affected 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 – < 9c90449a9ac2cd1ba540ad2561b8b70c1bfb0a25
    • affected 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 – < ca99cbcc316cdfd2040cc2b13d1426ccb3b3b50b
    • affected 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 – < 19782b4c793b49a6aa4abbb307ddff3610009d21
    • affected 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 – < f7817ad399d604e8639005d87d148b5ec626ad26
    • affected 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 – < c426231e3d51916e83b6d1ab7ed8a65e83bca5b4
    • affected 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 – < ec0a7500d8eace5b4f305fa0c594dd148f0e8d29
  • Linux · Linux

    • affected 5.10
    • unaffected < 5.10
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.168 – ≤ 6.1.*
    • unaffected 6.6.131 – ≤ 6.6.*
    • unaffected 6.12.80 – ≤ 6.12.*
    • unaffected 6.18.21 – ≤ 6.18.*
    • unaffected 6.19.11 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .