From: Greg KH <gregkh@linuxfoundation.org>
To: can-yildirim@ymail.ne.jp
Cc: "security@kernel.org" <security@kernel.org>,
"gfs2@lists.linux.dev" <gfs2@lists.linux.dev>,
"aahringo@redhat.com" <aahringo@redhat.com>,
"teigland@redhat.com" <teigland@redhat.com>
Subject: Re: [vs] DLM debugfs information disclosure via non-null-terminated resource name
Date: Wed, 11 Mar 2026 07:42:25 +0100 [thread overview]
Message-ID: <2026031118-shower-darkened-3e3a@gregkh> (raw)
In-Reply-To: <2098115699.650906.1773192682434@mail.yahoo.co.jp>
On Wed, Mar 11, 2026 at 10:31:22AM +0900, can-yildirim@ymail.ne.jp wrote:
> Dear maintainers,
> There is an possible information disclosure vulnerability in the DLM
> subsystem's debugfs interface.
debugfs is, by default, only readable by root, and contains loads of
stuff like this, as it's full of debug information on the system. So
much so that many systems do not enable it in their kernels, and others
do not mount it at all. So it's not really a problem overall from a
security point of view.
> The issue resides in the function
> print_format2_lock() in fs/dlm/debug_fs.c. When a resource name
> is exactly DLM_RESNAME_MAXLEN bytes long and contains no null
> byte, the %s format specifier in a seq_printf call reads beyond
> the intended buffer, exposing adjacent kernel memory.
That's not good, can you just send a patch for this to the developers
and mailing list and they can apply it like normal?
thanks,
greg k-h
next prev parent reply other threads:[~2026-03-11 6:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <173757593.643632.1773164229041.ref@mail.yahoo.co.jp>
[not found] ` <173757593.643632.1773164229041@mail.yahoo.co.jp>
2026-03-11 1:31 ` [vs] DLM debugfs information disclosure via non-null-terminated resource name can-yildirim
2026-03-11 6:42 ` Greg KH [this message]
2026-03-11 10:26 ` can-yildirim
2026-03-11 10:34 ` Greg KH
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=2026031118-shower-darkened-3e3a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=aahringo@redhat.com \
--cc=can-yildirim@ymail.ne.jp \
--cc=gfs2@lists.linux.dev \
--cc=security@kernel.org \
--cc=teigland@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox