Linux Test Project
 help / color / mirror / Atom feed
From: linuxtestproject.agent@gmail.com
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] lapi/prctl: add more fallback definitions
Date: Sat,  1 Aug 2026 11:27:23 +0000	[thread overview]
Message-ID: <20260801112723.9180-1-linuxtestproject.agent@gmail.com> (raw)
In-Reply-To: <20260801-cve-ghostlock-v1-1-178f698f9702@suse.com>

Hi Andrea,

On Aug 1, 2026, Andrea Cervesato wrote:
> lapi/prctl: add more fallback definitions

--- [PATCH 2/2] ---

> +	static const int try_sizes[] = {
> +		MAX_AUXV_QWORDS,
> +		MAX_AUXV_QWORDS - 4,
> +		MAX_AUXV_QWORDS - 8
> +	};
> [...]
> +		valid_auxv_size = try_sizes[i] * sizeof(uint64_t);

Could these sizes either use the native word size, or could the test be
restricted to the 64-bit architectures on which the reproducer works?

On i386, the smallest attempted size is 320 bytes, but the kernel's
saved_auxv is only 56 * sizeof(unsigned long), or 224 bytes.
prctl_set_mm_map() therefore rejects all three attempts, and setup reports
TBROK. With no supported_archs restriction, the cve runtest entry runs this
test on 32-bit x86.

Verdict - Needs revision

---
Note:

The agent can sometimes produce false positives although often its
findings are genuine. If you find issues with the review, please
comment this email or ignore the suggestions.

Regards,
LTP AI Reviewer

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2026-08-01 11:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-01 10:34 [LTP] [PATCH 0/2] Reproducer for ghostlock Andrea Cervesato
2026-08-01 10:34 ` [LTP] [PATCH 1/2] lapi/prctl: add more fallback definitions Andrea Cervesato
2026-08-01 11:27   ` linuxtestproject.agent [this message]
2026-08-03  8:11   ` Cyril Hrubis
2026-08-01 10:34 ` [LTP] [PATCH 2/2] cve: add CVE-2026-43499 reproducer Andrea Cervesato

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=20260801112723.9180-1-linuxtestproject.agent@gmail.com \
    --to=linuxtestproject.agent@gmail.com \
    --cc=andrea.cervesato@suse.de \
    --cc=ltp@lists.linux.it \
    /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