{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-89630", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2026-09-11T19:38:34.738Z", "datePublished": "2026-09-11T19:45:25.697Z", "dateUpdated": "2026-09-11T19:45:25.697Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-09-11T19:45:25.697Z"}, "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: restore the data_offset bound in is_valid_oplock_break()\n\nCommit 83bfbd0bb902 (\"cifs: Remove the RFC1002 header from smb_hdr\")\nchanged the quantity this bound is measured against. It used to be\nsrv->total_read minus the 4-byte RFC1002 preamble that total_read then\nincluded, so it was the SMB message length. The same commit stopped\ncounting the preamble, and the mechanical substitution to\nsrv->total_read - srv->pdu_size left an expression that is identically\nzero: standard_receive3() reads MID_HEADER_SIZE() bytes and then exactly\npdu_length - MID_HEADER_SIZE() more, adding both to total_read.\n\nlen is therefore 0, the subtraction below it wraps, and no __u32\nDataOffset can exceed the result, so the check from commit 097f5863b1a0\n(\"cifs: read overflow in is_valid_oplock_break()\") no longer rejects\nanything. Use total_read, which is now the message length on its own."}], "affected": [{"product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["fs/smb/client/smb1misc.c"], "versions": [{"version": "83bfbd0bb9025f98fa62b44f93bd67466773d1db", "lessThan": "5b16a1967a01ad4496a7206a87c3eb16f1df2b05", "status": "affected", "versionType": "git"}, {"version": "83bfbd0bb9025f98fa62b44f93bd67466773d1db", "lessThan": "ba22f575de9deeae4ae0859ca4315a7698226237", "status": "affected", "versionType": "git"}]}, {"product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["fs/smb/client/smb1misc.c"], "versions": [{"version": "6.19", "status": "affected"}, {"version": "0", "lessThan": "6.19", "status": "unaffected", "versionType": "semver"}, {"version": "7.2.4", "lessThanOrEqual": "7.2.*", "status": "unaffected", "versionType": "semver"}, {"version": "7.3-rc1", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix"}]}], "cpeApplicability": [{"nodes": [{"operator": "OR", "negate": false, "cpeMatch": [{"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.19", "versionEndExcluding": "7.2.4"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.19", "versionEndExcluding": "7.3-rc1"}]}]}], "references": [{"url": "https://git.kernel.org/stable/c/5b16a1967a01ad4496a7206a87c3eb16f1df2b05"}, {"url": "https://git.kernel.org/stable/c/ba22f575de9deeae4ae0859ca4315a7698226237"}], "title": "smb: client: restore the data_offset bound in is_valid_oplock_break()", "x_generator": {"engine": "bippy-1.2.0"}}}}

{}

{"affected": [{"affectedData": [{"defaultStatus": "unaffected", "product": "Linux", "programFiles": ["fs/smb/client/smb1misc.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"lessThan": "5b16a1967a01ad4496a7206a87c3eb16f1df2b05", "status": "affected", "version": "83bfbd0bb9025f98fa62b44f93bd67466773d1db", "versionType": "git"}, {"lessThan": "ba22f575de9deeae4ae0859ca4315a7698226237", "status": "affected", "version": "83bfbd0bb9025f98fa62b44f93bd67466773d1db", "versionType": "git"}]}, {"defaultStatus": "affected", "product": "Linux", "programFiles": ["fs/smb/client/smb1misc.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"status": "affected", "version": "6.19"}, {"lessThan": "6.19", "status": "unaffected", "version": "0", "versionType": "semver"}, {"lessThanOrEqual": "7.2.*", "status": "unaffected", "version": "7.2.4", "versionType": "semver"}, {"lessThanOrEqual": "*", "status": "unaffected", "version": "7.3-rc1", "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\nsmb: client: restore the data_offset bound in is_valid_oplock_break()\n\nCommit 83bfbd0bb902 (\"cifs: Remove the RFC1002 header from smb_hdr\")\nchanged the quantity this bound is measured against. It used to be\nsrv->total_read minus the 4-byte RFC1002 preamble that total_read then\nincluded, so it was the SMB message length. The same commit stopped\ncounting the preamble, and the mechanical substitution to\nsrv->total_read - srv->pdu_size left an expression that is identically\nzero: standard_receive3() reads MID_HEADER_SIZE() bytes and then exactly\npdu_length - MID_HEADER_SIZE() more, adding both to total_read.\n\nlen is therefore 0, the subtraction below it wraps, and no __u32\nDataOffset can exceed the result, so the check from commit 097f5863b1a0\n(\"cifs: read overflow in is_valid_oplock_break()\") no longer rejects\nanything. Use total_read, which is now the message length on its own."}], "id": "CVE-2026-89630", "lastModified": "2026-09-11T20:19:48.517", "metrics": {}, "published": "2026-09-11T20:19:48.517", "references": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/5b16a1967a01ad4496a7206a87c3eb16f1df2b05"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/ba22f575de9deeae4ae0859ca4315a7698226237"}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "vulnStatus": "Received"}

{"bugzilla": {"description": "kernel: Linux kernel: SMB client read overflow vulnerability in oplock break handling", "id": "2532051", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2532051"}, "csaw": false, "cvss3": {"cvss3_base_score": "6.3", "cvss3_scoring_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:H", "status": "draft"}, "cwe": "CWE-125", "details": ["A flaw was found in the Linux kernel's Server Message Block (SMB) client. An incorrect calculation of the `data_offset` bound in the `is_valid_oplock_break()` function can lead to a read overflow. This vulnerability allows a malicious SMB server to potentially trigger an out-of-bounds read, which could result in information disclosure or a denial of service."], "name": "CVE-2026-89630", "package_state": [{"cpe": "cpe:/a:redhat:openshift:4", "fix_state": "Fix deferred", "package_name": "openshift/ose-rhel-coreos-8", "product_name": "Red Hat OpenShift Container Platform 4"}, {"cpe": "cpe:/a:redhat:openshift:4", "fix_state": "Fix deferred", "package_name": "openshift/ose-rhel-coreos-9", "product_name": "Red Hat OpenShift Container Platform 4"}], "public_date": "2026-09-11T19:45:25Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2026-89630\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-89630\nhttps://git.kernel.org/stable/c/5b16a1967a01ad4496a7206a87c3eb16f1df2b05\nhttps://git.kernel.org/stable/c/ba22f575de9deeae4ae0859ca4315a7698226237"], "threat_severity": "Moderate"}

{}