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-43168ocfs2: fix reflink preserve cleanup issue

Description

In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix reflink preserve cleanup issue commit c06c303832ec ("ocfs2: fix xattr array entry __counted_by error") doesn't handle all cases and the cleanup job for preserved xattr entries still has bug: - the 'last' pointer should be shifted by one unit after cleanup an array entry. - current code logic doesn't cleanup the first entry when xh_count is 1. Note, commit c06c303832ec is also a bug fix for 0fe9b66c65f3.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 6 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-43168, 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 (18 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 0fe9b66c65f3ff227da45381afe7612f91e32740 – < c44d86ca949cb1e5566ad14510cc26fa1a17e2d8
    • affected 0fe9b66c65f3ff227da45381afe7612f91e32740 – < 02acc9f72365e50eb45a56b7dacb9114ca3b503c
    • affected 0fe9b66c65f3ff227da45381afe7612f91e32740 – < 8ff329353134280b203cb2bce95311cb8f7cbd8a
    • affected 0fe9b66c65f3ff227da45381afe7612f91e32740 – < bb273b68c1719c2925e05557f7e7099edb066680
    • affected 0fe9b66c65f3ff227da45381afe7612f91e32740 – < b2952dbeac2c3c527cb0519d5ffaeb95b062466a
    • affected 0fe9b66c65f3ff227da45381afe7612f91e32740 – < 3bdc3766aafb052aef4baadef455a84c1c0a059d
    • affected 0fe9b66c65f3ff227da45381afe7612f91e32740 – < 2f4daccd9d9b8b2952df7878df8c2e8ba6439398
    • affected 0fe9b66c65f3ff227da45381afe7612f91e32740 – < 5138c936c2c82c9be8883921854bc6f7e1177d8c
  • Linux · Linux

    • affected 2.6.32
    • unaffected < 2.6.32
    • unaffected 5.10.252 – ≤ 5.10.*
    • unaffected 5.15.202 – ≤ 5.15.*
    • unaffected 6.1.165 – ≤ 6.1.*
    • unaffected 6.6.128 – ≤ 6.6.*
    • unaffected 6.12.75 – ≤ 6.12.*
    • unaffected 6.18.16 – ≤ 6.18.*
    • unaffected 6.19.6 – ≤ 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-43168 badge
[![CVE-2026-43168](https://cveledger.app/badge/CVE-2026-43168.svg)](https://cveledger.app/cve/CVE-2026-43168)

Record last updated .