[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-USN-5939-1":6},{"stargazers_count":4,"fetched_at":5},7,"2026-06-04T14:53:31.930Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":11,"aliases":12,"duplicate_of":9,"upstream":13,"downstream":94,"duplicates":95,"related":96,"reserved_at":9,"published_at":117,"modified_at":118,"state":9,"summary":119,"references_raw":121,"kevs":209,"epss":9,"epss_history":210,"metrics":211,"affected":212},"USN-5939-1","linux-gcp-5.4 vulnerabilities\n\nIt was discovered that the Upper Level Protocol (ULP) subsystem in the\nLinux kernel did not properly handle sockets entering the LISTEN state in\ncertain protocols, leading to a use-after-free vulnerability. A local\nattacker could use this to cause a denial of service (system crash) or\npossibly execute arbitrary code. (CVE-2023-0461)\n\nIt was discovered that the NVMe driver in the Linux kernel did not properly\nhandle reset events in some situations. A local attacker could use this to\ncause a denial of service (system crash). (CVE-2022-3169)\n\nIt was discovered that a use-after-free vulnerability existed in the SGI\nGRU driver in the Linux kernel. A local attacker could possibly use this to\ncause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2022-3424)\n\nGwangun Jung discovered a race condition in the IPv4 implementation in the\nLinux kernel when deleting multipath routes, resulting in an out-of-bounds\nread. An attacker could use this to cause a denial of service (system\ncrash) or possibly expose sensitive information (kernel memory).\n(CVE-2022-3435)\n\nIt was discovered that a race condition existed in the Kernel Connection\nMultiplexor (KCM) socket implementation in the Linux kernel when releasing\nsockets in certain situations. A local attacker could use this to cause a\ndenial of service (system crash). (CVE-2022-3521)\n\nIt was discovered that the Netronome Ethernet driver in the Linux kernel\ncontained a use-after-free vulnerability. A local attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2022-3545)\n\nIt was discovered that the hugetlb implementation in the Linux kernel\ncontained a race condition in some situations. A local attacker could use\nthis to cause a denial of service (system crash) or expose sensitive\ninformation (kernel memory). (CVE-2022-3623)\n\nZiming Zhang discovered that the VMware Virtual GPU DRM driver in the Linux\nkernel contained an out-of-bounds write vulnerability. A local attacker\ncould use this to cause a denial of service (system crash).\n(CVE-2022-36280)\n\nHyunwoo Kim discovered that the DVB Core driver in the Linux kernel did not\nproperly perform reference counting in some situations, leading to a use-\nafter-free vulnerability. A local attacker could use this to cause a denial\nof service (system crash) or possibly execute arbitrary code.\n(CVE-2022-41218)\n\nIt was discovered that the Intel i915 graphics driver in the Linux kernel\ndid not perform a GPU TLB flush in some situations. A local attacker could\nuse this to cause a denial of service or possibly execute arbitrary code.\n(CVE-2022-4139)\n\nIt was discovered that a race condition existed in the Xen network backend\ndriver in the Linux kernel when handling dropped packets in certain\ncircumstances. An attacker could use this to cause a denial of service\n(kernel deadlock). (CVE-2022-42328, CVE-2022-42329)\n\nIt was discovered that the Atmel WILC1000 driver in the Linux kernel did\nnot properly validate offsets, leading to an out-of-bounds read\nvulnerability. An attacker could use this to cause a denial of service\n(system crash). (CVE-2022-47520)\n\nIt was discovered that the network queuing discipline implementation in the\nLinux kernel contained a null pointer dereference in some situations. A\nlocal attacker could use this to cause a denial of service (system crash).\n(CVE-2022-47929)\n\nJosé Oliveira and Rodrigo Branco discovered that the prctl syscall\nimplementation in the Linux kernel did not properly protect against\nindirect branch prediction attacks in some situations. A local attacker\ncould possibly use this to expose sensitive information. (CVE-2023-0045)\n\nIt was discovered that a use-after-free vulnerability existed in the\nAdvanced Linux Sound Architecture (ALSA) subsystem. A local attacker could\nuse this to cause a denial of service (system crash). (CVE-2023-0266)\n\nKyle Zeng discovered that the IPv6 implementation in the Linux kernel\ncontained a NULL pointer dereference vulnerability in certain situations. A\nlocal attacker could use this to cause a denial of service (system crash).\n(CVE-2023-0394)\n\nIt was discovered that the Android Binder IPC subsystem in the Linux kernel\ndid not properly validate inputs in some situations, leading to a use-\nafter-free vulnerability. A local attacker could use this to cause a denial\nof service (system crash) or possibly execute arbitrary code.\n(CVE-2023-20938)\n\nKyle Zeng discovered that the class-based queuing discipline implementation\nin the Linux kernel contained a type confusion vulnerability in some\nsituations. An attacker could use this to cause a denial of service (system\ncrash). (CVE-2023-23454)\n\nKyle Zeng discovered that the ATM VC queuing discipline implementation in\nthe Linux kernel contained a type confusion vulnerability in some\nsituations. An attacker could use this to cause a denial of service (system\ncrash). (CVE-2023-23455)\n\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,74,76,78,80,82,84,86,88,90,92],{"_key":15},"CVE-2022-3169",{"_key":17},"CVE-2022-3424",{"_key":19},"CVE-2022-3435",{"_key":21},"CVE-2022-3521",{"_key":23},"CVE-2022-3545",{"_key":25},"CVE-2022-3623",{"_key":27},"CVE-2022-36280",{"_key":29},"CVE-2022-41218",{"_key":31},"CVE-2022-4139",{"_key":33},"CVE-2022-42328",{"_key":35},"CVE-2022-42329",{"_key":37},"CVE-2022-47520",{"_key":39},"CVE-2022-47929",{"_key":41},"CVE-2023-0045",{"_key":43},"CVE-2023-0266",{"_key":45},"CVE-2023-0394",{"_key":47},"CVE-2023-0461",{"_key":49},"CVE-2023-20938",{"_key":51},"CVE-2023-23454",{"_key":53},"CVE-2023-23455",{"_key":55},"UBUNTU-CVE-2022-3169",{"_key":57},"UBUNTU-CVE-2022-3424",{"_key":59},"UBUNTU-CVE-2022-3435",{"_key":61},"UBUNTU-CVE-2022-3521",{"_key":63},"UBUNTU-CVE-2022-3545",{"_key":65},"UBUNTU-CVE-2022-3623",{"_key":67},"UBUNTU-CVE-2022-36280",{"_key":69},"UBUNTU-CVE-2022-41218",{"_key":71},"UBUNTU-CVE-2022-4139",{"_key":73},"UBUNTU-CVE-2022-42328",{"_key":75},"UBUNTU-CVE-2022-42329",{"_key":77},"UBUNTU-CVE-2022-47520",{"_key":79},"UBUNTU-CVE-2022-47929",{"_key":81},"UBUNTU-CVE-2023-0045",{"_key":83},"UBUNTU-CVE-2023-0266",{"_key":85},"UBUNTU-CVE-2023-0394",{"_key":87},"UBUNTU-CVE-2023-0461",{"_key":89},"UBUNTU-CVE-2023-20938",{"_key":91},"UBUNTU-CVE-2023-23454",{"_key":93},"UBUNTU-CVE-2023-23455",[],[],[97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116],{"_key":55},{"_key":57},{"_key":59},{"_key":61},{"_key":63},{"_key":65},{"_key":67},{"_key":69},{"_key":71},{"_key":73},{"_key":75},{"_key":77},{"_key":79},{"_key":81},{"_key":83},{"_key":85},{"_key":87},{"_key":89},{"_key":91},{"_key":93},"2023-03-08T20:14:29Z","2026-06-03T14:04:05.333998555Z",{"cisa_kev":120,"cisa_ransomware":120,"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,[122,128,133,137,141,145,149,153,157,161,165,169,173,177,181,185,189,193,197,201,205],{"url":123,"sources":124,"tags":126},"https://ubuntu.com/security/notices/USN-5939-1",[125],"osv_ubuntu",[127],"Advisory",{"url":129,"sources":130,"tags":131},"https://ubuntu.com/security/CVE-2022-3169",[125],[132],"REPORT",{"url":134,"sources":135,"tags":136},"https://ubuntu.com/security/CVE-2022-3424",[125],[132],{"url":138,"sources":139,"tags":140},"https://ubuntu.com/security/CVE-2022-3435",[125],[132],{"url":142,"sources":143,"tags":144},"https://ubuntu.com/security/CVE-2022-3521",[125],[132],{"url":146,"sources":147,"tags":148},"https://ubuntu.com/security/CVE-2022-3545",[125],[132],{"url":150,"sources":151,"tags":152},"https://ubuntu.com/security/CVE-2022-3623",[125],[132],{"url":154,"sources":155,"tags":156},"https://ubuntu.com/security/CVE-2022-4139",[125],[132],{"url":158,"sources":159,"tags":160},"https://ubuntu.com/security/CVE-2022-36280",[125],[132],{"url":162,"sources":163,"tags":164},"https://ubuntu.com/security/CVE-2022-41218",[125],[132],{"url":166,"sources":167,"tags":168},"https://ubuntu.com/security/CVE-2022-42328",[125],[132],{"url":170,"sources":171,"tags":172},"https://ubuntu.com/security/CVE-2022-42329",[125],[132],{"url":174,"sources":175,"tags":176},"https://ubuntu.com/security/CVE-2022-47520",[125],[132],{"url":178,"sources":179,"tags":180},"https://ubuntu.com/security/CVE-2022-47929",[125],[132],{"url":182,"sources":183,"tags":184},"https://ubuntu.com/security/CVE-2023-0045",[125],[132],{"url":186,"sources":187,"tags":188},"https://ubuntu.com/security/CVE-2023-0266",[125],[132],{"url":190,"sources":191,"tags":192},"https://ubuntu.com/security/CVE-2023-0394",[125],[132],{"url":194,"sources":195,"tags":196},"https://ubuntu.com/security/CVE-2023-0461",[125],[132],{"url":198,"sources":199,"tags":200},"https://ubuntu.com/security/CVE-2023-20938",[125],[132],{"url":202,"sources":203,"tags":204},"https://ubuntu.com/security/CVE-2023-23454",[125],[132],{"url":206,"sources":207,"tags":208},"https://ubuntu.com/security/CVE-2023-23455",[125],[132],[],[],[],[213],{"ecosystem":214,"name":215,"vendor":216,"product":215,"cpe_part":9,"purl_type":217,"purl_namespace":216,"purl_name":215,"source":9,"versions":218},"Ubuntu","linux-gcp-5.4","ubuntu","deb",[219],{"version":220,"is_range":221,"range_type":222,"version_start":9,"version_start_type":9,"version_end":223,"version_end_type":224,"fixed_in":9},"lt5_4_0_1101_110~18_04_1",true,"ecosystem","5.4.0-1101.110~18.04.1","excluding"]