mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Waiman Long <longman@redhat.com>
To: Naveen Kumar Chaudhary <naveen.osdev@gmail.com>,
	peterz@infradead.org, mingo@redhat.com, will@kernel.org,
	boqun@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] locking/lockdep: Fix NULL pointer dereference in __lock_set_class()
Date: Thu, 11 Jun 2026 14:15:26 -0400	[thread overview]
Message-ID: <677f24bb-158b-40dc-939b-9f6c3ad0b0ed@redhat.com> (raw)
In-Reply-To: <h2kfw43n4527x6mgi2lwpz2rieqnfzgictpv4wr5nyfjkc47co@2r5vz4uz44db>

On 6/11/26 1:38 PM, Naveen Kumar Chaudhary wrote:
> register_lock_class() can return NULL when the lock class pool is
> exhausted, graph_lock() fails, or key validation fails. However,
> __lock_set_class() uses the return value directly in pointer arithmetic
> without a NULL check:
>
>    class = register_lock_class(lock, subclass, 0);
>    hlock->class_idx = class - lock_classes;
>
> If class is NULL, this computes a wild offset that corrupts
> hlock->class_idx. The subsequent reacquire_held_locks() call will
> invoke hlock_class() with this corrupted index, leading to a NULL or
> out-of-bounds pointer dereference.
>
> Add the missing NULL check, consistent with how __lock_acquire() already
> handles this case at the same call site.
>
> Fixes: 64aa348edc61 ("lockdep: lock_set_subclass - reset a held lock's subclass")
> Signed-off-by: Naveen Kumar Chaudhary <naveen.osdev@gmail.com>
> ---
>   kernel/locking/lockdep.c | 2 ++
>   1 file changed, 2 insertions(+)
>
> diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c
> index 2d4c5bab5af8..e0de81114824 100644
> --- a/kernel/locking/lockdep.c
> +++ b/kernel/locking/lockdep.c
> @@ -5437,6 +5437,8 @@ __lock_set_class(struct lockdep_map *lock, const char *name,
>   			      lock->wait_type_outer,
>   			      lock->lock_type);
>   	class = register_lock_class(lock, subclass, 0);
> +	if (!class)
> +		return 0;
>   	hlock->class_idx = class - lock_classes;
>   
>   	curr->lockdep_depth = i;
Reviewed-by: Waiman Long <longman@redhat.com>


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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-11 17:38 Naveen Kumar Chaudhary
2026-06-11 18:15 ` Waiman Long [this message]
2026-08-03  8:09 ` [tip: locking/core] " tip-bot2 for Naveen Kumar Chaudhary

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=677f24bb-158b-40dc-939b-9f6c3ad0b0ed@redhat.com \
    --to=longman@redhat.com \
    --cc=boqun@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=naveen.osdev@gmail.com \
    --cc=peterz@infradead.org \
    --cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®