[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-MGASA-2017-0343":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":22,"duplicates":23,"related":24,"reserved_at":9,"published_at":29,"modified_at":30,"state":9,"summary":31,"references_raw":33,"kevs":74,"epss":9,"epss_history":75,"metrics":76,"affected":77},"MGASA-2017-0343","Updated kernel-tmb packages fix security vulnerabilities\n\nThis kernel-tmb update is based on upstream 4.9.50 and fixes at least the\nfollowing security issues:\n\nnet/xfrm/xfrm_policy.c in the Linux kernel through 4.12.3, when \nCONFIG_XFRM_MIGRATE is enabled, does not ensure that the dir value of\nxfrm_userpolicy_id is XFRM_POLICY_MAX or less, which allows local users\nto cause a denial of service (out-of-bounds access) or possibly have\nunspecified other impact via an XFRM_MSG_MIGRATE xfrm Netlink message\n(CVE-2017-11600).\n\nThe xen_biovec_phys_mergeable function in drivers/xen/biomerge.c in Xen\nmight allow local OS guest users to corrupt block device data streams\nand consequently obtain sensitive memory information, cause a denial of\nservice, or gain host OS privileges by leveraging incorrect block IO\nmerge-ability calculation (CVE-2017-12134 / XSA-229).\n\nThe XFS_IS_REALTIME_INODE macro in fs/xfs/xfs_linux.h in the Linux kernel\nbefore 4.13.2 does not verify that a filesystem has a realtime device,\nwhich allows local users to cause a denial of service (NULL pointer\ndereference and OOPS) via vectors related to setting an RHINHERIT flag\non a directory (CVE-2017-14340).\n\nThe native Bluetooth stack in the Linux Kernel (BlueZ), starting at the\nLinux kernel version 3.3-rc1 and up to and including 4.13.1, are vulnerable\nto a stack overflow vulnerability in the processing of L2CAP configuration\nresponses resulting in Remote code execution in kernel space\n(CVE-2017-1000251).\n\nFor other upstream fixes in this update, read the referenced changelogs.\n",null,[],[],[],[14,16,18,20],{"_key":15},"CVE-2017-1000251",{"_key":17},"CVE-2017-11600",{"_key":19},"CVE-2017-12134",{"_key":21},"CVE-2017-14340",[],[],[25,26,27,28],{"_key":15},{"_key":17},{"_key":19},{"_key":21},"2017-09-16T08:24:57Z","2026-04-16T06:26:29.071909383Z",{"cisa_kev":32,"cisa_ransomware":32,"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,[34,40,45,50,54,58,62,66,70],{"url":35,"sources":36,"tags":38},"https://advisories.mageia.org/MGASA-2017-0343.html",[37],"osv_mageia",[39],"Advisory",{"url":41,"sources":42,"tags":43},"https://bugs.mageia.org/show_bug.cgi?id=21709",[37],[44],"REPORT",{"url":46,"sources":47,"tags":48},"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.44",[37],[44,49],"WEB",{"url":51,"sources":52,"tags":53},"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.45",[37],[44,49],{"url":55,"sources":56,"tags":57},"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.46",[37],[44,49],{"url":59,"sources":60,"tags":61},"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.47",[37],[44,49],{"url":63,"sources":64,"tags":65},"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.48",[37],[44,49],{"url":67,"sources":68,"tags":69},"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.49",[37],[44,49],{"url":71,"sources":72,"tags":73},"https://cdn.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.50",[37],[44,49],[],[],[],[78],{"ecosystem":79,"name":80,"vendor":81,"product":80,"cpe_part":9,"purl_type":82,"purl_namespace":81,"purl_name":80,"source":9,"versions":83},"Mageia","kernel-tmb","mageia","rpm",[84],{"version":85,"is_range":86,"range_type":87,"version_start":9,"version_start_type":9,"version_end":88,"version_end_type":89,"fixed_in":9},"lt4_9_50_1_mga6",true,"ecosystem","4.9.50-1.mga6","excluding"]