Menu

Star on GitHub · 3.5k

CVE-2026-89630

9.1 · CRITICAL

In the Linux kernel, the following vulnerability has been resolved: smb: client: restore the data_offset bound in is_valid_oplock_break() Commit 83bfbd0bb902 ("cifs: Remove the RFC1002 header fro…

Published Sep 11, 2026EPSS 0.54%

Overview

CVE-2026-89630 is a critical-severity vulnerability. It was published on September 11, 2026 and has a CVSS 3.1 base score of 9.1 (CRITICAL).

This vulnerability has a CVSS 3.1 base score of 9.1, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

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

smb: client: restore the data_offset bound in is_valid_oplock_break()

Commit 83bfbd0bb902 ("cifs: Remove the RFC1002 header from smb_hdr")

changed the quantity this bound is measured against. It used to be

srv->total_read minus the 4-byte RFC1002 preamble that total_read then

included, so it was the SMB message length. The same commit stopped

counting the preamble, and the mechanical substitution to

srv->total_read - srv->pdu_size left an expression that is identically

zero: standard_receive3() reads MID_HEADER_SIZE() bytes and then exactly

pdu_length - MID_HEADER_SIZE() more, adding both to total_read.

len is therefore 0, the subtraction below it wraps, and no __u32

DataOffset can exceed the result, so the check from commit 097f5863b1a0

("cifs: read overflow in is_valid_oplock_break()") no longer rejects

anything. Use total_read, which is now the message length on its own.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-89630?

CVE-2026-89630 is a critical-severity vulnerability. It was published on September 11, 2026 and has a CVSS 3.1 base score of 9.1 (CRITICAL).

How severe is CVE-2026-89630?

This vulnerability has a CVSS 3.1 base score of 9.1, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2026-89630?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-89630?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-89630 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related CRITICAL CVEs from 2026

View all
CyberStrike v2 is here — more intelligence, greater reach