Bug 1524530 – CVE-2017-17426 glibc: Integer overflow with enabled tcache

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1524530 - (CVE-2017-17426) CVE-2017-17426 glibc: Integer overflow with enabled tcache

Summary:	CVE-2017-17426 glibc: Integer overflow with enabled tcache

Status:	NEW

Aliases:	CVE-2017-17426

Product:	Security Response
Classification:	Other
Component:	vulnerability (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Product Security
QA Contact:
Docs Contact:

URL:
Whiteboard:	impact=moderate,public=20171031,repor...
Keywords:	Security

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-12-11 11:19 EST by Andrej Nemec
Modified:	2018-02-06 14:29 EST (History)
CC List:	13 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Andrej Nemec 2017-12-11 11:19:43 EST

The malloc function in the GNU C Library (aka glibc or libc6) 2.26 could return a memory block that is too small if an attempt is made to allocate an object whose size is close to SIZE_MAX, potentially leading to a subsequent heap overflow. This occurs because the per-thread cache (aka tcache) feature enables a code path that lacks an integer overflow check.

Upstream issue:

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

Upstream patch:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=34697694e8a93b325b18f25f7dcded55d6baeaf6

Introduced by:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=d5c3fafc4307c9b7a4c7d5cb381fcdbfad340bcc

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