Bug 1203330 – VUL-0: CVE-2022-38457: kernel: use-after-free found in 'vmw_cmd_res_check' in vmwgfx driver

Bug 1203330 - (CVE-2022-38457) VUL-0: CVE-2022-38457: kernel: use-after-free found in 'vmw_cmd_res_check' in vmwgfx driver

(CVE-2022-38457)
Summary:	VUL-0: CVE-2022-38457: kernel: use-after-free found in 'vmw_cmd_res_check' in...

Status:	NEW

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

Priority:	P3 - Medium Severity: Normal
Target Milestone:	---
Assigned To:	Thomas Zimmermann
QA Contact:	Security Team bot

URL:	https://smash.suse.de/issue/341982/
Whiteboard:	CVSSv3.1:SUSE:CVE-2022-38457:5.5:(AV:...
Keywords:

Depends on:	CVE-2022-40133
Blocks:
	Show dependency tree / graph

Create test case

Clone This Bug

Reported:	2022-09-12 08:51 UTC by Robert Frohl
Modified:	2023-03-23 18:31 UTC (History)
CC List:	8 users (show)

See Also:	CVE-2022-40133
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 Robert Frohl 2022-09-12 08:51:59 UTC

CVE-2022-38457

A use-after-free(UAF) vulnerability was found in function 'vmw_cmd_res_check' in
drivers/gpu/vmxgfx/vmxgfx_execbuf.c in Linux kernel's vmwgfx driver with device
file '/dev/dri/renderD128 (or Dxxx)'. This flaw allows a local attacker with a
user account on the system to gain privilege, causing a denial of service(DoS).

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2022-38457
https://www.cve.org/CVERecord?id=CVE-2022-38457
https://bugzilla.openanolis.cn/show_bug.cgi?id=2074

Comment 7 Takashi Iwai 2022-10-21 06:48:57 UTC

A gentle reminder from Kernel Security Sentinel:
is there any progress in the upstream about this bug?

Comment 8 Petr Mladek 2022-11-16 09:02:42 UTC

I guess that the situation here is the same as in the bug #1203517, e.i. the fix is not available in upstream yet. Am I right, please?

Comment 9 Thomas Zimmermann 2022-11-16 10:20:59 UTC

(In reply to Petr Mladek from comment #8)
> I guess that the situation here is the same as in the bug #1203517, e.i. the
> fix is not available in upstream yet. Am I right, please?

No changes here.