From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sourceware-bugzilla@sourceware.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 440423858D20; Thu, 11 Apr 2024 12:16:55 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 440423858D20
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org;
	s=default; t=1712837815;
	bh=6fOV7vFLDwwK+Adbgqd9OkwTr1UQpicbgVNaCpqLnlw=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=BCItAgDtPNXvhKziBmb4vQINFqd8N15MJs3zx/y/CcuQTJ2uY+hO2Z6rrVYL1KWUN
	 QFJesZFGQgXP63VSZ9rTIm7t9F9S/rad0JEE6whfzpPDDTRlAEE6301SPP/jXfsL7b
	 tvYx0Tu8+Y1ISo6XGXunGHbMqg5xdd5OX/hPzmlM=
From: "N1nEmAn at proton dot me" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/31631] [gdb/python] inferior.read_memory:
 internal-error: virtual memory exhausted
Date: Thu, 11 Apr 2024 12:16:54 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: python
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: N1nEmAn at proton dot me
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-31631-4717-pk4iKQizyr@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-31631-4717@http.sourceware.org/bugzilla/>
References: <bug-31631-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
List-Id: <gdb-prs.sourceware.org>

https://sourceware.org/bugzilla/show_bug.cgi?id=3D31631

--- Comment #9 from N1nEmAn <N1nEmAn at proton dot me> ---
(In reply to Tom de Vries from comment #8)
> (In reply to N1nEmAn from comment #7)
> > (In reply to Tom de Vries from comment #6)
> > > > just run gdb and source the poc can make the memory corrupt/exhaust=
ed
> > >=20
> > > I'm not sure where you see memory corruption.
> > >=20
> > > I'm updating $subject to make the failure mode more clear.
> >=20
> > you are right. sorry for my unclear descreption.
>=20
> No problem, thanks for reporting this PR.

Thank you for your recognition. We look forward to your team's resolution of
this issue.
Additionally, I have a question. Can we apply for a CVE for this vulnerabil=
ity
through MITRE? Or is there another process? I didn't see Sourceware on the =
CNA
list, but I only saw Glibc.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=