The Linux kernel through 3.17.4 does not properly restrict dropping of supplemental group memberships in certain namespace scenarios, which allows local users to bypass intended file permissions by leveraging a POSIX ACL containing an entry for the group category that is more restrictive than the entry for the other category, aka a 'negative groups' issue, related to kernel/groups.c, kernel/uid16.c, and kernel/user_namespace.c. (CVE-2014-8989)

A flaw was found in the way the Linux kernel's splice() system call validated its parameters. On certain file systems, a local, unprivileged user could use this flaw to write past the maximum file size, and thus crash the system. (CVE-2014-7822)

Several vulnerabilities have been discovered in the Linux kernel that may lead to a denial of service, information leaks or privilege escalation.

  - CVE-2013-7421 / CVE-2014-9644     It was discovered that the Crypto API allowed     unprivileged users to load arbitrary kernel modules. A     local user can use this flaw to exploit vulnerabilities     in modules that would not normally be loaded.

  - CVE-2014-7822     Akira Fujita found that the splice() system call did not     validate the given file offset and length. A local     unprivileged user can use this flaw to cause filesystem     corruption on ext4 filesystems, or possibly other     effects.

  - CVE-2014-8160     Florian Westphal discovered that a netfilter     (iptables/ip6tables) rule accepting packets to a     specific SCTP, DCCP, GRE or UDPlite port/endpoint could     result in incorrect connection tracking state. If only     the generic connection tracking module (nf_conntrack)     was loaded, and not the protocol-specific connection     tracking module, this would allow access to any     port/endpoint of the specified protocol.

  - CVE-2014-8559     It was found that kernel functions that iterate over a     directory tree can dead-lock or live-lock in case some     of the directory entries were recently deleted or     dropped from the cache. A local unprivileged user can     use this flaw for denial of service.

  - CVE-2014-9585     Andy Lutomirski discovered that address randomisation     for the vDSO in 64-bit processes is extremely biased. A     local unprivileged user could potentially use this flaw     to bypass the ASLR protection mechanism.

  - CVE-2014-9683     Dmitry Chernenkov discovered that eCryptfs writes past     the end of the allocated buffer during encrypted     filename decoding, resulting in local denial of service.

  - CVE-2015-0239     It was found that KVM did not correctly emulate the x86     SYSENTER instruction. An unprivileged user within a     guest system that has not enabled SYSENTER, for example     because the emulated CPU vendor is AMD, could     potentially use this flaw to cause a denial of service     or privilege escalation in that guest.

  - CVE-2015-1420     It was discovered that the open_by_handle_at() system     call reads the handle size from user memory a second     time after validating it. A local user with the     CAP_DAC_READ_SEARCH capability could use this flaw for     privilege escalation.

  - CVE-2015-1421     It was found that the SCTP implementation could free an     authentication state while it was still in use,     resulting in heap corruption. This could allow remote     users to cause a denial of service or privilege     escalation.

  - CVE-2015-1593     It was found that address randomisation for the initial     stack in 64-bit processes was limited to 20 rather than     22 bits of entropy. A local unprivileged user could     potentially use this flaw to bypass the ASLR protection     mechanism.

Updated kernel packages that fix multiple security issues and several bugs are now available for Red Hat Enterprise Linux 6.

Red Hat Product Security has rated this update as having Important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

The kernel packages contain the Linux kernel, the core of any Linux operating system.

* It was found that the Linux kernel's Infiniband subsystem did not properly sanitize input parameters while registering memory regions from user space via the (u)verbs API. A local user with access to a /dev/infiniband/uverbsX device could use this flaw to crash the system or, potentially, escalate their privileges on the system.
(CVE-2014-8159, Important)

* A flaw was found in the way the Linux kernel's splice() system call validated its parameters. On certain file systems, a local, unprivileged user could use this flaw to write past the maximum file size, and thus crash the system. (CVE-2014-7822, Moderate)

* A flaw was found in the way the Linux kernel's netfilter subsystem handled generic protocol tracking. As demonstrated in the Stream Control Transmission Protocol (SCTP) case, a remote attacker could use this flaw to bypass intended iptables rule restrictions when the associated connection tracking module was not loaded on the system.
(CVE-2014-8160, Moderate)

* It was found that the fix for CVE-2014-3601 was incomplete: the Linux kernel's kvm_iommu_map_pages() function still handled IOMMU mapping failures incorrectly. A privileged user in a guest with an assigned host device could use this flaw to crash the host.
(CVE-2014-8369, Moderate)

