Bug 1743591 (CVE-2019-15214) - CVE-2019-15214 kernel: use-after-free in sound/core/init.c and sound/core/info.c
Summary: CVE-2019-15214 kernel: use-after-free in sound/core/init.c and sound/core/info.c
Alias: CVE-2019-15214
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1743592 1809900 1809901 1809902 1809903 1809904
Blocks: 1743593
TreeView+ depends on / blocked
Reported: 2019-08-20 09:18 UTC by Dhananjay Arunesh
Modified: 2021-10-27 10:48 UTC (History)
40 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A vulnerability was found in the Linux kernel’s core sound driver code. A use-after-free in a race condition between disconnection events could allow a local attacker who can trigger disconnection events (remove or add hardware) to crash the system, corrupt memory, or escalate privileges.
Clone Of:
Last Closed: 2021-10-27 10:48:22 UTC

Attachments (Terms of Use)

Description Dhananjay Arunesh 2019-08-20 09:18:31 UTC
A vulnerability was found in the Linux kernel. There is a use-after-free in the sound subsystem because card disconnection causes certain data structures to be deleted too early. This is related to sound/core/init.c and sound/core/info.c.

Comment 1 Dhananjay Arunesh 2019-08-20 09:19:13 UTC
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1743592]

Comment 2 Justin M. Forbes 2019-08-20 12:51:00 UTC
This was fixed for Fedora with the 5.0.10 stable updates.

Comment 5 Wade Mealing 2020-03-04 06:21:03 UTC

As the snd module will be auto-loaded when required, its use can be disabled  by preventing the module from loading with the following instructions:

# echo "install snd /bin/true" >> /etc/modprobe.d/disable-snd.conf 
The system will need to be restarted if the snd modules are loaded. In most circumstances, the snd kernel modules will be unable to be unloaded while they are is in use.

If the system requires this module to work correctly, this mitigation may not be suitable.

If you need further assistance, see KCS article https://access.redhat.com/solutions/41278 or contact Red Hat Global Support Services.

Comment 6 Wade Mealing 2020-03-04 06:38:36 UTC
So, it looks as though this flaw requires more privledges than a local account to trigger.  It requires an ability to race a register and disconnect (likely of the same device) functions which means that this needs to be a hotpluggable device.  The attacker would also need a local account that is ready to exploit the race on the system.

For this reason, I'm not convinced its rated as "Important" but I'm rating this as moderate with a reccomendation that it be fixed.

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