Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
Check your stack
CVE-2026-99429

ocfs2: pin refcount trees before dropping the lookup lock

Products / packages Linux

Published

Share

Severity and exploitation

Not in CISA KEV

KEV coverage does not rule out exploitation.

KEV checked 22/11/2026, 11:50:32 UTC
Linux · CVSS:3.1 · 7.8
Assessment vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Severity

high7.8

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Not established by this record

Missing evidence does not mean no public exploit exists.

Remediation

Fix status not established

No structured fix or guidance is available here. Check the latest publisher advisory.

What this means

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

Source excerpt · Linux

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

Linux · Linux

Linux

4 ranges

Compare with this publisher’s ranges. This does not inspect your installation.

affected

374a263e790c4de85844283c098810a92985f623 → before ce7b46556af15642a1e9f8d0c596022dd7cfb4a7

git versions

374a263e790c4de85844283c098810a92985f623 → before 7ff4f020f7b03fddd529735f0b61ac0a8dd92c9e

git versions

374a263e790c4de85844283c098810a92985f623 → before 2d9e864c234469dc7f56ea974f8269d251441e6a

git versions

374a263e790c4de85844283c098810a92985f623 → before 8c714a074074af7ae59233c1fa6ef9d7aa710462

git versions

unaffected

unknown

Other versions: unaffected

Linux · Linux

Linux

6 ranges

Compare with this publisher’s ranges. This does not inspect your installation.

affected

2.6.32

unaffected

0 → before 2.6.32

semver versions

6.12.117 → through 6.12.*

semver versions

6.18.61 → through 6.18.*

semver versions

7.3.2 → through 7.3.*

semver versions

7.4-rc1 → through *

original_commit_for_fix versions

unknown

Other versions: affected

Automatic dependency matching is unavailable for this record. Use the product evidence and publisher’s instructions to check your installation.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

No structured fix or remediation guidance is available here. Check the full source description and vendor’s latest advisory for a patch or workaround; do not assume another version is safe.

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.

Original source description

Read the full publisher description

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

ocfs2: pin refcount trees before dropping the lookup lock

A refcount tree returned to ocfs2_lock_refcount_tree() must stay alive until that caller releases its operation reference. However, ocfs2_get_refcount_tree() returns the cached pointer after dropping osb_lock, and the caller only takes its kref afterwards. The registry reference does not protect this gap from concurrent removal.

This can happen when another node frees a refcount root and reuses its block with a different generation while this mount retains the old cached tree. Two local operations on different inodes sharing the new root, such as data CoW and an external xattr update, can then look up the same stale tree. Their inode locks are independent, and both the REFCOUNT DLM lock and rf_sem are acquired after the first operation reference.

The following ordering is possible, with no other operation references:

Data CoW Xattr update


Look up the old tree under osb_lock, then drop osb_lock Look up the same tree and take a kref Acquire the tree locks and read the new on-disk generation Erase the old tree under osb_lock Unlock and drop the operation kref Drop the registry kref, freeing tree Take a kref through the freed tree pointer

The final kref_get() accesses freed rf_getcnt storage, and subsequent accesses in ocfs2_lock_refcount_tree() also use the freed allocation.

Take the operation reference in ocfs2_get_refcount_tree() before releasing osb_lock, including when an insertion loses to another lookup. Removal must acquire the same lock, so it cannot drop the registry reference before the lookup has pinned the tree. Keep the existing unlock and error path puts. The two callers that already hold the refcount tree lock keep their borrowed lookup behavior and do not acquire an extra reference.

KASAN report as below:

BUG: KASAN: slab-use-after-free in ocfs2_lock_refcount_tree+0x94a/0x9b0
Read of size 4 at addr ffff888117212820 by task python3/497

[Kernel and hardware identification omitted.]

Call Trace:
 <TASK>
 dump_stack_lvl+0x93/0xd0
 print_report+0xce/0x630
 ? ocfs2_lock_refcount_tree+0x94a/0x9b0
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? __virt_addr_valid+0x20e/0x420
 ? ocfs2_lock_refcount_tree+0x94a/0x9b0
 kasan_report+0xe0/0x110
 ? ocfs2_lock_refcount_tree+0x94a/0x9b0
 ocfs2_lock_refcount_tree+0x94a/0x9b0
 ? __pfx_ocfs2_lock_refcount_tree+0x10/0x10
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? ocfs2_refcount_cow+0x3b6/0xd90
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? __kmalloc_cache_noprof+0x28d/0x610
 ? ocfs2_refcount_cow+0x3b6/0xd90
 ocfs2_refcount_cow+0x410/0xd90
 ? __pfx_ocfs2_refcount_cow+0x10/0x10
 ? __pfx___might_resched+0x10/0x10
 ? down_write+0x11a/0x1f0
 ? __pfx_down_write+0x10/0x10
 ? ocfs2_inode_unlock+0x1a9/0x260
 ? __pfx_ocfs2_inode_unlock+0x10/0x10
 ? ocfs2_file_write_iter+0x1413/0x1d30
 ocfs2_file_write_iter+0x157b/0x1d30
 ? __pfx_ocfs2_file_write_iter+0x10/0x10
 ? lock_acquire+0x190/0x300
 ? __x64_sys_pwrite64+0x1b7/0x220
 ? __pfx___might_resched+0x10/0x10
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? security_file_permission+0x26/0x80
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? lock_is_held_type+0x8f/0x100
 vfs_write+0x639/0x1010
 ? __pfx_ocfs2_file_write_iter+0x10/0x10
 ? lock_vma_under_rcu+0x154/0x4a0
 ? __pfx_vfs_write+0x10/0x10
 ? lock_release+0x121/0x290
 ? srso_alias_return_thunk+0x5/0xfbef5
 __x64_sys_pwrite64+0x1b7/0x220
 ? __pfx___x64_sys_pwrite64+0x10/0x10
 ? irqentry_exit+0xbe/0x820

---truncated---

References

4 sources

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification · not supplied
Additional publishers · not supplied

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-99429

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Environment requirements

These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.

Linux · platform conditions

Any condition may hold

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 2.6.32

Before: 6.12.117

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 2.6.32

Before: 6.18.61

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 2.6.32

Before: 7.3.2

Vulnerable product

cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

From (inclusive): 2.6.32

Before: 7.4-rc1

Applicability preview
[
  {
    "nodes": [
      {
        "operator": "OR",
        "negate": false,
        "cpeMatch": [
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "2.6.32",
            "versionEndExcluding": "6.12.117"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "2.6.32",
            "versionEndExcluding": "6.18.61"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "2.6.32",
            "versionEndExcluding": "7.3.2"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "2.6.32",
            "versionEndExcluding": "7.4-rc1"
          }
        ]
      }
    ]
  }
]
Contributing organizations · 1
Linux

Assigning organization

2026-11-22

Timeline

All times UTC
  1. Advisory published

    Publication date supplied by the source.

  2. Source updated

    Latest modification date supplied by the source.

  3. Last imported by cve.new

    Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes
  1. CVE · CVE-2026-99429

    Observed 2026-11-22T11:21:19.208Z · upstream updated 2026-11-22T11:08:12.672Z

    Severity assessment changed

    before

    []

    after

    [
      {
        "source": "Linux",
        "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
        "score": 7.8
      }
    ]

Large field values are marked as truncated previews. Original source snapshots remain retained.

Showing up to 50 most recent observed changes.