All reports
Medium

UBUNTU-CVE-2019-19039

Affected versions

Affected versions
<4.15.0-1079.83~16.04.1
Fixed version
4.15.0-1079.83~16.04.1
Affected versions
<4.15.0-1091.101~16.04.1
Fixed version
4.15.0-1091.101~16.04.1
Affected versions
<4.15.0-1080.90~16.04.1
Fixed version
4.15.0-1080.90~16.04.1
Affected versions
*
Fixed version
Not reported
Affected versions
<4.15.0-112.113~16.04.1
Fixed version
4.15.0-112.113~16.04.1
Affected versions
<4.15.0-1050.54~16.04.1
Fixed version
4.15.0-1050.54~16.04.1
Affected versions
*
Fixed version
Not reported
Affected versions
<5.3.0-1019.21~18.04.1
Fixed version
5.3.0-1019.21~18.04.1
Affected versions
<4.15.0-1077.81
Fixed version
4.15.0-1077.81
Affected versions
<4.15.0-1091.101
Fixed version
4.15.0-1091.101
Affected versions
<5.3.0-1022.23~18.04.1
Fixed version
5.3.0-1022.23~18.04.1
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<4.15.0-1080.90
Fixed version
4.15.0-1080.90
Affected versions
<5.3.0-1020.22~18.04.1
Fixed version
5.3.0-1020.22~18.04.1
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<4.15.0-1066.69
Fixed version
4.15.0-1066.69
Affected versions
<5.3.0-1020.22~18.04.1
Fixed version
5.3.0-1020.22~18.04.1
Affected versions
*
Fixed version
Not reported
Affected versions
<5.3.0-53.47~18.04.1
Fixed version
5.3.0-53.47~18.04.1
Affected versions
<4.15.0-1069.70
Fixed version
4.15.0-1069.70
Affected versions
<4.15.0-1091.101
Fixed version
4.15.0-1091.101
Affected versions
*
Fixed version
Not reported
Affected versions
<5.3.0-1018.20~18.04.1
Fixed version
5.3.0-1018.20~18.04.1
Affected versions
<4.15.0-1048.52
Fixed version
4.15.0-1048.52
Affected versions
<5.3.0-1026.28~18.04.1
Fixed version
5.3.0-1026.28~18.04.1
Affected versions
<4.15.0-1065.69
Fixed version
4.15.0-1065.69
Affected versions
<4.15.0-1083.91
Fixed version
4.15.0-1083.91
Affected versions
<4.15.0-109.110
Fixed version
4.15.0-109.110
Affected versions
<5.4.0-1011.11
Fixed version
5.4.0-1011.11
Affected versions
*
Fixed version
Not reported
Affected versions
<5.4.0-1012.12
Fixed version
5.4.0-1012.12
Affected versions
<5.4.0-1011.11
Fixed version
5.4.0-1011.11
Affected versions
*
Fixed version
Not reported
Affected versions
<5.4.0-1011.11
Fixed version
5.4.0-1011.11
Affected versions
<5.6.0-1010.10
Fixed version
5.6.0-1010.10
Affected versions
<5.4.0-1011.11
Fixed version
5.4.0-1011.11
Affected versions
*
Fixed version
Not reported
Affected versions
<5.4.0-1011.11
Fixed version
5.4.0-1011.11
Affected versions
<5.4.0-26.30
Fixed version
5.4.0-26.30
Affected versions
<5.4.0-31.35
Fixed version
5.4.0-31.35
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<4.15.0-1091.101~14.04.1
Fixed version
4.15.0-1091.101~14.04.1
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<5.15.0-1114.123~20.04.1
Fixed version
5.15.0-1114.123~20.04.1
Affected versions
*
Fixed version
Not reported
Affected versions
<4.15.0-2022.22
Fixed version
4.15.0-2022.22
Affected versions
<4.15.0-2006.7
Fixed version
4.15.0-2006.7
Affected versions
<4.15.0-1037.42
Fixed version
4.15.0-1037.42
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported

Description

__btrfs_free_extent in fs/btrfs/extent-tree.c in the Linux kernel through 5.3.12 calls btrfs_print_leaf in a certain ENOENT case, which allows local users to obtain potentially sensitive information about register values via the dmesg program. NOTE: The BTRFS development team disputes this issues as not being a vulnerability because “1) The kernel provide facilities to restrict access to dmesg - dmesg_restrict=1 sysctl option. So it's really up to the system administrator to judge whether dmesg access shall be disallowed or not. 2) WARN/WARN_ON are widely used macros in the linux kernel. If this CVE is considered valid this would mean there are literally thousands CVE lurking in the kernel - something which clearly is not the case.

Links