Bug 1170352 – VUL-1: CVE-2019-9444: kernel-source: pointer leak in sync debug fs driver leads to local information disclosure

Bug 1170352 - (CVE-2019-9444) VUL-1: CVE-2019-9444: kernel-source: pointer leak in sync debug fs driver leads to local information disclosure

(CVE-2019-9444)
Summary:	VUL-1: CVE-2019-9444: kernel-source: pointer leak in sync debug fs driver lea...

Status:	RESOLVED INVALID

Classification:	Novell Products
Product:	SUSE Security Incidents
Classification:	Novell Products
Component:	Incidents
Version:	unspecified
Hardware:	Other Other

Priority:	P4 - Low Severity: Normal
Target Milestone:	---
Assigned To:	Security Team bot
QA Contact:	Security Team bot

URL:	https://smash.suse.de/issue/241958/
Whiteboard:	CVSSv3.1:SUSE:CVE-2019-9444:4.4:(AV:...
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Create test case

Clone This Bug

Reported:	2020-04-23 13:54 UTC by Wolfgang Frisch
Modified:	2020-04-23 15:08 UTC (History)
CC List:	2 users (show)

See Also:
Found By:	Security Response Team
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

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

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

Description Wolfgang Frisch 2020-04-23 13:54:59 UTC

CVE-2019-9444

A vulnerability was found in sync debug fs driver in Kernel where there is a kernel pointer leak due to the usage of printf with %p. This could lead to local information disclosure with system execution privileges needed. User interaction is not needed for exploitation.

References:
https://lore.kernel.org/patchwork/patch/902287/
https://bugzilla.redhat.com/show_bug.cgi?id=1819433
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-9444
https://access.redhat.com/security/cve/CVE-2019-9444
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9444
https://source.android.com/security/bulletin/pixel/2019-09-01

Comment 2 Wolfgang Frisch 2020-04-23 15:07:10 UTC

Even though our kernels have address space randomization enabled, this should not be considered a security vulnerability in our current protection model. Root is required to trigger the information leak, and we have CONFIG_SECURITY_DMESG_RESTRICT=y set.