Red Hat would like to thank Mellanox for reporting CVE-2014-8159, and Akira Fujita of NEC for reporting CVE-2014-7822.

Bug fixes :

* The maximum amount of entries in the IPv6 route table (net.ipv6.route.max_size) was 4096, and every route towards this maximum size limit was counted. Communication to more systems was impossible when the limit was exceeded. Now, only cached routes are counted, which guarantees that the kernel does not run out of memory, but the user can now install as many routes as the memory allows until the kernel indicates it can no longer handle the amount of memory and returns an error message.

In addition, the default 'net.ipv6.route.max_size' value has been increased to 16384 for performance improvement reasons. (BZ#1177581)

* When the user attempted to scan for an FCOE-served Logical Unit Number (LUN), after an initial LUN scan, a kernel panic occurred in bnx2fc_init_task. System scanning for LUNs is now stable after LUNs have been added. (BZ#1179098)

* Under certain conditions, such as when attempting to scan the network for LUNs, a race condition in the bnx2fc driver could trigger a kernel panic in bnx2fc_init_task. A patch fixing a locking issue that caused the race condition has been applied, and scanning the network for LUNs no longer leads to a kernel panic. (BZ#1179098)

* Previously, it was not possible to boot the kernel on Xen hypervisor in PVHVM mode if more than 32 vCPUs were specified in the guest configuration. Support for more than 32 vCPUs has been added, and the kernel now boots successfully in the described situation. (BZ#1179343)

* When the NVMe driver allocated a namespace queue, it indicated that it was a request-based driver when it was actually a block I/O-based driver. Consequently, when NVMe driver was loaded along with a request-based dm device, the system could terminate unexpectedly or become unresponsive when attempting to access data. The NVMe driver no longer sets the QUEUE_FLAG_STACKABLE bit when allocating a namespace queue and device-mapper no longer perceives NVMe driver as request-based; system hangs or crashes no longer occur. (BZ#1180555)

* If a user attempted to apply an NVRAM firmware update when running the tg3 module provided with Red Hat Enterprise Linux 6.6 kernels, the update could fail. As a consequence, the Network Interface Card (NIC) could stay in an unusable state and this could prevent the entire system from booting. The tg3 module has been updated to correctly apply firmware updates. (BZ#1182903)

* Support for key sizes of 256 and 192 bits has been added to AES-NI.
(BZ#1184332)

Eric Windisch discovered flaw in how the Linux kernel's XFS file system replaces remote attributes. A local access with access to an XFS file system could exploit this flaw to escalate their privileges.
(CVE-2015-0274)

A flaw was discovered in the automatic loading of modules in the crypto subsystem of the Linux kernel. A local user could exploit this flaw to load installed kernel modules, increasing the attack surface and potentially using this to gain administrative privileges.
(CVE-2013-7421)

The Linux kernel's splice system call did not correctly validate its parameters. A local, unprivileged user could exploit this flaw to cause a denial of service (system crash). (CVE-2014-7822)

A flaw was discovered in the crypto subsystem when screening module names for automatic module loading if the name contained a valid crypto module name, eg. vfat(aes). A local user could exploit this flaw to load installed kernel modules, increasing the attack surface and potentially using this to gain administrative privileges.
(CVE-2014-9644).

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

This update fixes the CVEs described below.

A further issue, CVE-2014-9419, was considered, but appears to require extensive changes with a consequent high risk of regression. It is now unlikely to be fixed in squeeze-lts.

CVE-2013-6885

It was discovered that under specific circumstances, a combination of write operations to write-combined memory and locked CPU instructions may cause a core hang on AMD 16h 00h through 0Fh processors. A local user can use this flaw to mount a denial of service (system hang) via a crafted application.

For more information please refer to the AMD CPU erratum 793 in http://support.amd.com/TechDocs/51810_16h_00h-0Fh_Rev_Guide.
pdf

CVE-2014-7822

It was found that the splice() system call did not validate the given file offset and length. A local unprivileged user can use this flaw to cause filesystem corruption on ext4 filesystems, or possibly other effects.

CVE-2014-8133

It was found that the espfix functionality can be bypassed by installing a 16-bit RW data segment into GDT instead of LDT (which espfix checks for) and using it for stack. A local unprivileged user could potentially use this flaw to leak kernel stack addresses.

CVE-2014-8134

It was found that the espfix functionality is wrongly disabled in a 32-bit KVM guest. A local unprivileged user could potentially use this flaw to leak kernel stack addresses.

CVE-2014-8160

It was found that a netfilter (iptables or ip6tables) rule accepting packets to a specific SCTP, DCCP, GRE or UDPlite port/endpoint could result in incorrect connection tracking state. If only the generic connection tracking module (nf_conntrack) was loaded, and not the protocol-specific connection tracking module, this would allow access to any port/endpoint of the specified protocol.

CVE-2014-9420

It was found that the ISO-9660 filesystem implementation (isofs) follows arbitrarily long chains, including loops, of Continuation Entries (CEs). This allows local users to mount a denial of service via a crafted disc image.

CVE-2014-9584

It was found that the ISO-9660 filesystem implementation (isofs) does not validate a length value in the Extensions Reference (ER) System Use Field, which allows local users to obtain sensitive information from kernel memory via a crafted disc image.

CVE-2014-9585

It was discovered that address randomisation for the vDSO in 64-bit processes is extremely biassed. A local unprivileged user could potentially use this flaw to bypass the ASLR protection mechanism.

CVE-2015-1421

It was found that the SCTP implementation could free authentication state while it was still in use, resulting in heap corruption. This could allow remote users to cause a denial of service or privilege escalation.

CVE-2015-1593

It was found that address randomisation for the initial stack in 64-bit processes was limited to 20 rather than 22 bits of entropy. A local unprivileged user could potentially use this flaw to bypass the ASLR protection mechanism.

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote OracleVM system is missing necessary patches to address critical security updates : please see Oracle VM Security Advisory OVMSA-2017-0057 for details.

The remote Redhat Enterprise Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2015:0102 advisory.

    The kernel packages contain the Linux kernel, the core of any Linux     operating system.

    * A flaw was found in the way the Linux kernel's SCTP implementation     validated INIT chunks when performing Address Configuration Change     (ASCONF). A remote attacker could use this flaw to crash the system by     sending a specially crafted SCTP packet to trigger a NULL pointer     dereference on the system. (CVE-2014-7841, Important)

    * A race condition flaw was found in the way the Linux kernel's mmap(2),     madvise(2), and fallocate(2) system calls interacted with each other while     operating on virtual memory file system files. A local user could use this     flaw to cause a denial of service. (CVE-2014-4171, Moderate)

    * A NULL pointer dereference flaw was found in the way the Linux kernel's     Common Internet File System (CIFS) implementation handled mounting of file     system shares. A remote attacker could use this flaw to crash a client     system that would mount a file system share from a malicious server.
    (CVE-2014-7145, Moderate)

    * A flaw was found in the way the Linux kernel's splice() system call     validated its parameters. On certain file systems, a local, unprivileged     user could use this flaw to write past the maximum file size, and thus     crash the system. (CVE-2014-7822, Moderate)

    * It was found that the parse_rock_ridge_inode_internal() function of the     Linux kernel's ISOFS implementation did not correctly check relocated     directories when processing Rock Ridge child link (CL) tags. An attacker     with physical access to the system could use a specially crafted ISO image     to crash the system or, potentially, escalate their privileges on the     system. (CVE-2014-5471, CVE-2014-5472, Low)

    Red Hat would like to thank Akira Fujita of NEC for reporting the     CVE-2014-7822 issue. The CVE-2014-7841 issue was discovered by Liu Wei of     Red Hat.

    This update also fixes the following bugs:

    * Previously, a kernel panic could occur if a process reading from a locked     NFS file was killed and the lock was not released properly before the read     operations finished. Consequently, the system crashed. The code handling     file locks has been fixed, and instead of halting, the system now emits a     warning about the unreleased lock. (BZ#1172266)

    * A race condition in the command abort handling logic of the ipr device     driver could cause the kernel to panic when the driver received a response     to an abort command prior to receiving other responses to the aborted     command due to the support for multiple interrupts. With this update, the     abort handler waits for the aborted command's responses first before     completing an abort operation. (BZ#1162734)

    * Previously, a race condition could occur when changing a Page Table Entry     (PTE) or a Page Middle Directory (PMD) to pte_numa or pmd_numa,     respectively, causing the kernel to crash. This update removes the BUG_ON()     macro from the __handle_mm_fault() function, preventing the kernel panic in     the aforementioned scenario. (BZ#1170662)

    All kernel users are advised to upgrade to these updated packages, which     contain backported patches to correct these issues. The system must be     rebooted for this update to take effect.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

- It was found that the Linux kernel's Infiniband     subsystem did not properly sanitize input parameters     while registering memory regions from user space via the     (u)verbs API. A local user with access to a     /dev/infiniband/uverbsX device could use this flaw to     crash the system or, potentially, escalate their     privileges on the system. (CVE-2014-8159, Important)

  - A flaw was found in the way the Linux kernel's splice()     system call validated its parameters. On certain file     systems, a local, unprivileged user could use this flaw     to write past the maximum file size, and thus crash the     system. (CVE-2014-7822, Moderate)

  - A flaw was found in the way the Linux kernel's netfilter     subsystem handled generic protocol tracking. As     demonstrated in the Stream Control Transmission Protocol     (SCTP) case, a remote attacker could use this flaw to     bypass intended iptables rule restrictions when the     associated connection tracking module was not loaded on     the system. (CVE-2014-8160, Moderate)

  - It was found that the fix for CVE-2014-3601 was     incomplete: the Linux kernel's kvm_iommu_map_pages()     function still handled IOMMU mapping failures     incorrectly. A privileged user in a guest with an     assigned host device could use this flaw to crash the     host. (CVE-2014-8369, Moderate)

Bug fixes :

  - The maximum amount of entries in the IPv6 route table     (net.ipv6.route.max_size) was 4096, and every route     towards this maximum size limit was counted.
    Communication to more systems was impossible when the     limit was exceeded. Now, only cached routes are counted,     which guarantees that the kernel does not run out of     memory, but the user can now install as many routes as     the memory allows until the kernel indicates it can no     longer handle the amount of memory and returns an error     message.

In addition, the default 'net.ipv6.route.max_size' value has been increased to 16384 for performance improvement reasons.

  - When the user attempted to scan for an FCOE-served     Logical Unit Number (LUN), after an initial LUN scan, a     kernel panic occurred in bnx2fc_init_task. System     scanning for LUNs is now stable after LUNs have been     added.

  - Under certain conditions, such as when attempting to     scan the network for LUNs, a race condition in the     bnx2fc driver could trigger a kernel panic in     bnx2fc_init_task. A patch fixing a locking issue that     caused the race condition has been applied, and scanning     the network for LUNs no longer leads to a kernel panic.

  - Previously, it was not possible to boot the kernel on     Xen hypervisor in PVHVM mode if more than 32 vCPUs were     specified in the guest configuration. Support for more     than 32 vCPUs has been added, and the kernel now boots     successfully in the described situation.

  - When the NVMe driver allocated a namespace queue, it     indicated that it was a request-based driver when it was     actually a block I/O-based driver. Consequently, when     NVMe driver was loaded along with a request-based dm     device, the system could terminate unexpectedly or     become unresponsive when attempting to access data. The     NVMe driver no longer sets the QUEUE_FLAG_STACKABLE bit     when allocating a namespace queue and device- mapper no     longer perceives NVMe driver as request-based; system     hangs or crashes no longer occur.

  - If a user attempted to apply an NVRAM firmware update     when running the tg3 module provided with Scientific     Linux 6.6 kernels, the update could fail. As a     consequence, the Network Interface Card (NIC) could stay     in an unusable state and this could prevent the entire     system from booting. The tg3 module has been updated to     correctly apply firmware updates.

  - Support for key sizes of 256 and 192 bits has been added     to AES-NI.

According to the versions of the kernel packages installed, the EulerOS Virtualization for ARM 64 installation on the remote host is affected by the following vulnerabilities :

  - An information-leak vulnerability was found in the     kernel when it truncated a file to a smaller size which     consisted of an inline extent that was compressed. The     data between the new file size and the old file size     was not discarded and the number of bytes used by the     inode were not correctly decremented, which gave the     wrong report for callers of the stat(2) syscall. This     wasted metadata space and allowed for the truncated     data to be leaked, and data corruption or loss to     occur. A caller of the clone ioctl could exploit this     flaw by using only standard file-system operations     without root access to read the truncated     data.(CVE-2015-8374i1/4%0

  - crypto/pcrypt.c in the Linux kernel, before 4.14.13,     mishandles freeing instances, allowing a local user     able to access the AF_ALG-based AEAD interface     (CONFIG_CRYPTO_USER_API_AEAD) and pcrypt     (CONFIG_CRYPTO_PCRYPT) to cause a denial of service     (kfree of an incorrect pointer) or possibly have     unspecified other impact by executing a crafted     sequence of system calls. Due to the nature of the     flaw, privilege escalation cannot be fully ruled out,     although we believe it is unlikely.(CVE-2017-18075i1/4%0

  - An elevation of privilege vulnerability in the Qualcomm     Wi-Fi driver could enable a local malicious application     to execute arbitrary code within the context of the     kernel. This issue is rated as High because it first     requires compromising a privileged process. Product:
    Android. Versions: N/A. Android ID: A-32835279.
    References: QC-CR#1096945.(CVE-2017-0523i1/4%0

  - The saa7164_bus_get function in     drivers/media/pci/saa7164/saa7164-bus.c in the Linux     kernel through 4.10.14 allows local users to cause a     denial of service (out-of-bounds array access) or     possibly have unspecified other impact by changing a     certain sequence-number value, aka a 'double fetch'     vulnerability.(CVE-2017-8831i1/4%0

  - A flaw was found in the way the Linux kernel's splice()     system call validated its parameters. On certain file     systems, a local, unprivileged user could use this flaw     to write past the maximum file size, and thus crash the     system.(CVE-2014-7822i1/4%0

  - The vc4_get_bcl function in     drivers/gpu/drm/vc4/vc4_gem.c in the VideoCore DRM     driver in the Linux kernel before 4.9.7 does not set an     errno value upon certain overflow detections allowing     local users to cause a denial of service (incorrect     pointer dereference and OOPS) via inconsistent size     values in a VC4_SUBMIT_CL ioctl call.(CVE-2017-5577i1/4%0

  - In fs/ocfs2/cluster/nodemanager.c in the Linux kernel     before 4.15, local users can cause a denial of service     (NULL pointer dereference and BUG) because a required     mutex is not used.(CVE-2017-18216i1/4%0

  - A race condition issue leading to a use-after-free flaw     was found in the way the raw packet sockets     implementation in the Linux kernel networking subsystem     handled synchronization while creating the TPACKET_V3     ring buffer. A local user able to open a raw packet     socket (requires the CAP_NET_RAW capability) could use     this flaw to elevate their privileges on the     system.(CVE-2016-8655i1/4%0

  - An exploitable memory corruption flaw was found in the     Linux kernel. The append path can be erroneously     switched from UFO to non-UFO in ip_ufo_append_data()     when building an UFO packet with MSG_MORE option. If     unprivileged user namespaces are available, this flaw     can be exploited to gain root     privileges.(CVE-2017-1000112i1/4%0

  - A security flaw was found in the Linux kernel in a way     that the cleancache subsystem clears an inode after the     final file truncation (removal). The new file created     with the same inode may contain leftover pages from     cleancache and the old file data instead of the new     one.(CVE-2018-16862i1/4%0

  - arch/arm64/ include /asm/pgtable.h in the Linux kernel     before 3.15-rc5-next-20140519, as used in Android     before 2016-07-05 on Nexus 5X and 6P devices,     mishandles execute-only pages, which allows attackers     to gain privileges via a crafted application, aka     Android internal bug 28557020.(CVE-2014-9803i1/4%0

  - A heap-buffer overflow vulnerability was found in the     arcmsr_iop_message_xfer() function in     'drivers/scsi/arcmsr/arcmsr_hba.c' file in the Linux     kernel through 4.8.2. The function does not restrict a     certain length field, which allows local users to gain     privileges or cause a denial of service via an     ARCMSR_MESSAGE_WRITE_WQBUFFER control code. This can     potentially cause kernel heap corruption and arbitrary     kernel code execution.(CVE-2016-7425i1/4%0

  - An issue was discovered in the Linux kernel before     4.18.11. The ipddp_ioctl function in     drivers/net/appletalk/ipddp.c allows local users to     obtain sensitive kernel address information by     leveraging CAP_NET_ADMIN to read the ipddp_route dev     and next fields via an SIOCFINDIPDDPRT ioctl     call.(CVE-2018-20511i1/4%0

  - A memory leak in the irda_bind function in     net/irda/af_irda.c in the Linux kernel, through 4.16,     allows local users to cause a denial of service due to     a memory consumption by repeatedly binding an AF_IRDA     socket.(CVE-2018-6554i1/4%0

  - sound/core/timer.c in the Linux kernel before 4.4.1     employs a locking approach that does not consider slave     timer instances, which allows local users to cause a     denial of service (race condition, use-after-free, and     system crash) via a crafted ioctl     call.(CVE-2016-2547i1/4%0

  - Buffer overflow in the complete_emulated_mmio function     in arch/x86/kvm/x86.c in the Linux kernel before 3.13.6     allows guest OS users to execute arbitrary code on the     host OS by leveraging a loop that triggers an invalid     memory copy affecting certain cancel_work_item     data.(CVE-2014-0049i1/4%0

  - An issue was discovered in the F2FS filesystem code in     the Linux kernel in fs/f2fs/inode.c. A denial of     service due to a slab out-of-bounds read can occur for     a crafted f2fs filesystem image in which FI_EXTRA_ATTR     is set in an inode.(CVE-2018-13098i1/4%0

  - A vulnerability was found in the Linux kernel where     having malicious IP options present would cause the     ipv4_pktinfo_prepare() function to drop/free the dst.
    This could result in a system crash or possible     privilege escalation.(CVE-2017-5970i1/4%0

  - In the Linux kernel's vmw_gb_surface_define_ioctl()     function, in 'drivers/gpu/drm/vmwgfx/vmwgfx_surface.c'     file, a 'req-i1/4zmip_levels' is a user-controlled value     which is later used as a loop count limit. This allows     local unprivileged user to cause a denial of service by     a kernel lockup via a crafted ioctl call for a     '/dev/dri/renderD*' device.(CVE-2017-7346i1/4%0

  - It was found that the NFSv4 server in the Linux kernel     did not properly validate layout type when processing     NFSv4 pNFS LAYOUTGET and GETDEVICEINFO operands. A     remote attacker could use this flaw to soft-lockup the     system and thus cause denial of     service.(CVE-2017-8797i1/4%0

Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-001031 advisory.

    The implementation of certain splice_write file operations in the Linux kernel before 3.16 does not     enforce a restriction on the maximum size of a single file, which allows local users to cause a denial of     service (system crash) or possibly have unspecified other impact via a crafted splice system call, as     demonstrated by use of a file descriptor associated with an ext4 filesystem.

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
81322	Amazon Linux AMI : kernel (ALAS-2015-476)	Nessus	Amazon Linux Local Security Checks	2015/2/13	2018/4/18	high
81449	Debian DSA-3170-1 : linux - security update	Nessus	Debian Local Security Checks	2015/2/24	2021/1/11	critical
81769	RHEL 6 : kernel (RHSA-2015:0674)	Nessus	Red Hat Local Security Checks	2015/3/12	2021/2/5	high
82070	Ubuntu 12.04 LTS : linux-lts-trusty vulnerabilities (USN-2543-1)	Nessus	Ubuntu Local Security Checks	2015/3/25	2021/1/19	high
82138	Debian DLA-155-1 : linux-2.6 security update	Nessus	Debian Local Security Checks	2015/3/26	2021/1/11	critical
99163	OracleVM 3.3 : Unbreakable / etc (OVMSA-2017-0057) (Dirty COW)	Nessus	OracleVM Local Security Checks	2017/4/3	2025/12/26	critical
81070	RHEL 7 : kernel (RHSA-2015:0102)	Nessus	Red Hat Local Security Checks	2015/1/29	2025/4/15	medium
81792	CentOS 6 : kernel (CESA-2015:0674)	Nessus	CentOS Local Security Checks	2015/3/13	2021/1/4	high
81809	Scientific Linux Security Update : kernel on SL6.x i386/x86_64 (20150311)	Nessus	Scientific Linux Local Security Checks	2015/3/13	2021/1/14	high
82020	SuSE 11.3 Security Update : Linux Kernel (SAT Patch Numbers 10412 / 10415 / 10416)	Nessus	SuSE Local Security Checks	2015/3/24	2021/1/6	high
124806	EulerOS Virtualization for ARM 64 3.0.1.0 : kernel (EulerOS-SA-2019-1482)	Nessus	Huawei Local Security Checks	2019/5/13	2022/5/20	high
290358	Unity Linux 20.1050e / 20.1060e / 20.1070e Security Update: kernel (UTSA-2026-001031)	Nessus	Unity Linux Local Security Checks	2026/1/16	2026/1/16	high

检测

插件搜索

high

critical

high

high

critical

critical

medium

high

high

high

high

high