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-99692

ocfs2: stop recovery before shutting down local allocators

Products / packages Linux

Published

Share

Severity and exploitation

Not in CISA KEVNo CVSS score

KEV coverage does not rule out exploitation.

KEV checked 22/11/2026, 11:50:32 UTC

Severity

unknown

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

The Linux kernel's ocfs2 has a vulnerability where recovery completion may use a released buffer, potentially causing issues. The affected versions are prior to 6.12.118, 6.18.64, 7.3.5, and 7.4-rc2. Local access is required to exploit this weakness.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

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

ccd979bdbce9fba8412beb3f1de68a9d0171b12c → before 22c123334f3c4effc0b46923da2938e54ad3075b

git versions

ccd979bdbce9fba8412beb3f1de68a9d0171b12c → before 781991ddd2c4b6f003b7bdef6b7aae6db722707d

git versions

ccd979bdbce9fba8412beb3f1de68a9d0171b12c → before 47997a43d33fcb3d4a87249bfd8ab07ede119fa3

git versions

ccd979bdbce9fba8412beb3f1de68a9d0171b12c → before 126429e2f503ade63502978beb0c519066442250

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.16

unaffected

0 → before 2.6.16

semver versions

6.12.118 → through 6.12.*

semver versions

6.18.64 → through 6.18.*

semver versions

7.3.5 → through 7.3.*

semver versions

7.4-rc2 → 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: stop recovery before shutting down local allocators

Recovery completion needs the local allocators until it has finished reclaiming a failed node's allocation window and truncate log. During unmount, quota recovery is stopped first, but that leaves recovery_state at OCFS2_REC_QUOTA_DISABLED. New non-quota recovery can still start.

ocfs2_truncate_log_shutdown() drains existing completion work and releases osb_tl_bh before ocfs2_recovery_exit() closes that publication path:

Unmount Recovery


stop quota recovery; disable quotas truncate_log_shutdown() flush existing completion work recover another failed node queue completion flush local log; release buffer complete_truncate_log_recovery() use released osb_tl_bh recovery_exit(): disable and drain

An extra buffer reference alone would still let completion append new records after the final truncate-log flush.

Split stopping and draining recovery from freeing its state. Stop all recovery producers and drain completion work before shutting down either local allocator. Keep recovery-state release at its existing later point, so its lifetime relative to other teardown users stays unchanged. The second stop at recovery_exit() is harmless once recovery is disabled.

KASAN report as below:

BUG: KASAN: slab-use-after-free in ocfs2_truncate_log_needs_flush+0x23d/0x360
Read of size 8 at addr ffff8881093711e8 by task kworker/u16:3/53

CPU: 0 UID: 0 PID: 53 Comm: kworker/u16:3 Not tainted 7.3.0-rc4-next-20260921-pmb-ocfs2-functional-v1+ #1 PREEMPT(lazy) 
Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
Workqueue: ocfs2_wq ocfs2_complete_recovery
Call Trace:
 <TASK>
 dump_stack_lvl+0x93/0xd0
 print_report+0xce/0x630
 ? ocfs2_truncate_log_needs_flush+0x23d/0x360
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? __virt_addr_valid+0x20e/0x420
 ? ocfs2_truncate_log_needs_flush+0x23d/0x360
 kasan_report+0xe0/0x110
 ? ocfs2_truncate_log_needs_flush+0x23d/0x360
 ocfs2_truncate_log_needs_flush+0x23d/0x360
 ? __pfx_ocfs2_truncate_log_needs_flush+0x10/0x10
 ? __pfx_down_write+0x10/0x10
 ocfs2_complete_truncate_log_recovery+0x315/0x780
 ? trace_hardirqs_on+0x18/0x160
 ? __pfx_ocfs2_complete_truncate_log_recovery+0x10/0x10
 ? ocfs2_complete_recovery+0x666/0x11b0
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? kfree+0x308/0x580
 ocfs2_complete_recovery+0x676/0x11b0
 ? __pfx_ocfs2_complete_recovery+0x10/0x10
 ? reacquire_held_locks+0xdd/0x200
 ? process_one_work+0x7c8/0x1b40
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? lock_acquire+0x190/0x300
 ? __pfx_autoremove_wake_function+0x10/0x10
 ? process_one_work+0x834/0x1b40
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? lock_release+0xc8/0x290
 ? srso_alias_return_thunk+0x5/0xfbef5
 process_one_work+0x9a8/0x1b40
 ? __pfx_process_one_work+0x10/0x10
 ? lock_acquire+0x190/0x300
 ? lock_is_held_type+0x8f/0x100
 ? srso_alias_return_thunk+0x5/0xfbef5
 worker_thread+0x65c/0xe40
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? __kthread_parkme+0x177/0x220
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? __pfx_worker_thread+0x10/0x10
 kthread+0x351/0x460
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? __pfx_kthread+0x10/0x10
 ret_from_fork+0x659/0x940
 ? __pfx_ret_from_fork+0x10/0x10
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? __switch_to+0x74f/0xf70
 ? __pfx_kthread+0x10/0x10
 ret_from_fork_asm+0x1a/0x30
 </TASK>

Allocated by task 538:
 kasan_save_stack+0x33/0x60
 kasan

---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-99692

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.16

Before: 6.12.118

Vulnerable product

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

From (inclusive): 2.6.16

Before: 6.18.64

Vulnerable product

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

From (inclusive): 2.6.16

Before: 7.3.5

Vulnerable product

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

From (inclusive): 2.6.16

Before: 7.4-rc2

Applicability preview
[
  {
    "nodes": [
      {
        "operator": "OR",
        "negate": false,
        "cpeMatch": [
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "2.6.16",
            "versionEndExcluding": "6.12.118"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "2.6.16",
            "versionEndExcluding": "6.18.64"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "2.6.16",
            "versionEndExcluding": "7.3.5"
          },
          {
            "vulnerable": true,
            "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
            "versionStartIncluding": "2.6.16",
            "versionEndExcluding": "7.4-rc2"
          }
        ]
      }
    ]
  }
]
Contributing organizations · 1
Linux

Assigning organization

2026-11-20

Timeline

All times UTC
  1. Advisory published

    Publication date supplied by the source.

  2. Last imported by cve.new

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

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

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