All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99549: smb: client: do not pass a NULL buf to is_oplock_break()
Date: Thu, 19 Nov 2026 15:27:27 +0100	[thread overview]
Message-ID: <2026111925-CVE-2026-99549-45e1@gregkh> (raw)

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

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

smb: client: do not pass a NULL buf to is_oplock_break()

receive_encrypted_read() sets *num_mids = 1 and never writes the
caller's bufs[]. Offload returns -1 with *num_mids = 0, so the
demultiplex thread skips the frame. The inline decrypt path
returns 0 even when smb2_find_mid() fails.

cifs_demultiplex_thread() then treats mids[i] == NULL as an
oplock break and calls is_oplock_break(bufs[i], server) with
bufs[i] still NULL. smb2_is_valid_oplock_break() reads
hdr.Command at offset 12 and oopses.

A large encrypted READ whose MessageId does not match is enough
to panic cifsd.

    Oops: general protection fault, probably for non-canonical address
    0xdffffc0000000001: 0000 [#1] SMP KASAN PTI
    KASAN: null-ptr-deref in range
    [0x0000000000000008-0x000000000000000f]
    CPU: 0 PID: 100 Comm: cifsd
    RIP: smb2_is_valid_oplock_break+0xc8/0x2270 [cifs]
    cifs_demultiplex_thread
    Kernel panic - not syncing: Fatal exception

Return -1 when inline decrypt finds no mid, and skip
is_oplock_break() plus the unknown-frame dump when bufs[i]
is NULL. receive_encrypted_standard() already assigns
bufs[*num_mids].

The Linux kernel CVE team has assigned CVE-2026-99549 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 4.11 with commit c42a6abe3012832a68a371dabe17c2ced97e62ad and fixed in 6.12.117 with commit 6c1ccd31b3a995a1a73e10e7bc8b6d96cf382241
	Issue introduced in 4.11 with commit c42a6abe3012832a68a371dabe17c2ced97e62ad and fixed in 6.18.61 with commit ee793cc8dcd58ed9afa0a69a84d66df4f8eacd88
	Issue introduced in 4.11 with commit c42a6abe3012832a68a371dabe17c2ced97e62ad and fixed in 7.3.2 with commit 4bf4fb7f323402df1c57982365c8ac2498b89d10
	Issue introduced in 4.11 with commit c42a6abe3012832a68a371dabe17c2ced97e62ad and fixed in 7.4-rc1 with commit 2225ab306575e424b3dad2ee1be2521c89249d15

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-99549
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	fs/smb/client/connect.c
	fs/smb/client/smb2ops.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/6c1ccd31b3a995a1a73e10e7bc8b6d96cf382241
	https://git.kernel.org/stable/c/ee793cc8dcd58ed9afa0a69a84d66df4f8eacd88
	https://git.kernel.org/stable/c/4bf4fb7f323402df1c57982365c8ac2498b89d10
	https://git.kernel.org/stable/c/2225ab306575e424b3dad2ee1be2521c89249d15

                 reply	other threads:[~2026-11-19 15:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2026111925-CVE-2026-99549-45e1@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=cve@kernel.org \
    --cc=gregkh@kernel.org \
    --cc=linux-cve-announce@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.