[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-MGASA-2017-0384":6},{"stargazers_count":4,"fetched_at":5},7,"2026-06-04T02:53:27.892Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":11,"aliases":12,"duplicate_of":9,"upstream":13,"downstream":34,"duplicates":35,"related":36,"reserved_at":9,"published_at":47,"modified_at":48,"state":9,"summary":49,"references_raw":51,"kevs":88,"epss":9,"epss_history":89,"metrics":90,"affected":91},"MGASA-2017-0384","Updated kernel-tmb packages fix security vulnerabilities\n\nThis kernel-tmb update is based on upstream 4.9.56 and fixes at least the\nfollowing security issues:\n\nA flaw was found in the way the Linux KVM module processed the trap flag(TF)\nbit in EFLAGS during emulation of the syscall instruction, which leads to a\ndebug exception(#DB) being raised in the guest stack. A user/process inside\na guest could use this flaw to potentially escalate their privileges inside\nthe guest (CVE-2017-7518).\n\nA kernel data leak due to an out-of-bound read was found in the Linux kernel\nin inet_diag_msg_sctp{,l}addr_fill() and sctp_get_sctp_info() functions\npresent since version 4.7-rc1 through version 4.13. A data leak happens when\nthese functions fill in sockaddr data structures used to export socket's\ndiagnostic information. As a result, up to 100 bytes of the slab data could\nbe leaked to a userspace (CVE-2017-7558).\n\nA security flaw was discovered in nl80211_set_rekey_data() function in the\nLinux kernel since v3.1-rc1 through v4.13. This function does not check\nwhether the required attributes are present in a netlink request. This\nrequest can be issued by a user with CAP_NET_ADMIN privilege and may result\nin NULL dereference and a system crash (CVE-2017-12153).\n\nLinux kernel built with the KVM visualization support (CONFIG_KVM), with\nnested visualization (nVMX) feature enabled (nested=1), is vulnerable to a\ncrash due to disabled external interrupts. As L2 guest could acce s (r/w)\nhardware CR8 register of the host(L0). In a nested visualization setup,\nL2 guest user could use this flaw to potentially crash the host(L0)\nresulting in DoS (CVE-2017-12154).\n\nThe tcp_disconnect function in net/ipv4/tcp.c in the Linux kernel before\n4.12 allows local users to cause a denial of service (__tcp_select_window\ndivide-by-zero error and system crash) by triggering a disconnect within a\ncertain tcp_recvmsg code path (CVE-2017-14106).\n\nThe atyfb_ioctl function in drivers/video/fbdev/aty/atyfb_base.c in the\nLinux kernel through 4.12.10 does not initialize a certain data structure,\nwhich allows local users to obtain sensitive information from kernel stack\nmemory by reading locations associated with padding bytes (CVE-2017-14156).\n\nIt was found that the iscsi_if_rx() function in scsi_transport_iscsi.c in\nthe Linux kernel since v2.6.24-rc1 through 4.13.2 allows local users to\ncause a denial of service (a system panic) by making a number of certain\nsyscalls by leveraging incorrect length validation in the kernel code\n(CVE-2017-14489).\n\nThe sg_ioctl function in drivers/scsi/sg.c in the Linux kernel before 4.13.4\nallows local users to obtain sensitive information from uninitialized kernel\nheap-memory locations via an SG_GET_REQUEST_TABLE ioctl call for /dev/sg0\n(CVE-2017-14991).\n\nThe tpacket_rcv() function in 'net/packet/af_packet.c' file in the Linux\nkernel before 4.13 mishandles vnet headers, which might allow local users\nto cause a denial of service (buffer overflow, and disk and memory\ncorruption) or possibly have unspecified other impact via crafted system\ncalls (CVE-2017-14497).\n\nA reachable assertion failure flaw was found in the Linux kernel built with\nKVM virtualisation(CONFIG_KVM) support with Virtual Function I/O feature\n(CONFIG_VFIO) enabled. This failure could occur if a malicious guest device\nsent a virtual interrupt (guest IRQ) with a larger (>1024) index value\n(CVE-2017-1000252).\n\nFor other upstream fixes in this update, read the referenced changelogs.\n",null,[],[],[],[14,16,18,20,22,24,26,28,30,32],{"_key":15},"CVE-2017-1000252",{"_key":17},"CVE-2017-12153",{"_key":19},"CVE-2017-12154",{"_key":21},"CVE-2017-14106",{"_key":23},"CVE-2017-14156",{"_key":25},"CVE-2017-14489",{"_key":27},"CVE-2017-14497",{"_key":29},"CVE-2017-14991",{"_key":31},"CVE-2017-7518",{"_key":33},"CVE-2017-7558",[],[],[37,38,39,40,41,42,43,44,45,46],{"_key":15},{"_key":17},{"_key":19},{"_key":21},{"_key":23},{"_key":25},{"_key":27},{"_key":29},{"_key":31},{"_key":33},"2017-10-24T05:50:58Z","2026-04-16T06:22:32.602926837Z",{"cisa_kev":50,"cisa_ransomware":50,"cisa_vendor":9,"epss_severity":9,"epss_score":9,"severity":9,"severity_score":9,"severity_version":9,"severity_source":9,"severity_vector":9,"severity_status":9},false,[52,58,63,68,72,76,80,84],{"url":53,"sources":54,"tags":56},"https://advisories.mageia.org/MGASA-2017-0384.html",[55],"osv_mageia",[57],"Advisory",{"url":59,"sources":60,"tags":61},"https://bugs.mageia.org/show_bug.cgi?id=21851",[55],[62],"REPORT",{"url":64,"sources":65,"tags":66},"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.51",[55],[62,67],"WEB",{"url":69,"sources":70,"tags":71},"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.52",[55],[62,67],{"url":73,"sources":74,"tags":75},"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.53",[55],[62,67],{"url":77,"sources":78,"tags":79},"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.54",[55],[62,67],{"url":81,"sources":82,"tags":83},"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.55",[55],[62,67],{"url":85,"sources":86,"tags":87},"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.56",[55],[62,67],[],[],[],[92],{"ecosystem":93,"name":94,"vendor":95,"product":94,"cpe_part":9,"purl_type":96,"purl_namespace":95,"purl_name":94,"source":9,"versions":97},"Mageia","kernel-tmb","mageia","rpm",[98],{"version":99,"is_range":100,"range_type":101,"version_start":9,"version_start_type":9,"version_end":102,"version_end_type":103,"fixed_in":9},"lt4_9_56_1_mga6",true,"ecosystem","4.9.56-1.mga6","excluding"]