Linux Kernel up to 5.3.10 sound/core/timer.c snd_timer_open/snd_timer_close_locked use after free

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Linux Kernel up to 5.3.10. Affected by this issue is the function snd_timer_open/snd_timer_close_locked of the file sound/core/timer.c. Performing a manipulation results in use after free.
This vulnerability is known as CVE-2019-19807. Attacking locally is a requirement. No exploit is available.
It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in Linux Kernel up to 5.3.10 (Operating System). This affects the function snd_timer_open/snd_timer_close_locked of the file sound/core/timer.c. The manipulation with an unknown input leads to a use after free vulnerability. CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In the Linux kernel before 5.3.11, sound/core/timer.c has a use-after-free caused by erroneous code refactoring, aka CID-e7af6307a8a5. This is related to snd_timer_open and snd_timer_close_locked. The timeri variable was originally intended to be for a newly created timer instance, but was used for a different purpose after refactoring.
The weakness was published 12/15/2019. This vulnerability is uniquely identified as CVE-2019-19807 since 12/15/2019. An attack has to be approached locally. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.
Upgrading to version 5.3.11 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Use after freeCWE: CWE-416 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Kernel 5.3.11
Patch: git.kernel.org
Timeline
12/15/2019 🔍12/15/2019 🔍
12/16/2019 🔍
03/12/2024 🔍
Sources
Vendor: kernel.orgAdvisory: e7af6307a8a54f0b873960b32b6a644f2d0fbd97
Status: Not defined
CVE: CVE-2019-19807 (🔍)
GCVE (CVE): GCVE-0-2019-19807
GCVE (VulDB): GCVE-100-147225
Entry
Created: 12/16/2019 07:48Updated: 03/12/2024 10:04
Changes: 12/16/2019 07:48 (39), 12/16/2019 07:53 (18), 03/12/2024 10:03 (6), 03/12/2024 10:04 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.