From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E0A9F385742F; Tue, 6 Sep 2022 14:52:40 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E0A9F385742F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1662475960; bh=9Z4T+gDUC4umvu0qrhFzN/9W5LGsFeh7MDLkoksPsZM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=scXh54o2nl/zyD4WdQQKl+HGRrLbBIlJ+0K2due+jx9wpLvGIOrhpONMWweAw68i1 arpUCYxGr8r2lL6RfThzhuKZyu7tp+fRq0Mnq4C7hLV0lGnLWy/VFXyt/e3I7155+K R7lR/ujqeKmXINkWNzBd5ceRle8PZm/lQ684Jvrc= From: "sjon at hortensius dot net" To: glibc-bugs@sourceware.org Subject: [Bug libc/29536] syslog fail to create large messages (CVE-2022-39046) Date: Tue, 06 Sep 2022 14:52:40 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: 2.36 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: sjon at hortensius dot net X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: adhemerval.zanella at linaro dot org X-Bugzilla-Target-Milestone: 2.37 X-Bugzilla-Flags: security+ X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: 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: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29536 sjon at hortensius dot net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sjon at hortensius dot net --- Comment #6 from sjon at hortensius dot net --- it seems glibc 2.36 is completely unable to syslog messages longer than 1024 chars which is very likely related to this issue. This seems like a pretty major bug and possible reason to release a glibc update quicker then in 6 months --=20 You are receiving this mail because: You are on the CC list for the bug.=