[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-USN-4186-1":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":66,"duplicates":67,"related":68,"reserved_at":9,"published_at":82,"modified_at":83,"state":9,"summary":84,"references_raw":86,"kevs":146,"epss":9,"epss_history":147,"metrics":148,"affected":149},"USN-4186-1","linux, linux-aws, linux-kvm vulnerabilities\n\nStephan van Schaik, Alyssa Milburn, Sebastian Österlund, Pietro Frigo,\nKaveh Razavi, Herbert Bos, Cristiano Giuffrida, Giorgi Maisuradze, Moritz\nLipp, Michael Schwarz, Daniel Gruss, and Jo Van Bulck discovered that Intel\nprocessors using Transactional Synchronization Extensions (TSX) could\nexpose memory contents previously stored in microarchitectural buffers to a\nmalicious process that is executing on the same CPU core. A local attacker\ncould use this to expose sensitive information. (CVE-2019-11135)\n\nIt was discovered that the Intel i915 graphics chipsets allowed userspace\nto modify page table entries via writes to MMIO from the Blitter Command\nStreamer and expose kernel memory information. A local attacker could use\nthis to expose sensitive information or possibly elevate privileges.\n(CVE-2019-0155)\n\nDeepak Gupta discovered that on certain Intel processors, the Linux kernel\ndid not properly perform invalidation on page table updates by virtual\nguest operating systems. A local attacker in a guest VM could use this to\ncause a denial of service (host system crash). (CVE-2018-12207)\n\nIt was discovered that the Intel i915 graphics chipsets could cause a\nsystem hang when userspace performed a read from GT memory mapped input\noutput (MMIO) when the product is in certain low power states. A local\nattacker could use this to cause a denial of service. (CVE-2019-0154)\n\nHui Peng discovered that the Atheros AR6004 USB Wi-Fi device driver for the\nLinux kernel did not properly validate endpoint descriptors returned by the\ndevice. A physically proximate attacker could use this to cause a denial of\nservice (system crash). (CVE-2019-15098)\n\nIt was discovered that a buffer overflow existed in the 802.11 Wi-Fi\nconfiguration interface for the Linux kernel when handling beacon settings.\nA local attacker could use this to cause a denial of service (system crash)\nor possibly execute arbitrary code. (CVE-2019-16746)\n\nOri Nimron discovered that the AX25 network protocol implementation in the\nLinux kernel did not properly perform permissions checks. A local attacker\ncould use this to create a raw socket. (CVE-2019-17052)\n\nOri Nimron discovered that the IEEE 802.15.4 Low-Rate Wireless network\nprotocol implementation in the Linux kernel did not properly perform\npermissions checks. A local attacker could use this to create a raw socket.\n(CVE-2019-17053)\n\nOri Nimron discovered that the Appletalk network protocol implementation in\nthe Linux kernel did not properly perform permissions checks. A local\nattacker could use this to create a raw socket. (CVE-2019-17054)\n\nOri Nimron discovered that the modular ISDN network protocol implementation\nin the Linux kernel did not properly perform permissions checks. A local\nattacker could use this to create a raw socket. (CVE-2019-17055)\n\nOri Nimron discovered that the Near field Communication (NFC) network\nprotocol implementation in the Linux kernel did not properly perform\npermissions checks. A local attacker could use this to create a raw socket.\n(CVE-2019-17056)\n\nNico Waisman discovered that a buffer overflow existed in the Realtek Wi-Fi\ndriver for the Linux kernel when handling Notice of Absence frames. A\nphysically proximate attacker could use this to cause a denial of service\n(system crash) or possibly execute arbitrary code. (CVE-2019-17666)\n\nMaddie Stone discovered that the Binder IPC Driver implementation in the\nLinux kernel contained a use-after-free vulnerability. A local attacker\ncould use this to cause a denial of service (system crash) or possibly\nexecute arbitrary code. (CVE-2019-2215)\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],{"_key":15},"CVE-2018-12207",{"_key":17},"CVE-2019-0154",{"_key":19},"CVE-2019-0155",{"_key":21},"CVE-2019-11135",{"_key":23},"CVE-2019-15098",{"_key":25},"CVE-2019-16746",{"_key":27},"CVE-2019-17052",{"_key":29},"CVE-2019-17053",{"_key":31},"CVE-2019-17054",{"_key":33},"CVE-2019-17055",{"_key":35},"CVE-2019-17056",{"_key":37},"CVE-2019-17666",{"_key":39},"CVE-2019-2215",{"_key":41},"UBUNTU-CVE-2018-12207",{"_key":43},"UBUNTU-CVE-2019-0154",{"_key":45},"UBUNTU-CVE-2019-0155",{"_key":47},"UBUNTU-CVE-2019-11135",{"_key":49},"UBUNTU-CVE-2019-15098",{"_key":51},"UBUNTU-CVE-2019-16746",{"_key":53},"UBUNTU-CVE-2019-17052",{"_key":55},"UBUNTU-CVE-2019-17053",{"_key":57},"UBUNTU-CVE-2019-17054",{"_key":59},"UBUNTU-CVE-2019-17055",{"_key":61},"UBUNTU-CVE-2019-17056",{"_key":63},"UBUNTU-CVE-2019-17666",{"_key":65},"UBUNTU-CVE-2019-2215",[],[],[69,70,71,72,73,74,75,76,77,78,79,80,81],{"_key":41},{"_key":43},{"_key":45},{"_key":47},{"_key":49},{"_key":51},{"_key":53},{"_key":55},{"_key":57},{"_key":59},{"_key":61},{"_key":63},{"_key":65},"2019-11-13T01:06:52Z","2026-06-03T14:04:08.939288571Z",{"cisa_kev":85,"cisa_ransomware":85,"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,[87,93,98,102,106,110,114,118,122,126,130,134,138,142],{"url":88,"sources":89,"tags":91},"https://ubuntu.com/security/notices/USN-4186-1",[90],"osv_ubuntu",[92],"Advisory",{"url":94,"sources":95,"tags":96},"https://ubuntu.com/security/CVE-2018-12207",[90],[97],"REPORT",{"url":99,"sources":100,"tags":101},"https://ubuntu.com/security/CVE-2019-0154",[90],[97],{"url":103,"sources":104,"tags":105},"https://ubuntu.com/security/CVE-2019-0155",[90],[97],{"url":107,"sources":108,"tags":109},"https://ubuntu.com/security/CVE-2019-2215",[90],[97],{"url":111,"sources":112,"tags":113},"https://ubuntu.com/security/CVE-2019-11135",[90],[97],{"url":115,"sources":116,"tags":117},"https://ubuntu.com/security/CVE-2019-15098",[90],[97],{"url":119,"sources":120,"tags":121},"https://ubuntu.com/security/CVE-2019-16746",[90],[97],{"url":123,"sources":124,"tags":125},"https://ubuntu.com/security/CVE-2019-17052",[90],[97],{"url":127,"sources":128,"tags":129},"https://ubuntu.com/security/CVE-2019-17053",[90],[97],{"url":131,"sources":132,"tags":133},"https://ubuntu.com/security/CVE-2019-17054",[90],[97],{"url":135,"sources":136,"tags":137},"https://ubuntu.com/security/CVE-2019-17055",[90],[97],{"url":139,"sources":140,"tags":141},"https://ubuntu.com/security/CVE-2019-17056",[90],[97],{"url":143,"sources":144,"tags":145},"https://ubuntu.com/security/CVE-2019-17666",[90],[97],[],[],[],[150,162,168],{"ecosystem":151,"name":152,"vendor":153,"product":152,"cpe_part":9,"purl_type":154,"purl_namespace":153,"purl_name":152,"source":9,"versions":155},"Ubuntu","linux","ubuntu","deb",[156],{"version":157,"is_range":158,"range_type":159,"version_start":9,"version_start_type":9,"version_end":160,"version_end_type":161,"fixed_in":9},"lt4_4_0_168_197",true,"ecosystem","4.4.0-168.197","excluding",{"ecosystem":151,"name":163,"vendor":153,"product":163,"cpe_part":9,"purl_type":154,"purl_namespace":153,"purl_name":163,"source":9,"versions":164},"linux-aws",[165],{"version":166,"is_range":158,"range_type":159,"version_start":9,"version_start_type":9,"version_end":167,"version_end_type":161,"fixed_in":9},"lt4_4_0_1098_109","4.4.0-1098.109",{"ecosystem":151,"name":169,"vendor":153,"product":169,"cpe_part":9,"purl_type":154,"purl_namespace":153,"purl_name":169,"source":9,"versions":170},"linux-kvm",[171],{"version":172,"is_range":158,"range_type":159,"version_start":9,"version_start_type":9,"version_end":173,"version_end_type":161,"fixed_in":9},"lt4_4_0_1062_69","4.4.0-1062.69"]