From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
gregkh@linuxfoundation.org, zohar@linux.ibm.com,
Lincoln Wallace <locnnil0@gmail.com>
Subject: Re: [PATCH 5.10.y] ima: fix out-of-bounds read in xattr_verify()
Date: Fri, 14 Aug 2026 22:33:14 -0400 [thread overview]
Message-ID: <20260814193000.14@kernel.org> (raw)
In-Reply-To: <20260813190635.1109461-1-locnnil0@gmail.com>
> The digest-length check in xattr_verify() mixes int and size_t:
>
> if (xattr_len - sizeof(xattr_value->type) - hash_start >=
> iint->ima_hash->length)
>
> sizeof() yields size_t, so the usual arithmetic conversions promote
> the whole left-hand side to unsigned 64-bit before the subtraction
> runs.
Queued for 5.10, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-08-15 2:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 13:55 FAILED: patch "[PATCH] ima: fix out-of-bounds read in xattr_verify()" failed to apply to 5.10-stable tree gregkh
2026-08-13 19:06 ` [PATCH 5.10.y] ima: fix out-of-bounds read in xattr_verify() Lincoln Wallace
2026-08-15 2:33 ` Sasha Levin [this message]
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=20260814193000.14@kernel.org \
--to=sashal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=locnnil0@gmail.com \
--cc=stable@vger.kernel.org \
--cc=zohar@linux.ibm.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