From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2022-49366: ksmbd: fix reference count leak in smb_check_perm_dacl()
Date: Wed, 26 Feb 2025 03:10:40 +0100 [thread overview]
Message-ID: <2025022645-CVE-2022-49366-d901@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix reference count leak in smb_check_perm_dacl()
The issue happens in a specific path in smb_check_perm_dacl(). When
"id" and "uid" have the same value, the function simply jumps out of
the loop without decrementing the reference count of the object
"posix_acls", which is increased by get_acl() earlier. This may
result in memory leaks.
Fix it by decreasing the reference count of "posix_acls" before
jumping to label "check_access_bits".
The Linux kernel CVE team has assigned CVE-2022-49366 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.15 with commit 777cad1604d68ed4379ec899d1f7d2f6a29f01f0 and fixed in 5.15.47 with commit cf824b95c12a1abacadbc2d069931963221a3414
Issue introduced in 5.15 with commit 777cad1604d68ed4379ec899d1f7d2f6a29f01f0 and fixed in 5.17.15 with commit 248d71b440aef829f5cc5f6545ca113ef5062900
Issue introduced in 5.15 with commit 777cad1604d68ed4379ec899d1f7d2f6a29f01f0 and fixed in 5.18.4 with commit 9758a6653c27867d810de02b4e5697163dda9883
Issue introduced in 5.15 with commit 777cad1604d68ed4379ec899d1f7d2f6a29f01f0 and fixed in 5.19 with commit d21a580dafc69aa04f46e6099616146a536b0724
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-2022-49366
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/ksmbd/smbacl.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/cf824b95c12a1abacadbc2d069931963221a3414
https://git.kernel.org/stable/c/248d71b440aef829f5cc5f6545ca113ef5062900
https://git.kernel.org/stable/c/9758a6653c27867d810de02b4e5697163dda9883
https://git.kernel.org/stable/c/d21a580dafc69aa04f46e6099616146a536b0724
reply other threads:[~2025-02-26 2:13 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=2025022645-CVE-2022-49366-d901@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@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.