---
id: CVE-2026-80926
title: |-
  In the Linux kernel, the following vulnerability has been resolved:

  ksmbd: fix use-after-free in oplock break notification

  smb2_oplock_break_noti() reads opinfo->conn without any lock and
  dereferences it after two allocations which may…
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  ksmbd: fix use-after-free in oplock break notification

  smb2_oplock_break_noti() reads opinfo->conn without any lock and
  dereferences it after two allocations which may…
severity: critical
cvss: 9.8
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 1ff58dcfcab434ebb51649da33774fbb8e1f7b67 <
    5de0527f782430b1109a447646e32033ad018a6a
  - >-
    Linux >= e735dbd489e3ea02be78dba991056fe1138be51e <
    c8279ae8df68cce9cd3b785e85f7a86c80a46e78
  - >-
    Linux >= b003086d76968298f22e7cf62239833b5a3a06b1 <
    8cc98db4fc590e6c7d9db6529320982ee16c5d1d
  - >-
    Linux >= b003086d76968298f22e7cf62239833b5a3a06b1 <
    0e753899627b5e28a9fea8bca98262a6f65a2452
  - Linux 945a86b21b40fb17183f5b27461baa6f03e2467f
  - Linux 75e33deda658c1ab3a9336cbdb1436536f9b3660
  - Linux >= 6.12.94 < 6.12.111
  - Linux >= 6.18.36 < 6.18.51
  - Linux >= 6.6.143 < 6.7
  - Linux >= 7.0.13 < 7.1
  - Linux 7.1
published: '2026-09-11'
updated: '2026-09-21'
sourceUpdated: '2026-09-21T14:17:21.413'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-80926'
references:
  - url: 'https://git.kernel.org/stable/c/0e753899627b5e28a9fea8bca98262a6f65a2452'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/5de0527f782430b1109a447646e32033ad018a6a'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/8cc98db4fc590e6c7d9db6529320982ee16c5d1d'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/c8279ae8df68cce9cd3b785e85f7a86c80a46e78'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
epss: 0.0045
epssPercentile: 0.38491
ingestedAt: '2026-09-14T15:23:07.476Z'
---

## Overview

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

ksmbd: fix use-after-free in oplock break notification

smb2_oplock_break_noti() reads opinfo->conn without any lock and
dereferences it after two allocations which may sleep.  When the
durable handle owning the oplock is disconnected, session_fd_check()
clears opinfo->conn and drops its conn reference under ci->m_lock, and
the last ksmbd_conn_put() frees the connection.  A break triggered by
another connection that races with the teardown can then resurrect the
freed connection: ksmbd_conn_get() is a plain atomic_inc, and the
queued break work later dereferences the stale conn via
ksmbd_conn_write(), a use-after-free reachable by any authenticated
client holding a durable batch oplock.

Thread the caller's inode into the notification path instead of taking
a new reference on it.  Every caller of oplock_break() already holds a
live ksmbd_file (or an explicit ksmbd_inode_lookup_lock() reference,
in the parent lease break paths) on the inode that owns the break
target's oplock list, so ci cannot be freed during the call, and its
lock can be taken without dereferencing opinfo->o_fp, which a
concurrent close may free.  Select and pin the connection under
ci->m_lock, the same lock session_fd_check() and
ksmbd_reopen_durable_fd() use to update opinfo->conn, so a concurrent
detach either loses the race to the clear or keeps the connection
alive until the notification work releases it.  Transfer the reference
to the work item and release it on allocation failures.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.