{"api_version":"1","generated_at":"2026-09-27T01:42:59+00:00","cve":"CVE-2026-80926","urls":{"html":"https://cve.report/CVE-2026-80926","api":"https://cve.report/api/cve/CVE-2026-80926.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-80926","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-80926"},"summary":{"title":"ksmbd: fix use-after-free in oplock break notification","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix use-after-free in oplock break notification\n\nsmb2_oplock_break_noti() reads opinfo->conn without any lock and\ndereferences it after two allocations which may sleep.  When the\ndurable handle owning the oplock is disconnected, session_fd_check()\nclears opinfo->conn and drops its conn reference under ci->m_lock, and\nthe last ksmbd_conn_put() frees the connection.  A break triggered by\nanother connection that races with the teardown can then resurrect the\nfreed connection: ksmbd_conn_get() is a plain atomic_inc, and the\nqueued break work later dereferences the stale conn via\nksmbd_conn_write(), a use-after-free reachable by any authenticated\nclient holding a durable batch oplock.\n\nThread the caller's inode into the notification path instead of taking\na new reference on it.  Every caller of oplock_break() already holds a\nlive ksmbd_file (or an explicit ksmbd_inode_lookup_lock() reference,\nin the parent lease break paths) on the inode that owns the break\ntarget's oplock list, so ci cannot be freed during the call, and its\nlock can be taken without dereferencing opinfo->o_fp, which a\nconcurrent close may free.  Select and pin the connection under\nci->m_lock, the same lock session_fd_check() and\nksmbd_reopen_durable_fd() use to update opinfo->conn, so a concurrent\ndetach either loses the race to the clear or keeps the connection\nalive until the notification work releases it.  Transfer the reference\nto the work item and release it on allocation failures.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-11 20:18:56","updated_at":"2026-09-21 14:17:21"},"problem_types":[],"metrics":[{"version":"3.1","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","score":"9.8","severity":"CRITICAL","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","baseScore":9.8,"baseSeverity":"CRITICAL","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"9.8","severity":"CRITICAL","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","data":{"baseScore":9.8,"baseSeverity":"CRITICAL","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"}}],"references":[{"url":"https://git.kernel.org/stable/c/8cc98db4fc590e6c7d9db6529320982ee16c5d1d","name":"https://git.kernel.org/stable/c/8cc98db4fc590e6c7d9db6529320982ee16c5d1d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/c8279ae8df68cce9cd3b785e85f7a86c80a46e78","name":"https://git.kernel.org/stable/c/c8279ae8df68cce9cd3b785e85f7a86c80a46e78","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/5de0527f782430b1109a447646e32033ad018a6a","name":"https://git.kernel.org/stable/c/5de0527f782430b1109a447646e32033ad018a6a","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/0e753899627b5e28a9fea8bca98262a6f65a2452","name":"https://git.kernel.org/stable/c/0e753899627b5e28a9fea8bca98262a6f65a2452","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-80926","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80926","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1ff58dcfcab434ebb51649da33774fbb8e1f7b67 5de0527f782430b1109a447646e32033ad018a6a git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e735dbd489e3ea02be78dba991056fe1138be51e c8279ae8df68cce9cd3b785e85f7a86c80a46e78 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b003086d76968298f22e7cf62239833b5a3a06b1 8cc98db4fc590e6c7d9db6529320982ee16c5d1d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected b003086d76968298f22e7cf62239833b5a3a06b1 0e753899627b5e28a9fea8bca98262a6f65a2452 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 945a86b21b40fb17183f5b27461baa6f03e2467f git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 75e33deda658c1ab3a9336cbdb1436536f9b3660 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.12.94 6.12.111 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.18.36 6.18.51 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.6.143 6.7 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7.0.13 7.1 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 7.1","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.111 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.51 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.5 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"80926","cve":"CVE-2026-80926","epss":"0.004500000","percentile":"0.384810000","score_date":"2026-09-22","updated_at":"2026-09-23 00:06:34"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/smb/server/oplock.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"5de0527f782430b1109a447646e32033ad018a6a","status":"affected","version":"1ff58dcfcab434ebb51649da33774fbb8e1f7b67","versionType":"git"},{"lessThan":"c8279ae8df68cce9cd3b785e85f7a86c80a46e78","status":"affected","version":"e735dbd489e3ea02be78dba991056fe1138be51e","versionType":"git"},{"lessThan":"8cc98db4fc590e6c7d9db6529320982ee16c5d1d","status":"affected","version":"b003086d76968298f22e7cf62239833b5a3a06b1","versionType":"git"},{"lessThan":"0e753899627b5e28a9fea8bca98262a6f65a2452","status":"affected","version":"b003086d76968298f22e7cf62239833b5a3a06b1","versionType":"git"},{"status":"affected","version":"945a86b21b40fb17183f5b27461baa6f03e2467f","versionType":"git"},{"status":"affected","version":"75e33deda658c1ab3a9336cbdb1436536f9b3660","versionType":"git"},{"lessThan":"6.12.111","status":"affected","version":"6.12.94","versionType":"semver"},{"lessThan":"6.18.51","status":"affected","version":"6.18.36","versionType":"semver"},{"lessThan":"6.7","status":"affected","version":"6.6.143","versionType":"semver"},{"lessThan":"7.1","status":"affected","version":"7.0.13","versionType":"semver"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/smb/server/oplock.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"7.1"},{"lessThan":"7.1","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.111","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.51","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.111","versionStartIncluding":"6.12.94","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.51","versionStartIncluding":"6.18.36","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.5","versionStartIncluding":"7.1","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc2","versionStartIncluding":"7.1","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.6.143","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"7.0.13","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix use-after-free in oplock break notification\n\nsmb2_oplock_break_noti() reads opinfo->conn without any lock and\ndereferences it after two allocations which may sleep.  When the\ndurable handle owning the oplock is disconnected, session_fd_check()\nclears opinfo->conn and drops its conn reference under ci->m_lock, and\nthe last ksmbd_conn_put() frees the connection.  A break triggered by\nanother connection that races with the teardown can then resurrect the\nfreed connection: ksmbd_conn_get() is a plain atomic_inc, and the\nqueued break work later dereferences the stale conn via\nksmbd_conn_write(), a use-after-free reachable by any authenticated\nclient holding a durable batch oplock.\n\nThread the caller's inode into the notification path instead of taking\na new reference on it.  Every caller of oplock_break() already holds a\nlive ksmbd_file (or an explicit ksmbd_inode_lookup_lock() reference,\nin the parent lease break paths) on the inode that owns the break\ntarget's oplock list, so ci cannot be freed during the call, and its\nlock can be taken without dereferencing opinfo->o_fp, which a\nconcurrent close may free.  Select and pin the connection under\nci->m_lock, the same lock session_fd_check() and\nksmbd_reopen_durable_fd() use to update opinfo->conn, so a concurrent\ndetach either loses the race to the clear or keeps the connection\nalive until the notification work releases it.  Transfer the reference\nto the work item and release it on allocation failures."}],"metrics":[{"cvssV3_1":{"baseScore":9.8,"baseSeverity":"CRITICAL","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"scenarios":[{"lang":"en","value":"AV:N - ksmbd is the in-kernel SMB server on TCP/445; smb2_oplock_break_noti() is reached from remote SMB2 CREATE/WRITE/truncate that breaks a durable batch oplock, and the racing teardown is a remote disconnect or SMB2 LOGOFF, so a network peer fully drives the UAF.\nAC:L - The attacker controls both sides of the race: one connection holds a durable batch oplock while a second opens the same file to force oplock_break(), and dropping the first connection runs session_fd_check() during the sleeping allocations before ksmbd_conn_get(); the window is retryable.\nPR:N - ksmbd shares are commonly exposed with guest/anonymous mapping, so a remote client can SESSION_SETUP, TREE_CONNECT, CREATE a durable batch oplock, and trigger the racing disconnect without a privileged host account; no meaningful credential gate protects this path.\nUI:N - No victim action is required; the attacker opens both SMB connections, requests the durable batch oplock, forces the conflicting open, and drops the first connection entirely on their own.\nS:U - The freed ksmbd_conn and resulting kernel heap corruption stay within the ksmbd/kernel security authority on the SMB server host; this is not a VM, IOMMU, or sandbox escape.\nC:H - Use-after-free of struct ksmbd_conn lets the attacker reclaim the slab object; __smb2_oplock_break_noti() then reads conn->transport and related fields from attacker-controlled memory, enabling kernel pointer and data disclosure.\nI:H - ksmbd_conn_write() calls conn->transport->ops->writev and ksmbd_conn_lock() on the freed object, so heap spraying the reclaimed ksmbd_conn yields an arbitrary function-pointer call and mutex writes into attacker-chosen memory.\nA:H - Even without a fully controlled exploit, using a freed ksmbd_conn (mutex lock, transport dereference, r_count/waitqueue) causes kernel memory corruption, oops, or panic and takes down the host."}]}],"providerMetadata":{"dateUpdated":"2026-09-21T13:14:19.421Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/5de0527f782430b1109a447646e32033ad018a6a"},{"url":"https://git.kernel.org/stable/c/c8279ae8df68cce9cd3b785e85f7a86c80a46e78"},{"url":"https://git.kernel.org/stable/c/8cc98db4fc590e6c7d9db6529320982ee16c5d1d"},{"url":"https://git.kernel.org/stable/c/0e753899627b5e28a9fea8bca98262a6f65a2452"}],"title":"ksmbd: fix use-after-free in oplock break notification","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-80926","datePublished":"2026-09-11T19:37:29.855Z","dateReserved":"2026-08-26T14:34:25.802Z","dateUpdated":"2026-09-21T13:14:19.421Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-11 20:18:56","lastModifiedDate":"2026-09-21 14:17:21","problem_types":[],"metrics":{"cvssMetricV31":[{"source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","baseScore":9.8,"baseSeverity":"CRITICAL","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":3.9,"impactScore":5.9}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"80926","Ordinal":"1","Title":"ksmbd: fix use-after-free in oplock break notification","CVE":"CVE-2026-80926","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"80926","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix use-after-free in oplock break notification\n\nsmb2_oplock_break_noti() reads opinfo->conn without any lock and\ndereferences it after two allocations which may sleep.  When the\ndurable handle owning the oplock is disconnected, session_fd_check()\nclears opinfo->conn and drops its conn reference under ci->m_lock, and\nthe last ksmbd_conn_put() frees the connection.  A break triggered by\nanother connection that races with the teardown can then resurrect the\nfreed connection: ksmbd_conn_get() is a plain atomic_inc, and the\nqueued break work later dereferences the stale conn via\nksmbd_conn_write(), a use-after-free reachable by any authenticated\nclient holding a durable batch oplock.\n\nThread the caller's inode into the notification path instead of taking\na new reference on it.  Every caller of oplock_break() already holds a\nlive ksmbd_file (or an explicit ksmbd_inode_lookup_lock() reference,\nin the parent lease break paths) on the inode that owns the break\ntarget's oplock list, so ci cannot be freed during the call, and its\nlock can be taken without dereferencing opinfo->o_fp, which a\nconcurrent close may free.  Select and pin the connection under\nci->m_lock, the same lock session_fd_check() and\nksmbd_reopen_durable_fd() use to update opinfo->conn, so a concurrent\ndetach either loses the race to the clear or keeps the connection\nalive until the notification work releases it.  Transfer the reference\nto the work item and release it on allocation failures.","Type":"Description","Title":"ksmbd: fix use-after-free in oplock break notification"}]}}}