Bug 985433 – p11-kit: memdup inconsistent

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 985433 - p11-kit: memdup inconsistent

Summary:	p11-kit: memdup inconsistent

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	p11-kit (Show other bugs)
Sub Component:
Version:	6.5
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	Stef Walter
QA Contact:	Aleš Mareček
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	983512
	Show dependency tree / graph

Reported:	2013-07-17 09:20 EDT by Florian Weimer
Modified:	2013-11-21 06:40 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:	p11-kit-0.18.5-1.el6
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2013-11-21 06:40:13 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Don't call memdup with zero length or NULL pointer (2.50 KB, patch) 2013-07-17 14:30 EDT, Stef Walter	no flags	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHEA-2013:1626	normal	SHIPPED_LIVE	new packages: p11-kit	2013-11-20 16:53:58 EST

Groups: None (edit)

Description Florian Weimer 2013-07-17 09:20:42 EDT

memdup() usage is inconsistent.  Some alternative implementations require that the source pointer is not NULL.

common/attrs.c:attrs_build() might actually trigger this.

Comment 2 Stef Walter 2013-07-17 14:30:48 EDT

Created attachment 774900 [details]
Don't call memdup with zero length or NULL pointer

Comment 3 Stef Walter 2013-07-18 09:55:58 EDT

Pushed to p11-kit git stable branch, released as part of p11-kit 0.18.5. Package built for RHEL 6.5.

Comment 10 errata-xmlrpc 2013-11-21 06:40:13 EST

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2013-1626.html

Note You need to log in before you can comment on or make changes to this bug.