FKIE_CVE-2026-80926
Vulnerability from fkie_nvd - Published: 2026-09-11 20:18 - Updated: 2026-09-13 07:16
Severity
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 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.
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"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": "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": "1ff58dcfcab434ebb51649da33774fbb8e1f7b67",
"versionType": "git"
},
{
"status": "affected",
"version": "75e33deda658c1ab3a9336cbdb1436536f9b3660",
"versionType": "git"
},
{
"lessThan": "6.18.51",
"status": "affected",
"version": "6.18.36",
"versionType": "semver"
},
{
"lessThan": "6.7",
"status": "affected",
"version": "6.6.143",
"versionType": "semver"
},
{
"lessThan": "6.13",
"status": "affected",
"version": "6.12.94",
"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.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"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"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-\u003econn 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-\u003econn and drops its conn reference under ci-\u003em_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\u0027s 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\u0027s oplock list, so ci cannot be freed during the call, and its\nlock can be taken without dereferencing opinfo-\u003eo_fp, which a\nconcurrent close may free. Select and pin the connection under\nci-\u003em_lock, the same lock session_fd_check() and\nksmbd_reopen_durable_fd() use to update opinfo-\u003econn, 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."
}
],
"id": "CVE-2026-80926",
"lastModified": "2026-09-13T07:16:59.460",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"type": "Secondary"
}
]
},
"published": "2026-09-11T20:18:56.257",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/0e753899627b5e28a9fea8bca98262a6f65a2452"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/8cc98db4fc590e6c7d9db6529320982ee16c5d1d"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/c8279ae8df68cce9cd3b785e85f7a86c80a46e78"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…