Bug 2166322

Summary:	CVE-2023-0615 kernel: multiple issues for the Video for Linux version 2 test driver [fedora-all]
Product:	[Fedora] Fedora	Reporter:	Alex <allarkin>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	37	CC:	acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, hpa, jarodwilson, jforbes, jglisse, josef, jwboyer, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, steved
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-02-01 19:11:46 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2166287

Description Alex 2023-02-01 13:36:35 UTC

This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.

For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.

For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs

When submitting as an update, use the fedpkg template provided in the next
comment(s).  This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.

Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.

NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time.  If you need to fix the versions independent of each other,
you may clone this bug as appropriate.

Reproducers, if any, will remain confidential and never be made public, unless done so by the security team.

Comment 1 Alex 2023-02-01 13:36:40 UTC

Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug.  This will ensure that all associated bugs get updated
when new packages are pushed to stable.

=====

# bugfix, security, enhancement, newpackage (required)
type=security

# low, medium, high, urgent (required)
severity=medium

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=2166287,2166322

# Description of your update
notes=Security fix for [PUT CVEs HERE]

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=3
unstable_karma=-3

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

======

Additionally, you may opt to use the bodhi web interface to submit updates:

https://bodhi.fedoraproject.org/updates/new

Comment 2 Hans de Goede 2023-02-01 14:22:19 UTC

Quoted from comments which I added to bug 2166287 :

"""
At least in the current (6.2-rc#) kernel code the vivid test code has its own Kconfig option CONFIG_VIDEO_VIVID. So disabling that should be enough to mitigate these security issues.

Note that completely disabling CONFIG_VIDEO_V4L2 will disable all support for video input devices, including UVC webcams found on almost all laptops, so that is a bad idea.

Fedora:
-------
With the latest kernels, building vivid depends on CONFIG_MEDIA_TEST_SUPPORT and the latest Fedora kernel config has:

# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 6.1.8-200.fc37.x86_64 Kernel Configuration
...
# CONFIG_MEDIA_TEST_SUPPORT is not set

I also checked kernel-debug-core-6.1.8-100 and that also does not have CONFIG_MEDIA_TEST_SUPPORT set.

So I believe that Fedora is not affected, at least in so far as vivid is involved.
"""

To make sure other arches are not affected, I also checked the kernel-ark sources and those only have a single setting for CONFIG_MEDIA_TEST_SUPPORT:

[hans@shalem kernel-ark]$ cat redhat/configs/common/generic/CONFIG_MEDIA_TEST_SUPPORT
# CONFIG_MEDIA_TEST_SUPPORT is not set

Comment 3 Hans de Goede 2023-02-01 19:11:46 UTC

I have gotten confirmation from the upstream v4l2-core and vivid maintainer that all these issues indeed only impact vivid so and we don't build the vivid driver at all, so this can be closed as not-a-bug.

And FWIW these issues have all been fixed in the latest upstream vivid code.