CVE-2018-1108
kernel drivers before version 4.17-rc1 are vulnerable to a weakness in the Linux kernel's...
kernel drivers before version 4.17-rc1 are vulnerable to a weakness in the Linux kernel's implementation of random seed data. Programs, early in the boot sequence, could use the data allocated for the seed before it was sufficiently generated.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- High
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- High
- Availability
- None
Exploit likelihood
What each source reports
CVE List Score used
5.9
kernel drivers before version 4.17-rc1 are vulnerable to a weakness in the Linux kernel's implementation of random seed data. Programs, early in the boot sequence, could use the data allocated for the seed before it was sufficiently generated.
- Record
CVE-2018-1108- CVSS 3.0
- 5.9 Medium
CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N - Weakness
- CWE-330
- Updated
- 2026-11-02
EUVDEUVD-2018-11754
5.9
kernel drivers before version 4.17-rc1 are vulnerable to a weakness in the Linux kernel's implementation of random seed data. Programs, early in the boot sequence, could use the data allocated for the seed before it was sufficiently generated.
- Record
EUVD-2018-11754- CVSS 3.0
- 5.9 Medium
CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N - Updated
- 2026-11-03
GitHub AdvisoriesGHSA-229x-53vm-m4f4
5.9
kernel drivers before version 4.17-rc1 are vulnerable to a weakness in the Linux kernel's...
kernel drivers before version 4.17-rc1 are vulnerable to a weakness in the Linux kernel's implementation of random seed data. Programs, early in the boot sequence, could use the data allocated for the seed before it was sufficiently generated.
- Record
GHSA-229x-53vm-m4f4- CVSS 3.1
- 5.9 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N - Weakness
- CWE-330
- Updated
- 2026-11-02
NVD
5.9
kernel drivers before version 4.17-rc1 are vulnerable to a weakness in the Linux kernel's implementation of random seed data. Programs, early in the boot sequence, could use the data allocated for the seed before it was sufficiently generated.
- Record
CVE-2018-1108- CVSS 3.1
- 5.9 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N - CVSS 3.0
- 5.9 Medium
CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N - CVSS 2.0
- 4.3 Medium
AV:N/AC:M/Au:N/C:N/I:P/A:N - Weakness
- CWE-330
- Updated
- 2026-11-02
OSV
5.9
kernel drivers before version 4.17-rc1 are vulnerable to a weakness in the Linux kernel's implementation of random seed data. Programs, early in the boot sequence, could use the data allocated for the seed before it was sufficiently generated.
- Record
CVE-2018-1108- CVSS 3.1
- 5.9 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N - Updated
- 2026-11-02
OSVDEBIAN-CVE-2018-1108
5.9
kernel drivers before version 4.17-rc1 are vulnerable to a weakness in the Linux kernel's implementation of random seed data. Programs, early in the boot sequence, could use the data allocated for the seed before it was sufficiently generated.
- Record
DEBIAN-CVE-2018-1108- CVSS 3.1
- 5.9 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N - Updated
- 2026-11-02
Show 6 moreShow less
OSVUBUNTU-CVE-2018-1108
5.9
kernel drivers before version 4.17-rc1 are vulnerable to a weakness in the Linux kernel's implementation of random seed data. Programs, early in the boot sequence, could use the data allocated for the seed before it was sufficiently generated.
- Record
UBUNTU-CVE-2018-1108- CVSS 3.1
- 5.9 Medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N - CVSS 3.0
- 5.9 Medium
CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N - CVSS 3.0
- 5.9 Medium
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N - Updated
- 2026-11-02
OSVMGASA-2018-0249 No score
Updated kernel packages fix security vulnerabilities
This kernel update is based on the upstream 4.14.40 and fixes at least the following security issues:
On x86, MOV SS and POP SS behave strangely if they encounter a data breakpoint. If this occurs in a KVM guest, KVM incorrectly thinks that a #DB instruction was caused by the undocumented ICEBP instruction. This results in #DB being delivered to the guest kernel with an incorrect RIP on the stack. On most guest kernels, this will allow a guest user to DoS the guest kernel or even to escalate privilege to that of the guest kernel (CVE-2018-1087).
The ext4_iget function in fs/ext4/inode.c in the Linux kernel through 4.15.15 mishandles the case of a root directory with a zero i_links_count, which allows attackers to cause a denial of service (ext4_process_freed_data NULL pointer dereference and OOPS) via a crafted ext4 image (CVE-2018-1092).
The ext4_valid_block_bitmap function in fs/ext4/balloc.c in the Linux kernel through 4.15.15 allows attackers to cause a denial of service (out-of-bounds read and system crash) via a crafted ext4 image because balloc.c and ialloc.c do not validate bitmap block numbers (CVE-2018-1093).
The ext4_fill_super function in fs/ext4/super.c in the Linux kernel through 4.15.15 does not always initialize the crc32c checksum driver, which allows attackers to cause a denial of service (ext4_xattr_inode_hash NULL pointer dereference and system crash) via a crafted ext4 image (CVE-2018-1094).
The ext4_xattr_check_entries function in fs/ext4/xattr.c in the Linux kernel through 4.15.15 does not properly validate xattr sizes, which causes misinterpretation of a size as an error code, and consequently allows attackers to cause a denial of service (get_acl NULL pointer dereference and system crash) via a crafted ext4 image (CVE-2018-1095).
Predictable Random Number Generator Weakness (CVE-2018-1108).
A null pointer dereference in dccp_write_xmit() function in net/dccp/output.c in the Linux kernel before v4.16-rc7 allows a local user to cause a denial of service by a number of certain crafted system calls (CVE-2018-1130).
The Linux kernel does not properly handle debug exceptions delivered after a stack switch operation via mov SS or pop SS instructions. During the stack switch operation, the exceptions are deferred. As a result, a local user can cause the kernel to crash (CVE-2018-8897).
WireGuard has been updated to 0.0.20180420.
For other fixes in this update, see the referenced changelogs.
- Record
MGASA-2018-0249- Updated
- 2026-11-02
OSVMGASA-2018-0265 No score
Updated kernel-linus packages fix security vulnerabilities
This kernel-linus update is based on the upstream 4.14.44 and fixes at least the following security issues:
The netfilter subsystem in the Linux kernel through 4.15.7 mishandles the case of a rule blob that contains a jump but lacks a user-defined chain, which allows local users to cause a denial of service (NULL pointer dereference) by leveraging the CAP_NET_RAW or CAP_NET_ADMIN capability, related to arpt_do_table in net/ipv4/netfilter/arp_tables.c, ipt_do_table in net/ipv4/netfilter/ip_tables.c, and ip6t_do_table in net/ipv6/netfilter/ip6_tables.c (CVE-2018-1065).
A flaw was found in the Linux kernel implementation of 32 bit syscall interface for bridging allowing a privileged user to arbitrarily write to a limited range of kernel memory. This flaw can be exploited not only by a system's privileged user (a real "root" user), but also by an attacker who is a privileged user (a "root" user) in a user+network namespace (CVE-2018-1068).
On x86, MOV SS and POP SS behave strangely if they encounter a data breakpoint. If this occurs in a KVM guest, KVM incorrectly thinks that a #DB instruction was caused by the undocumented ICEBP instruction. This results in #DB being delivered to the guest kernel with an incorrect RIP on the stack. On most guest kernels, this will allow a guest user to DoS the guest kernel or even to escalate privilege to that of the guest kernel (CVE-2018-1087).
The ext4_iget function in fs/ext4/inode.c in the Linux kernel through 4.15.15 mishandles the case of a root directory with a zero i_links_count, which allows attackers to cause a denial of service (ext4_process_freed_data NULL pointer dereference and OOPS) via a crafted ext4 image (CVE-2018-1092).
The ext4_valid_block_bitmap function in fs/ext4/balloc.c in the Linux kernel through 4.15.15 allows attackers to cause a denial of service (out-of-bounds read and system crash) via a crafted ext4 image because balloc.c and ialloc.c do not validate bitmap block numbers (CVE-2018-1093).
The ext4_fill_super function in fs/ext4/super.c in the Linux kernel through 4.15.15 does not always initialize the crc32c checksum driver, which allows attackers to cause a denial of service (ext4_xattr_inode_hash NULL pointer dereference and system crash) via a crafted ext4 image (CVE-2018-1094).
The ext4_xattr_check_entries function in fs/ext4/xattr.c in the Linux kernel through 4.15.15 does not properly validate xattr sizes, which causes misinterpretation of a size as an error code, and consequently allows attackers to cause a denial of service (get_acl NULL pointer dereference and system crash) via a crafted ext4 image (CVE-2018-1095).
Predictable Random Number Generator Weakness (CVE-2018-1108).
By mmap()ing a FUSE-backed file onto a process's memory containing command line arguments (or environment strings), an attacker can cause utilities from psutils or procps (such as ps, w) or any other program which makes a read() call to the /proc/<pid>/cmdline (or /proc/<pid>/environ) files to block indefinitely (denial of service) or for some controlled time (as a synchronization primitive for other attacks) (CVE-2018-1120).
A null pointer dereference in dccp_write_xmit() function in net/dccp/output.c in the Linux kernel before v4.16-rc7 allows a local user to cause a denial of service by a number of certain crafted system calls (CVE-2018-1130).
Speculative Store Bypass (SSB) – also known as Spectre Variant 4. Systems with microprocessors utilizing speculative execution and speculative execution of memory reads before the addresses of all prior memory writes are known may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis (CVE-2018-3639). NOTE! This fix only apply to Amd hardware so far as Intel CPUs need a fixed microcode update in order for the fix to get activated. At the time of this release we dont yet know when Intel will release new microcode.
The Linux kernel does not properly handle debug exceptions…
- Record
MGASA-2018-0265- Updated
- 2026-11-02
OSVUSN-3752-1 No score
linux, linux-aws, linux-gcp, linux-kvm, linux-raspi2 vulnerabilities
It was discovered that, when attempting to handle an out-of-memory situation, a null pointer dereference could be triggered in the Linux kernel in some circumstances. A local attacker could use this to cause a denial of service (system crash). (CVE-2018-1000200)
Wen Xu discovered that the XFS filesystem implementation in the Linux kernel did not properly validate meta-data information. An attacker could use this to construct a malicious xfs image that, when mounted, could cause a denial of service (system crash). (CVE-2018-10323)
Wen Xu discovered that the XFS filesystem implementation in the Linux kernel did not properly validate xattr information. An attacker could use this to construct a malicious xfs image that, when mounted, could cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2018-10840)
Wen Xu discovered that the ext4 filesystem implementation in the Linux kernel did not properly keep meta-data information consistent in some situations. An attacker could use this to construct a malicious ext4 image that, when mounted, could cause a denial of service (system crash). (CVE-2018-10881)
Wen Xu discovered that the ext4 filesystem implementation in the Linux kernel did not properly handle corrupted meta data in some situations. An attacker could use this to specially craft an ext4 filesystem that caused a denial of service (system crash) when mounted. (CVE-2018-1093)
Jann Horn discovered that the Linux kernel's implementation of random seed data reported that it was in a ready state before it had gathered sufficient entropy. An attacker could use this to expose sensitive information. (CVE-2018-1108)
It was discovered that the procfs filesystem did not properly handle processes mapping some memory elements onto files. A local attacker could use this to block utilities that examine the procfs filesystem to report operating system state, such as ps(1). (CVE-2018-1120)
Jann Horn discovered that the ext4 filesystem implementation in the Linux kernel did not properly keep xattr information consistent in some situations. An attacker could use this to construct a malicious ext4 image that, when mounted, could cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2018-11412)
Piotr Gabriel Kosinski and Daniel Shapira discovered a stack-based buffer overflow in the CDROM driver implementation of the Linux kernel. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2018-11506)
Shankara Pailoor discovered that a race condition existed in the socket handling code in the Linux kernel. A local attacker could use this to cause a denial of service (system crash). (CVE-2018-12232)
Shankara Pailoor discovered that the JFS filesystem implementation in the Linux kernel contained a buffer overflow when handling extended attributes. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2018-12233)
Felix Wilhelm discovered that the KVM implementation in the Linux kernel did not properly perform permission checks in some situations when nested virtualization is used. An attacker in a guest VM could possibly use this to escape into an outer VM or the host OS. (CVE-2018-12904)
Wen Xu discovered that the XFS filesystem implementation in the Linux kernel did not properly handle an error condition with a corrupted xfs image. An attacker could use this to construct a malicious xfs image that, when mounted, could cause a denial of service (system crash). (CVE-2018-13094)
It was discovered that the Linux kernel did not properly handle setgid file creation when performed by a non-member of the group. A local attacker could use this to gain elevated privileges. (CVE-2018-13405)
Silvio Cesare discovered that the generic VESA frame buffer driver in the Linux kernel contained an integer overflow. A local attacker could use this to cause a denial of service…
- Record
USN-3752-1- Updated
- 2026-11-02
OSVUSN-3752-2 No score
linux-hwe vulnerabilities
USN-3752-1 fixed vulnerabilities in the Linux kernel for Ubuntu 18.04 LTS. This update provides the corresponding updates for the Linux Hardware Enablement (HWE) kernel from Ubuntu 18.04 LTS for Ubuntu 16.04 LTS.
It was discovered that, when attempting to handle an out-of-memory situation, a null pointer dereference could be triggered in the Linux kernel in some circumstances. A local attacker could use this to cause a denial of service (system crash). (CVE-2018-1000200)
Wen Xu discovered that the XFS filesystem implementation in the Linux kernel did not properly validate meta-data information. An attacker could use this to construct a malicious xfs image that, when mounted, could cause a denial of service (system crash). (CVE-2018-10323)
Wen Xu discovered that the XFS filesystem implementation in the Linux kernel did not properly validate xattr information. An attacker could use this to construct a malicious xfs image that, when mounted, could cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2018-10840)
Wen Xu discovered that the ext4 filesystem implementation in the Linux kernel did not properly keep meta-data information consistent in some situations. An attacker could use this to construct a malicious ext4 image that, when mounted, could cause a denial of service (system crash). (CVE-2018-10881)
Wen Xu discovered that the ext4 filesystem implementation in the Linux kernel did not properly handle corrupted meta data in some situations. An attacker could use this to specially craft an ext4 filesystem that caused a denial of service (system crash) when mounted. (CVE-2018-1093)
Jann Horn discovered that the Linux kernel's implementation of random seed data reported that it was in a ready state before it had gathered sufficient entropy. An attacker could use this to expose sensitive information. (CVE-2018-1108)
It was discovered that the procfs filesystem did not properly handle processes mapping some memory elements onto files. A local attacker could use this to block utilities that examine the procfs filesystem to report operating system state, such as ps(1). (CVE-2018-1120)
Jann Horn discovered that the ext4 filesystem implementation in the Linux kernel did not properly keep xattr information consistent in some situations. An attacker could use this to construct a malicious ext4 image that, when mounted, could cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2018-11412)
Piotr Gabriel Kosinski and Daniel Shapira discovered a stack-based buffer overflow in the CDROM driver implementation of the Linux kernel. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2018-11506)
Shankara Pailoor discovered that a race condition existed in the socket handling code in the Linux kernel. A local attacker could use this to cause a denial of service (system crash). (CVE-2018-12232)
Shankara Pailoor discovered that the JFS filesystem implementation in the Linux kernel contained a buffer overflow when handling extended attributes. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2018-12233)
Felix Wilhelm discovered that the KVM implementation in the Linux kernel did not properly perform permission checks in some situations when nested virtualization is used. An attacker in a guest VM could possibly use this to escape into an outer VM or the host OS. (CVE-2018-12904)
Wen Xu discovered that the XFS filesystem implementation in the Linux kernel did not properly handle an error condition with a corrupted xfs image. An attacker could use this to construct a malicious xfs image that, when mounted, could cause a denial of service (system crash). (CVE-2018-13094)
It was discovered that the Linux kernel did not properly handle setgid file creation when performed by a non-member of the group. A local attacker could use this to gain elevated…
- Record
USN-3752-2- Updated
- 2026-11-02
OSVUSN-3752-3 No score
linux-azure, linux-oem, linux-gcp vulnerabilities
It was discovered that, when attempting to handle an out-of-memory situation, a null pointer dereference could be triggered in the Linux kernel in some circumstances. A local attacker could use this to cause a denial of service (system crash). (CVE-2018-1000200)
Wen Xu discovered that the XFS filesystem implementation in the Linux kernel did not properly validate meta-data information. An attacker could use this to construct a malicious xfs image that, when mounted, could cause a denial of service (system crash). (CVE-2018-10323)
Wen Xu discovered that the XFS filesystem implementation in the Linux kernel did not properly validate xattr information. An attacker could use this to construct a malicious xfs image that, when mounted, could cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2018-10840)
Wen Xu discovered that the ext4 filesystem implementation in the Linux kernel did not properly keep meta-data information consistent in some situations. An attacker could use this to construct a malicious ext4 image that, when mounted, could cause a denial of service (system crash). (CVE-2018-10881)
Wen Xu discovered that the ext4 filesystem implementation in the Linux kernel did not properly handle corrupted meta data in some situations. An attacker could use this to specially craft an ext4 filesystem that caused a denial of service (system crash) when mounted. (CVE-2018-1093)
Jann Horn discovered that the Linux kernel's implementation of random seed data reported that it was in a ready state before it had gathered sufficient entropy. An attacker could use this to expose sensitive information. (CVE-2018-1108)
It was discovered that the procfs filesystem did not properly handle processes mapping some memory elements onto files. A local attacker could use this to block utilities that examine the procfs filesystem to report operating system state, such as ps(1). (CVE-2018-1120)
Jann Horn discovered that the ext4 filesystem implementation in the Linux kernel did not properly keep xattr information consistent in some situations. An attacker could use this to construct a malicious ext4 image that, when mounted, could cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2018-11412)
Piotr Gabriel Kosinski and Daniel Shapira discovered a stack-based buffer overflow in the CDROM driver implementation of the Linux kernel. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2018-11506)
Shankara Pailoor discovered that a race condition existed in the socket handling code in the Linux kernel. A local attacker could use this to cause a denial of service (system crash). (CVE-2018-12232)
Shankara Pailoor discovered that the JFS filesystem implementation in the Linux kernel contained a buffer overflow when handling extended attributes. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2018-12233)
Felix Wilhelm discovered that the KVM implementation in the Linux kernel did not properly perform permission checks in some situations when nested virtualization is used. An attacker in a guest VM could possibly use this to escape into an outer VM or the host OS. (CVE-2018-12904)
Wen Xu discovered that the XFS filesystem implementation in the Linux kernel did not properly handle an error condition with a corrupted xfs image. An attacker could use this to construct a malicious xfs image that, when mounted, could cause a denial of service (system crash). (CVE-2018-13094)
It was discovered that the Linux kernel did not properly handle setgid file creation when performed by a non-member of the group. A local attacker could use this to gain elevated privileges. (CVE-2018-13405)
Silvio Cesare discovered that the generic VESA frame buffer driver in the Linux kernel contained an integer overflow. A local attacker could use this to cause a denial of service…
- Record
USN-3752-3- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
linuxDebian:12 |
before 4.16.5-1 | 4.16.5-1 |
linuxDebian:13 |
before 4.16.5-1 | 4.16.5-1 |
linuxDebian:14 |
before 4.16.5-1 | 4.16.5-1 |
linuxDebian:9 |
before 4.9.320-2, plus listed versions 4.9.107-14.9.110-14.9.110-24.9.110-34.9.110-3+deb9u1 Show 45 moreShow less4.9.110-3+deb9u24.9.110-3+deb9u34.9.110-3+deb9u44.9.110-3+deb9u54.9.110-3+deb9u64.9.130-14.9.130-24.9.135-14.9.144-14.9.144-24.9.144-34.9.144-3.14.9.161-14.9.168-14.9.168-1+deb9u24.9.168-1+deb9u34.9.168-1+deb9u44.9.168-1+deb9u54.9.184-14.9.185-14.9.189-14.9.189-24.9.189-34.9.189-3+deb9u14.9.189-3+deb9u24.9.210-14.9.210-1+deb9u14.9.228-14.9.240-14.9.240-24.9.246-14.9.246-24.9.258-14.9.272-14.9.272-24.9.290-14.9.30-24.9.30-2+deb9u14.9.30-2+deb9u24.9.30-2+deb9u2~bpo8+14.9.30-2+deb9u34.9.30-2+deb9u44.9.30-2+deb9u54.9.30-2+deb9u5~bpo8+14.9.303-1 |
4.9.320-2 |
kernelMageia:6 |
before 4.14.40-1.mga6 | 4.14.40-1.mga6 |
kernel-userspace-headersMageia:6 |
before 4.14.40-1.mga6 | 4.14.40-1.mga6 |
kmod-vboxadditionsMageia:6 |
before 5.2.8-14.mga6 | 5.2.8-14.mga6 |
kmod-virtualboxMageia:6 |
before 5.2.8-14.mga6 | 5.2.8-14.mga6 |
kmod-xtables-addonsMageia:6 |
before 2.13-34.mga6 | 2.13-34.mga6 |
wireguard-toolsMageia:6 |
before 0.0.20180420-1.mga6 | 0.0.20180420-1.mga6 |
Show 11 moreShow less
| Package | Affected | Fixed |
|---|---|---|
kernel-linusMageia:6 |
before 4.14.44-1.mga6 | 4.14.44-1.mga6 |
linux-azureUbuntu:16.04:LTS |
before 4.15.0-1022.22~16.04.1, plus listed versions 4.11.0-1009.94.11.0-1011.114.11.0-1013.134.11.0-1014.144.11.0-1015.15 Show 15 moreShow less4.11.0-1016.164.13.0-1005.74.13.0-1006.84.13.0-1007.94.13.0-1009.124.13.0-1011.144.13.0-1012.154.13.0-1014.174.13.0-1016.194.13.0-1018.214.15.0-1013.13~16.04.24.15.0-1014.14~16.04.14.15.0-1018.18~16.04.14.15.0-1019.19~16.04.14.15.0-1021.21~16.04.1 |
4.15.0-1022.22~16.04.1 |
linux-gcpUbuntu:16.04:LTS |
before 4.15.0-1018.19~16.04.2, plus listed versions 4.10.0-1004.44.10.0-1006.64.10.0-1007.74.10.0-1008.84.10.0-1009.9 Show 13 moreShow less4.13.0-1002.54.13.0-1006.94.13.0-1007.104.13.0-1008.114.13.0-1011.154.13.0-1012.164.13.0-1013.174.13.0-1015.194.13.0-1017.214.13.0-1019.234.15.0-1014.14~16.04.14.15.0-1015.15~16.04.14.15.0-1017.18~16.04.1 |
4.15.0-1018.19~16.04.2 |
linux-hweUbuntu:16.04:LTS |
before 4.15.0-33.36~16.04.1, plus listed versions 4.8.0-36.36~16.04.14.8.0-39.42~16.04.14.8.0-41.44~16.04.14.8.0-42.45~16.04.14.8.0-44.47~16.04.1 Show 33 moreShow less4.8.0-45.48~16.04.14.8.0-46.49~16.04.14.8.0-49.52~16.04.14.8.0-51.54~16.04.14.8.0-52.55~16.04.14.8.0-53.56~16.04.14.8.0-54.57~16.04.14.8.0-56.61~16.04.14.8.0-58.63~16.04.14.10.0-27.30~16.04.24.10.0-28.32~16.04.24.10.0-30.34~16.04.14.10.0-32.36~16.04.14.10.0-33.37~16.04.14.10.0-35.39~16.04.14.10.0-37.41~16.04.14.10.0-38.42~16.04.14.10.0-40.44~16.04.14.10.0-42.46~16.04.14.13.0-26.29~16.04.24.13.0-31.34~16.04.14.13.0-32.35~16.04.14.13.0-36.40~16.04.14.13.0-37.42~16.04.14.13.0-38.43~16.04.14.13.0-39.44~16.04.14.13.0-41.46~16.04.14.13.0-43.48~16.04.14.13.0-45.50~16.04.14.15.0-24.26~16.04.14.15.0-29.31~16.04.14.15.0-30.32~16.04.14.15.0-32.35~16.04.1 |
4.15.0-33.36~16.04.1 |
linuxUbuntu:18.04:LTS |
before 4.15.0-33.36, plus listed versions 4.13.0-16.194.13.0-17.204.13.0-25.294.13.0-32.354.15.0-10.11 Show 11 moreShow less4.15.0-12.134.15.0-13.144.15.0-15.164.15.0-19.204.15.0-20.214.15.0-22.244.15.0-23.254.15.0-24.264.15.0-29.314.15.0-30.324.15.0-32.35 |
4.15.0-33.36 |
linux-awsUbuntu:18.04:LTS |
before 4.15.0-1020.20, plus listed versions 4.15.0-1001.14.15.0-1003.34.15.0-1005.54.15.0-1006.64.15.0-1007.7 Show 6 moreShow less4.15.0-1009.94.15.0-1010.104.15.0-1011.114.15.0-1016.164.15.0-1017.174.15.0-1019.19 |
4.15.0-1020.20 |
linux-azureUbuntu:18.04:LTS |
before 4.15.0-1022.23, plus listed versions 4.15.0-1002.24.15.0-1003.34.15.0-1004.44.15.0-1008.84.15.0-1009.9 Show 6 moreShow less4.15.0-1012.124.15.0-1013.134.15.0-1014.144.15.0-1018.184.15.0-1019.194.15.0-1021.21 |
4.15.0-1022.23 |
linux-gcpUbuntu:18.04:LTS |
before 4.15.0-1018.19, plus listed versions 4.15.0-1001.14.15.0-1003.34.15.0-1005.54.15.0-1006.64.15.0-1008.8 Show 5 moreShow less4.15.0-1009.94.15.0-1010.104.15.0-1014.144.15.0-1015.154.15.0-1017.18 |
4.15.0-1018.19 |
linux-kvmUbuntu:18.04:LTS |
before 4.15.0-1020.20, plus listed versions 4.15.0-1002.24.15.0-1003.34.15.0-1004.44.15.0-1006.64.15.0-1008.8 Show 6 moreShow less4.15.0-1010.104.15.0-1011.114.15.0-1012.124.15.0-1016.164.15.0-1017.174.15.0-1019.19 |
4.15.0-1020.20 |
linux-oemUbuntu:18.04:LTS |
before 4.15.0-1017.20, plus listed versions 4.15.0-1002.34.15.0-1004.54.15.0-1006.94.15.0-1008.114.15.0-1009.124.15.0-1012.154.15.0-1013.164.15.0-1015.18 |
4.15.0-1017.20 |
linux-raspi2Ubuntu:18.04:LTS |
before 4.15.0-1021.23, plus listed versions 4.13.0-1005.54.13.0-1006.64.13.0-1008.84.15.0-1006.74.15.0-1009.10 Show 7 moreShow less4.15.0-1010.114.15.0-1011.124.15.0-1012.134.15.0-1013.144.15.0-1017.184.15.0-1018.194.15.0-1020.22 |
4.15.0-1021.23 |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2018-1108 is a medium vulnerability (CVSS 5.9) in Debian Linux, published May 18, 2018. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.70%, the 77th percentile. Fixed in linux 4.16.5-1.
References
usn.ubuntu.com/3752-2
usn.ubuntu.com/3752-3
usn.ubuntu.com/3718-2
securityfocus.com/bid/104055
debian.org/security/2018/dsa-4188
usn.ubuntu.com/3718-1
Show 62 moreShow less
usn.ubuntu.com/3752-1
bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-1108
lists.debian.org/debian-lts-announce/2022/07/msg00000.html
nvd.nist.gov/vuln/detail/CVE-2018-1108
github.com/advisories/GHSA-229x-53vm-m4f4
security-tracker.debian.org/tracker/CVE-2018-1108
advisories.mageia.org/MGASA-2018-0249.html
bugs.mageia.org/show_bug.cgi?id=22909
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.31
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.32
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.33
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.34
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.35
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.36
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.37
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.38
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.39
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.40
advisories.mageia.org/MGASA-2018-0265.html
bugs.mageia.org/show_bug.cgi?id=23077
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.19
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.20
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.21
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.22
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.23
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.24
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.25
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.26
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.27
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.28
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.29
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.30
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.41
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.42
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.43
cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.44
ubuntu.com/security/CVE-2018-1108
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=43838a23a05fbd13e47d750d3dfd77001536dd33
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=dc12baacb95f205948f64dc936a47d89ee110117
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=8ef35c866f8862df074a49a93b0309725812dea8
bugs.chromium.org/p/project-zero/issues/detail?id=1559
ubuntu.com/security/notices/USN-3752-1
ubuntu.com/security/notices/USN-3752-2
ubuntu.com/security/notices/USN-3752-3
cve.org/CVERecord?id=CVE-2018-1108
ubuntu.com/security/CVE-2018-1093
ubuntu.com/security/CVE-2018-1120
ubuntu.com/security/CVE-2018-5814
ubuntu.com/security/CVE-2018-9415
ubuntu.com/security/CVE-2018-10323
ubuntu.com/security/CVE-2018-10840
ubuntu.com/security/CVE-2018-10881
ubuntu.com/security/CVE-2018-11412
ubuntu.com/security/CVE-2018-11506
ubuntu.com/security/CVE-2018-12232
ubuntu.com/security/CVE-2018-12233
ubuntu.com/security/CVE-2018-12904
ubuntu.com/security/CVE-2018-13094
ubuntu.com/security/CVE-2018-13405
ubuntu.com/security/CVE-2018-13406
ubuntu.com/security/CVE-2018-1000200
ubuntu.com/security/CVE-2018-1000204
Left out here: 20 versions and the rest of 4 source descriptions. The JSON record has them.