CVE-2026-99383: Linux kernel · smb: client: reclaim credits for decrypted reads with no matching mid
Source GCVE Database
Not known to be exploited · fixed in b3f511aa7f45ff9ab1abc38d133e05b919563aaf : update Linux kernel when convenient.
Data as of 19 Nov 2026, 16:20 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in b3f511aa7f45ff9ab1abc38d133e05b919563aaf, 78f73985846465a25a7bd1d89904053661f3ca92, 9b3473e7bc5ec104c37faa7f7c9092914d97f076
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 b3f511aa7f45ff9ab1abc38d133e05b919563aaf, 78f73985846465a25a7bd1d89904053661f3ca92 or 9b3473e7bc5ec104c37faa7f7c9092914d97f076.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: smb: client: reclaim credits for decrypted reads with no matching mid When a decrypted SMB2 READ response carries a MessageId that matches no outstanding request, both the inline receive_encrypted_read() and the offloaded smb2_decrypt_offload() paths drop the frame without accounting the credits the server granted in it. The plaintext unknown-frame path in cifs_demultiplex_thread() already reclaims them with smb2_add_credits_from_hdr(), so encrypted reads leak credits that the plaintext path would not. This also happens for legitimate frames - e.g. a reply that arrives after the client has timed out and dropped the mid - so over a long-lived connection the client's credit count drifts down and can eventually starve it of the ability to issue requests. The frame is AEAD-authenticated, so the granted credits in the decrypted header come from the real server and are safe to apply. Reclaim the credits from the decrypted header before dropping the frame, and export smb2_add_credits_from_hdr() so the SMB2 receive paths can use it.
References
- nvd.nist.gov/vuln/detail/CVE-2026-99383 (opens in a new tab)
- git.kernel.org/stable/c/78f73985846465a25a7bd1d89904053661f3ca92 (opens in a new tab)
- git.kernel.org/stable/c/9b3473e7bc5ec104c37faa7f7c9092914d97f076 (opens in a new tab)
- git.kernel.org/stable/c/b3f511aa7f45ff9ab1abc38d133e05b919563aaf (opens in a new tab)