CVE-2026-99549: Linux kernel · smb: client: do not pass a NULL buf to is_oplock_break()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ee793cc8dcd58ed9afa0a69a84d66df4f8eacd88 : patch Linux kernel soon.
Data as of 19 Nov 2026, 15:07 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in ee793cc8dcd58ed9afa0a69a84d66df4f8eacd88, 2225ab306575e424b3dad2ee1be2521c89249d15, 6c1ccd31b3a995a1a73e10e7bc8b6d96cf382241 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade Linux kernel to ee793cc8dcd58ed9afa0a69a84d66df4f8eacd88, 2225ab306575e424b3dad2ee1be2521c89249d15, 6c1ccd31b3a995a1a73e10e7bc8b6d96cf382241 or 4bf4fb7f323402df1c57982365c8ac2498b89d10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in specific Linux kernel commits (ee793cc8dcd58ed9afa0a69a84d66df4f8eacd88, 2225ab306575e424b3dad2ee1be2521c89249d15, 6c1ccd31b3a995a1a73e10e7bc8b6d96cf382241, 4bf4fb7f323402df1c57982365c8ac2498b89d10). Users should update their Linux kernel to a version including these fixes to prevent kernel panics caused by this vulnerability.
Description
A vulnerability in the Linux kernel SMB client allows a NULL pointer to be passed to the is_oplock_break() function, causing a kernel panic. This occurs when a large encrypted READ with a mismatched MessageId triggers a NULL buffer dereference, leading to a general protection fault and system crash. The issue affects Linux kernel version 4.11 and has been fixed in specific commits.
References
- git.kernel.org/stable/c/6c1ccd31b3a995a1a73e10e7bc8b6d96cf382241 (opens in a new tab)
- git.kernel.org/stable/c/ee793cc8dcd58ed9afa0a69a84d66df4f8eacd88 (opens in a new tab)
- git.kernel.org/stable/c/4bf4fb7f323402df1c57982365c8ac2498b89d10 (opens in a new tab)
- git.kernel.org/stable/c/2225ab306575e424b3dad2ee1be2521c89249d15 (opens in a new tab)