CVE-2026-98897

ksmbd: don't hold ci->m_lock while waiting for a lease break ack

Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: don't hold ci->m_lock while waiting for a lease break ack When a cifs.ko client caches a read-handle (RH) lease via deferred close and a conflicting open arrives, ksmbd breaks the lease and waits for the acknowledgment in wait_for_break_ack() for up to OPLOCK_WAIT_TIME (35s). __smb_break_all_levII_oplock() runs that wait while holding ci->m_lock for read. cifs.ko reacts to a handle-lease break by closing the deferred handle rather than sending a lease break acknowledgment. That close path (close_id_del_oplock() -> opinfo_del()) takes ci->m_lock for write and is exactly what would wake the waiter, but it blocks on the read lock held by the waiting thread. The break is then resolved only by the 35s timeout, so xfstests generic/001 takes ~78s with leases enabled versus ~4s with oplocks only. Collect the target opinfos (each pinned with a reference) while holding ci->m_lock, then break them after releasing it, matching how smb_grant_oplock() already breaks a conflicting lease using only a reference. The reference keeps the opinfo (and its conn and lease) alive across the unlocked window, and a close racing the break is handled by the existing OPLOCK_CLOSING state check. Apply the same fix to the parent lease break paths.

Key facts

Published
23 Oct 2026
Last changed
26 Oct 2026
Assigned by
Linux
EPSS
0.192% likely to be exploited in the next 30 days, higher than 8.939% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • d1c189c6cb8b0fb7b5ee549237d27889c40c2f8b up to but excluding 868c9038ffd4af39766d087f68c8f543a3f66635 (affected)
  • d1c189c6cb8b0fb7b5ee549237d27889c40c2f8b up to but excluding 27a9bc968d4ae809a3f5ca2f2b136856ee613cb4 (affected)
  • 16ece7c5645a68efca22a0a69a7718c8e50c3232 (affected)
  • 6.6.35 up to but excluding 6.7 (affected)
LinuxLinux
  • Default status: affected
  • 6.9 (affected)
  • 0 up to but excluding 6.9 (unaffected)
  • 6.18.53 up to and including 6.18.* (unaffected)
  • 7.2 up to and including * (unaffected)

Timeline

  1. 23 Oct 2026 Published

References