Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-23465: btrfs: log new dentries when logging parent dir of a conflicting inode

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 1cf30c73602c69d750c9345c47f2c0e9d0cfb578, 56e72c8b02d982be775d9df025357c152383ee84, 6c23595c54cfeb878e3fbbb8eb08bc5061d0c2d4.

Low priority for now. Upgrade to Linux Linux 1cf30c73602c69d750c9345c47f2c0e9d0cfb578, 56e72c8b02d982be775d9df025357c152383ee84, 6c23595c54cfeb878e3fbbb8eb08bc5061d0c2d4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: btrfs: log new dentries when logging parent dir of a conflicting inode If we log the parent directory of a conflicting inode, we are not logging the new dentries of the directory, so when we finish we have the parent directory's inode marked as logged but we did not log its new dentries. As a consequence if the parent directory is explicitly fsynced later and it does not have any new changes since we logged it, the fsync is a no-op and after a power failure the new dentries are missing. Example scenario: $ mkdir foo $ sync $rmdir foo $ mkdir dir1 $ mkdir dir2 # A file with the same name and parent as the directory we just deleted # and was persisted in a past transaction. So the deleted directory's # inode is a conflicting inode of this new file's inode. $ touch foo $ ln foo dir2/link # The fsync on dir2 will log the parent directory (".") because the # conflicting inode (deleted directory) does not exists anymore, but it # it does not log its new dentries (dir1). $ xfs_io -c "fsync" dir2 # This fsync on the parent directory is no-op, since the previous fsync # logged it (but without logging its new dentries). $ xfs_io -c "fsync" . <power failure> # After log replay dir1 is missing. Fix this by ensuring we log new dir dentries whenever we log the parent directory of a no longer existing conflicting inode. A test case for fstests will follow soon.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Apr 3, 2026
Updated
Oct 30, 2026
EPSS
0.1% · 2th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-23465

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.1 and later · before 6.6.130
  • linux linux kernel6.7 and later · before 6.12.78
  • linux linux kernel6.13 and later · before 6.18.20
  • linux linux kernel6.19 and later · before 6.19.10
  • linux linux kernel7.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.1affected
    • a3baaf0d786e22fc86295fda9c58ba0dee07599f and later · before 6c23595c54cfeb878e3fbbb8eb08bc5061d0c2d4affected · git
    • a3baaf0d786e22fc86295fda9c58ba0dee07599f and later · before 56e72c8b02d982be775d9df025357c152383ee84affected · git
    • a3baaf0d786e22fc86295fda9c58ba0dee07599f and later · before f556b1e09d054e31f464c0fd37280c2b5a393feeaffected · git
    • a3baaf0d786e22fc86295fda9c58ba0dee07599f and later · before 1cf30c73602c69d750c9345c47f2c0e9d0cfb578affected · git
    • a3baaf0d786e22fc86295fda9c58ba0dee07599f and later · before 6f5a51969b1deb79aefd2194b48fe7e78e72ff7eaffected · git
    • a3baaf0d786e22fc86295fda9c58ba0dee07599f and later · before 9573a365ff9ff45da9222d3fe63695ce562beb24affected · git
    • before 5.1not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver
    • 6.6.130 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:13linuxbefore 6.12.85-16.12.85-1
Debian:14linuxbefore 6.19.10-16.19.10-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-23462Apr 3, 2026 · Bluetooth: HIDP: Fix possible UAF
    35Monitor
  • ← EarlierCVE-2026-23463Apr 3, 2026 · soc: fsl: qbman: fix race condition in qman_destroy_fq
    18Monitor
  • Later →CVE-2026-23466Apr 3, 2026 · drm/xe: Open-code GGTT MMIO access protection
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1cf30c73602c69d750c9345c47f2c0e9d0cfb578Vendor (CNA)
Linux Linux56e72c8b02d982be775d9df025357c152383ee84Vendor (CNA)
Linux Linux6c23595c54cfeb878e3fbbb8eb08bc5061d0c2d4Vendor (CNA)
Linux Linux6f5a51969b1deb79aefd2194b48fe7e78e72ff7eVendor (CNA)
Linux Linux9573a365ff9ff45da9222d3fe63695ce562beb24Vendor (CNA)
Linux Linuxf556b1e09d054e31f464c0fd37280c2b5a393feeVendor (CNA)
debian:linux6.12.85-1 · Debian:13Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records