Bug 1184166 – VUL-0: CVE-2021-29266: kernel-source: drivers/vhost/vdpa.c has a use-after-free

Bug 1184166 - (CVE-2021-29266) VUL-0: CVE-2021-29266: kernel-source: drivers/vhost/vdpa.c has a use-after-free

(CVE-2021-29266)
Summary:	VUL-0: CVE-2021-29266: kernel-source: drivers/vhost/vdpa.c has a use-after-free

Status:	RESOLVED INVALID

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:	Security Team bot
QA Contact:	Security Team bot

URL:	https://smash.suse.de/issue/280595/
Whiteboard:	CVSSv3.1:SUSE:CVE-2021-29266:4.4:(AV:...
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Create test case

Clone This Bug

Reported:	2021-03-30 14:31 UTC by Alexander Bergmann
Modified:	2022-05-03 12:55 UTC (History)
CC List:	3 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 Alexander Bergmann 2021-03-30 14:31:50 UTC

CVE-2021-29266

An issue was discovered in the Linux kernel before 5.11.9. drivers/vhost/vdpa.c
has a use-after-free because v->config_ctx has an invalid value upon re-opening
a character device, aka CID-f6bbf0010ba0.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-29266
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-29266
https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.11.9
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f6bbf0010ba004f5e90c7aefdebc0ee4bd3283b9

Comment 1 Takashi Iwai 2021-03-31 09:32:54 UTC

The fix commit suggests:
  Fixes: 776f395004d8 ("vhost_vdpa: Support config interrupt in vdpa")
which is in 5.8-rc1 kernel.  And this isn't backported to any SLE branches.

TW kernel already got the fix via 5.11.9 stable tree.

Reassigned back to security team.

Comment 2 Carlos López 2022-05-03 12:55:32 UTC

Closing, as we are not affected.