[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-USN-3655-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":58,"duplicates":59,"related":60,"reserved_at":9,"published_at":72,"modified_at":73,"state":9,"summary":74,"references_raw":76,"kevs":128,"epss":9,"epss_history":129,"metrics":130,"affected":131},"USN-3655-1","linux vulnerabilities\n\nJann Horn and Ken Johnson discovered that microprocessors utilizing\nspeculative execution of a memory read may allow unauthorized memory\nreads via a sidechannel attack. This flaw is known as Spectre\nVariant 4. A local attacker could use this to expose sensitive\ninformation, including kernel memory. (CVE-2018-3639)\n\nJan H. Schönherr discovered that the Xen subsystem did not properly handle\nblock IO merges correctly in some situations. An attacker in a guest vm\ncould use this to cause a denial of service (host crash) or possibly gain\nadministrative privileges in the host. (CVE-2017-12134)\n\nIt was discovered that the Bluetooth HIP Protocol implementation in the\nLinux kernel did not properly validate HID connection setup information. An\nattacker could use this to cause a denial of service (system crash) or\npossibly execute arbitrary code. (CVE-2017-13220)\n\nIt was discovered that a buffer overread vulnerability existed in the\nkeyring subsystem of the Linux kernel. A local attacker could possibly use\nthis to expose sensitive information (kernel memory). (CVE-2017-13305)\n\nIt was discovered that the netlink subsystem in the Linux kernel did not\nproperly restrict observations of netlink messages to the appropriate net\nnamespace. A local attacker could use this to expose sensitive information\n(kernel netlink traffic). (CVE-2017-17449)\n\nIt was discovered that a race condition existed in the i8042 serial device\ndriver implementation in the Linux kernel. A physically proximate attacker\ncould use this to cause a denial of service (system crash) or possibly\nexecute arbitrary code. (CVE-2017-18079)\n\nIt was discovered that a race condition existed in the Device Mapper\ncomponent of the Linux kernel. A local attacker could use this to cause a\ndenial of service (system crash). (CVE-2017-18203)\n\nIt was discovered that a race condition existed in the OCFS2 file system\nimplementation in the Linux kernel. A local attacker could use this to\ncause a denial of service (kernel deadlock). (CVE-2017-18204)\n\nIt was discovered that an infinite loop could occur in the madvise(2)\nimplementation in the Linux kernel in certain circumstances. A local\nattacker could use this to cause a denial of service (system hang).\n(CVE-2017-18208)\n\nKefeng Wang discovered that a race condition existed in the memory locking\nimplementation in the Linux kernel. A local attacker could use this to\ncause a denial of service. (CVE-2017-18221)\n\nSilvio Cesare discovered a buffer overwrite existed in the NCPFS\nimplementation in the Linux kernel. A remote attacker controlling a\nmalicious NCPFS server could use this to cause a denial of service (system\ncrash) or possibly execute arbitrary code. (CVE-2018-8822)\n",null,[],[],[],[14,16,18,20,22,24,26,28,30,32,34,36,38,40,42,44,46,48,50,52,54,56],{"_key":15},"CVE-2017-12134",{"_key":17},"CVE-2017-13220",{"_key":19},"CVE-2017-13305",{"_key":21},"CVE-2017-17449",{"_key":23},"CVE-2017-18079",{"_key":25},"CVE-2017-18203",{"_key":27},"CVE-2017-18204",{"_key":29},"CVE-2017-18208",{"_key":31},"CVE-2017-18221",{"_key":33},"CVE-2018-3639",{"_key":35},"CVE-2018-8822",{"_key":37},"UBUNTU-CVE-2017-12134",{"_key":39},"UBUNTU-CVE-2017-13220",{"_key":41},"UBUNTU-CVE-2017-13305",{"_key":43},"UBUNTU-CVE-2017-17449",{"_key":45},"UBUNTU-CVE-2017-18079",{"_key":47},"UBUNTU-CVE-2017-18203",{"_key":49},"UBUNTU-CVE-2017-18204",{"_key":51},"UBUNTU-CVE-2017-18208",{"_key":53},"UBUNTU-CVE-2017-18221",{"_key":55},"UBUNTU-CVE-2018-3639",{"_key":57},"UBUNTU-CVE-2018-8822",[],[],[61,62,63,64,65,66,67,68,69,70,71],{"_key":37},{"_key":39},{"_key":41},{"_key":43},{"_key":45},{"_key":47},{"_key":49},{"_key":51},{"_key":53},{"_key":55},{"_key":57},"2018-05-22T03:36:42Z","2026-06-03T14:03:30.428458954Z",{"cisa_kev":75,"cisa_ransomware":75,"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,[77,83,88,92,96,100,104,108,112,116,120,124],{"url":78,"sources":79,"tags":81},"https://ubuntu.com/security/notices/USN-3655-1",[80],"osv_ubuntu",[82],"Advisory",{"url":84,"sources":85,"tags":86},"https://ubuntu.com/security/CVE-2017-12134",[80],[87],"REPORT",{"url":89,"sources":90,"tags":91},"https://ubuntu.com/security/CVE-2017-13220",[80],[87],{"url":93,"sources":94,"tags":95},"https://ubuntu.com/security/CVE-2017-13305",[80],[87],{"url":97,"sources":98,"tags":99},"https://ubuntu.com/security/CVE-2017-17449",[80],[87],{"url":101,"sources":102,"tags":103},"https://ubuntu.com/security/CVE-2017-18079",[80],[87],{"url":105,"sources":106,"tags":107},"https://ubuntu.com/security/CVE-2017-18203",[80],[87],{"url":109,"sources":110,"tags":111},"https://ubuntu.com/security/CVE-2017-18204",[80],[87],{"url":113,"sources":114,"tags":115},"https://ubuntu.com/security/CVE-2017-18208",[80],[87],{"url":117,"sources":118,"tags":119},"https://ubuntu.com/security/CVE-2017-18221",[80],[87],{"url":121,"sources":122,"tags":123},"https://ubuntu.com/security/CVE-2018-3639",[80],[87],{"url":125,"sources":126,"tags":127},"https://ubuntu.com/security/CVE-2018-8822",[80],[87],[],[],[],[132],{"ecosystem":133,"name":134,"vendor":135,"product":134,"cpe_part":9,"purl_type":136,"purl_namespace":135,"purl_name":134,"source":9,"versions":137},"Ubuntu","linux","ubuntu","deb",[138],{"version":139,"is_range":140,"range_type":141,"version_start":9,"version_start_type":9,"version_end":142,"version_end_type":143,"fixed_in":9},"lt3_13_0_149_199",true,"ecosystem","3.13.0-149.199","excluding"]