[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-USN-3360-1":6},{"stargazers_count":4,"fetched_at":5},7,"2026-06-04T08:53:30.047Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":11,"aliases":12,"duplicate_of":9,"upstream":13,"downstream":74,"duplicates":75,"related":76,"reserved_at":9,"published_at":92,"modified_at":93,"state":9,"summary":94,"references_raw":96,"kevs":164,"epss":9,"epss_history":165,"metrics":166,"affected":167},"USN-3360-1","linux vulnerabilities\n\nIt was discovered that the Linux kernel did not properly initialize a Wake-\non-Lan data structure. A local attacker could use this to expose sensitive\ninformation (kernel memory). (CVE-2014-9900)\n\nIt was discovered that the Linux kernel did not properly restrict access to\n/proc/iomem. A local attacker could use this to expose sensitive\ninformation. (CVE-2015-8944)\n\nIt was discovered that a use-after-free vulnerability existed in the\nperformance events and counters subsystem of the Linux kernel for ARM64. A\nlocal attacker could use this to cause a denial of service (system crash)\nor possibly execute arbitrary code. (CVE-2015-8955)\n\nIt was discovered that the SCSI generic (sg) driver in the Linux kernel\ncontained a double-free vulnerability. A local attacker could use this to\ncause a denial of service (system crash). (CVE-2015-8962)\n\nSasha Levin discovered that a race condition existed in the performance\nevents and counters subsystem of the Linux kernel when handling CPU unplug\nevents. A local attacker could use this to cause a denial of service\n(system crash) or possibly execute arbitrary code. (CVE-2015-8963)\n\nTilman Schmidt and Sasha Levin discovered a use-after-free condition in the\nTTY implementation in the Linux kernel. A local attacker could use this to\nexpose sensitive information (kernel memory). (CVE-2015-8964)\n\nIt was discovered that the fcntl64() system call in the Linux kernel did\nnot properly set memory limits when returning on 32-bit ARM processors. A\nlocal attacker could use this to gain administrative privileges.\n(CVE-2015-8966)\n\nIt was discovered that the system call table for ARM 64-bit processors in\nthe Linux kernel was not write-protected. An attacker could use this in\nconjunction with another kernel vulnerability to execute arbitrary code.\n(CVE-2015-8967)\n\nIt was discovered that the generic SCSI block layer in the Linux kernel did\nnot properly restrict write operations in certain situations. A local\nattacker could use this to cause a denial of service (system crash) or\npossibly gain administrative privileges. (CVE-2016-10088)\n\nAlexander Potapenko discovered a race condition in the Advanced Linux Sound\nArchitecture (ALSA) subsystem in the Linux kernel. A local attacker could\nuse this to expose sensitive information (kernel memory).\n(CVE-2017-1000380)\n\nLi Qiang discovered that the DRM driver for VMware Virtual GPUs in the\nLinux kernel did not properly validate some ioctl arguments. A local\nattacker could use this to cause a denial of service (system crash).\n(CVE-2017-7346)\n\nTuomas Haanpää and Ari Kauppi discovered that the NFSv2 and NFSv3 server\nimplementations in the Linux kernel did not properly check for the end of\nbuffer. A remote attacker could use this to craft requests that cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2017-7895)\n\nIt was discovered that an integer underflow existed in the Edgeport USB\nSerial Converter device driver of the Linux kernel. An attacker with\nphysical access could use this to expose sensitive information (kernel\nmemory). (CVE-2017-8924)\n\nIt was discovered that the USB ZyXEL omni.net LCD PLUS driver in the Linux\nkernel did not properly perform reference counting. A local attacker could\nuse this to cause a denial of service (tty exhaustion). (CVE-2017-8925)\n\nMurray McAllister discovered that the DRM driver for VMware Virtual GPUs in\nthe Linux kernel did not properly initialize memory. A local attacker could\nuse this to expose sensitive information (kernel memory). (CVE-2017-9605)\n",null,[],[],[],[14,16,18,20,22,24,26,28,30,32,34,36,38,40,42,44,46,48,50,52,54,56,58,60,62,64,66,68,70,72],{"_key":15},"CVE-2014-9900",{"_key":17},"CVE-2015-8944",{"_key":19},"CVE-2015-8955",{"_key":21},"CVE-2015-8962",{"_key":23},"CVE-2015-8963",{"_key":25},"CVE-2015-8964",{"_key":27},"CVE-2015-8966",{"_key":29},"CVE-2015-8967",{"_key":31},"CVE-2016-10088",{"_key":33},"CVE-2017-1000380",{"_key":35},"CVE-2017-7346",{"_key":37},"CVE-2017-7895",{"_key":39},"CVE-2017-8924",{"_key":41},"CVE-2017-8925",{"_key":43},"CVE-2017-9605",{"_key":45},"UBUNTU-CVE-2014-9900",{"_key":47},"UBUNTU-CVE-2015-8944",{"_key":49},"UBUNTU-CVE-2015-8955",{"_key":51},"UBUNTU-CVE-2015-8962",{"_key":53},"UBUNTU-CVE-2015-8963",{"_key":55},"UBUNTU-CVE-2015-8964",{"_key":57},"UBUNTU-CVE-2015-8966",{"_key":59},"UBUNTU-CVE-2015-8967",{"_key":61},"UBUNTU-CVE-2016-10088",{"_key":63},"UBUNTU-CVE-2017-1000380",{"_key":65},"UBUNTU-CVE-2017-7346",{"_key":67},"UBUNTU-CVE-2017-7895",{"_key":69},"UBUNTU-CVE-2017-8924",{"_key":71},"UBUNTU-CVE-2017-8925",{"_key":73},"UBUNTU-CVE-2017-9605",[],[],[77,78,79,80,81,82,83,84,85,86,87,88,89,90,91],{"_key":45},{"_key":65},{"_key":69},{"_key":71},{"_key":73},{"_key":47},{"_key":49},{"_key":51},{"_key":53},{"_key":55},{"_key":57},{"_key":59},{"_key":61},{"_key":63},{"_key":67},"2017-07-21T08:12:39Z","2026-04-22T09:36:29.846281Z",{"cisa_kev":95,"cisa_ransomware":95,"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,[97,103,108,112,116,120,124,128,132,136,140,144,148,152,156,160],{"url":98,"sources":99,"tags":101},"https://ubuntu.com/security/notices/USN-3360-1",[100],"osv_ubuntu",[102],"Advisory",{"url":104,"sources":105,"tags":106},"https://ubuntu.com/security/CVE-2014-9900",[100],[107],"REPORT",{"url":109,"sources":110,"tags":111},"https://ubuntu.com/security/CVE-2015-8944",[100],[107],{"url":113,"sources":114,"tags":115},"https://ubuntu.com/security/CVE-2015-8955",[100],[107],{"url":117,"sources":118,"tags":119},"https://ubuntu.com/security/CVE-2015-8962",[100],[107],{"url":121,"sources":122,"tags":123},"https://ubuntu.com/security/CVE-2015-8963",[100],[107],{"url":125,"sources":126,"tags":127},"https://ubuntu.com/security/CVE-2015-8964",[100],[107],{"url":129,"sources":130,"tags":131},"https://ubuntu.com/security/CVE-2015-8966",[100],[107],{"url":133,"sources":134,"tags":135},"https://ubuntu.com/security/CVE-2015-8967",[100],[107],{"url":137,"sources":138,"tags":139},"https://ubuntu.com/security/CVE-2016-10088",[100],[107],{"url":141,"sources":142,"tags":143},"https://ubuntu.com/security/CVE-2017-7346",[100],[107],{"url":145,"sources":146,"tags":147},"https://ubuntu.com/security/CVE-2017-7895",[100],[107],{"url":149,"sources":150,"tags":151},"https://ubuntu.com/security/CVE-2017-8924",[100],[107],{"url":153,"sources":154,"tags":155},"https://ubuntu.com/security/CVE-2017-8925",[100],[107],{"url":157,"sources":158,"tags":159},"https://ubuntu.com/security/CVE-2017-9605",[100],[107],{"url":161,"sources":162,"tags":163},"https://ubuntu.com/security/CVE-2017-1000380",[100],[107],[],[],[],[168],{"ecosystem":169,"name":170,"vendor":171,"product":170,"cpe_part":9,"purl_type":172,"purl_namespace":171,"purl_name":170,"source":9,"versions":173},"Ubuntu","linux","ubuntu","deb",[174],{"version":175,"is_range":176,"range_type":177,"version_start":9,"version_start_type":9,"version_end":178,"version_end_type":179,"fixed_in":9},"lt3_13_0_125_174",true,"ecosystem","3.13.0-125.174","excluding"]