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

ocfs2: cancel quota sync work before freeing quota info

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, 12:05:31 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 quota info is freed without cancelling its work, potentially causing a use-after-free error. Affected versions include 4.14.17 and 4.15. The impact is uncertain.

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

6 ranges

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

affected

1a6152d36dee08da2be2a3030dceb45ef680460a → before 7873680692369bcdf65480a8d81ccd2f298a13b3

git versions

1a6152d36dee08da2be2a3030dceb45ef680460a → before 5ff0f92064ab9bb344e7389c198cc9fd7ed30e29

git versions

1a6152d36dee08da2be2a3030dceb45ef680460a → before cd3119eb1ebf8ea7631f68069addf109d4e77159

git versions

1a6152d36dee08da2be2a3030dceb45ef680460a → before 1dd1f005026d52642b994d63baa16b0b31f3b14f

git versions

606592f53b877dc77ec1356ea82ea1d7bb6e8580

git versions

4.14.17 → before 4.15

semver versions

unaffected

unknown

Other versions: unaffected

Linux · Linux

Linux

6 ranges

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

affected

4.15

unaffected

0 → before 4.15

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: cancel quota sync work before freeing quota info

OCFS2 quota info owns dqi_sync_work and must outlive both its timer and qsync_work_fn(). ocfs2_local_free_info() frees that owner without cancelling the work, relying on the quota suspend/disable wrappers.

Loading quotas on a read-only to read-write remount can successfully queue the work in ocfs2_global_read_info() and then fail while attaching a dquot to an existing inode in add_dquot_ref(). The quota core unwinds that failure directly through dquot_disable(), bypassing the OCFS2 wrapper:

Remount task (s_umount write) Timer/workqueue ocfs2_global_read_info() schedules dqi_sync_work add_dquot_ref() returns an error dquot_disable() ocfs2_local_free_info() frees oinfo delayed-work timer expires qsync_work_fn() reads oinfo

The timer core can then write to the freed embedded timer, or qsync_work_fn() can read oinfo->dqi_gqinode before its s_umount trylock. The outer ocfs2_disable_quotas() cleanup skips the failed type because dquot_disable() has already cleared its loaded state.

Cancel dqi_sync_work synchronously at the start of ocfs2_local_free_info(), before dropping the global inode or freeing any owner state. The work is initialized whenever read_file_info() succeeds. dquot_disable() holds s_umount for write, so the callback skips its quota scan via down_read_trylock() and can finish without waiting for teardown. The synchronous cancel also handles its self-rearm.

KASAN report as below:

BUG: KASAN: slab-use-after-free in __run_timers+0x9e9/0xa10
Write of size 8 at addr ffff888111b0aad0 by task swapper/3/0

Call Trace:
 <IRQ>
 dump_stack_lvl+0x93/0xd0
 print_report+0xce/0x630
 ? __run_timers+0x9e9/0xa10
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? __virt_addr_valid+0x20e/0x420
 ? __run_timers+0x9e9/0xa10
 kasan_report+0xe0/0x110
 ? __run_timers+0x9e9/0xa10
 __run_timers+0x9e9/0xa10
 ? __pfx___run_timers+0x10/0x10
 ? __lock_acquire+0x5a3/0x2140
 ? __pfx_do_raw_spin_lock+0x10/0x10
 ? srso_alias_return_thunk+0x5/0xfbef5
 timer_expire_remote+0xfa/0x160
 ? __pfx_timer_expire_remote+0x10/0x10
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? trace_hardirqs_on+0x18/0x160
 tmigr_handle_remote_up+0x4ba/0x9d0
 ? __pfx_tmigr_handle_remote_up+0x10/0x10
 ? tmigr_handle_remote+0x21a/0x340
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? lock_release+0xc8/0x290
 ? __pfx_tmigr_handle_remote_up+0x10/0x10
 __walk_groups_from+0x5a/0x160
 tmigr_handle_remote+0x24f/0x340
 ? __pfx_tmigr_handle_remote+0x10/0x10
 ? lock_acquire+0x190/0x300
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? lock_release+0xc8/0x290
 run_timer_softirq+0x222/0x270
 ? __pfx_run_timer_softirq+0x10/0x10
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? lockdep_hardirqs_on_prepare+0xb8/0x1a0
 ? srso_alias_return_thunk+0x5/0xfbef5
 handle_softirqs+0x1fa/0x8d0
 ? __pfx_handle_softirqs+0x10/0x10
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? _raw_spin_unlock+0x23/0x40
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? __hrtimer_rearm_deferred+0x1fb/0x5d0
 __irq_exit_rcu+0x113/0x1e0
 irq_exit_rcu+0xe/0x20
 sysvec_apic_timer_interrupt+0x6c/0x80
 </IRQ>
 <TASK>
 asm_sysvec_apic_timer_interrupt+0x1a/0x20
 ? ct_kernel_exit.constprop.0+0xc5/0xf0
 ? do_idle+0x3ae/0x650
 default_idle+0x9/0x10
 default_idle_call+0x6c/0xb0
 do_idle+0x3ae/0x650
 ? cpuhp_online_idle+0x9c/0xb0
 ? __pfx_do_idle+0x10/0x10
 ? __entry_text_end+0x1020f6/0x1020f9
 ? lockdep_hardirqs_on_prepare+0xeb/0x1a0
 ? srso_alias_return_thunk+0x5/0xfbef5
 ? trace_hardirqs_on+0x18/0x160
 ? srso_a

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

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): 4.15

Before: 6.12.117

Vulnerable product

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

From (inclusive): 4.15

Before: 6.18.61

Vulnerable product

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

From (inclusive): 4.15

Before: 7.3.2

Vulnerable product

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

From (inclusive): 4.15

Before: 7.4-rc1

Vulnerable product

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

From (inclusive): 4.14.17

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

Assigning organization

2026-11-19

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.