{ "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-10-11T13:47:14.848Z" }, "containers": { "cna": { "providerMetadata": { "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-10-11T13:47:14.848Z" }, "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." } ], "metrics": [ { "cvssV3_1": { "version": "3.1", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H", "baseScore": 9.1, "baseSeverity": "CRITICAL" }, "scenarios": [ { "lang": "en", "value": "AV:N - The flaw is in the in-kernel SMB1 client demultiplex path: a remote peer sends an unsolicited SMB_COM_NT_TRANSACT response over TCP/445 and cifs_demultiplex_thread() calls is_valid_oplock_break() on unmatched frames, so a malicious or compromised SMB server (or MITM) reaches it via network protocol data.\nAC:L - The attacker fully controls Command, Flags, ByteCount, and DataOffset in a single unsolicited frame; the broken bound wraps so any DataOffset is accepted and the resulting heap over-read is deterministic, with no race or condition the attacker cannot influence once the client is on the SMB1 connection.\nPR:N - A matching MID, session setup, or tree connect is not required: after negotiate, an unmatched NT_TRANSACT+RESPONSE frame is treated as an oplock/dnotify break before authentication, so the malicious server needs no credentials or privileges on the client host.\nUI:N - On a persistent SMB1 mount (cifsroot, automount, or an already-mounted legacy NAS share) the cifsd thread processes unsolicited frames after the existing connection or reconnect, so no additional victim action is required at attack time.\nS:U - The out-of-bounds/use-after-free read occurs in kernel heap used by the CIFS client on the same host kernel security authority and does not cross a VM, IOMMU, or sandbox boundary.\nC:H - Attacker-controlled DataOffset displaces file_notify_information into adjacent or freed cifs_small_rq slab objects (KASAN use-after-free read), and printing FileName with %s can walk unbounded kernel memory, so the disclosure is not limited to a few bounded bytes.\nI:N - The displaced pointer is only read (Action and FileName for a debug print); the bug does not write through that pointer or otherwise provide a kernel memory-modification or control-flow primitive.\nA:H - The KASAN-confirmed slab use-after-free and unmapped over-read run in the cifsd demultiplex thread and can oops or panic the kernel, and a malicious peer can repeat the unsolicited frame to retrigger the crash." } ] } ], "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" }, { "version": "78e718c5aa146063cd70d2cc68297c3ac41f31ee", "status": "affected", "versionType": "git" }, { "version": "6.18.56", "lessThan": "6.19", "status": "affected", "versionType": "semver" } ] }, { "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" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.18.56" } ] } ] } ], "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" } } } }