{"id":"USN-6331-1","summary":"linux-azure vulnerabilities","details":"It was discovered that the netlink implementation in the Linux kernel did\nnot properly validate policies when parsing attributes in some situations.\nAn attacker could use this to cause a denial of service (infinite\nrecursion). (CVE-2020-36691)\n\nBilly Jheng Bing Jhong discovered that the CIFS network file system\nimplementation in the Linux kernel did not properly validate arguments to\nioctl() in some situations. A local attacker could possibly use this to\ncause a denial of service (system crash). (CVE-2022-0168)\n\nIt was discovered that the ext4 file system implementation in the Linux\nkernel contained a use-after-free vulnerability. An attacker could use this\nto construct a malicious ext4 file system image that, when mounted, could\ncause a denial of service (system crash). (CVE-2022-1184)\n\nIt was discovered that some AMD x86-64 processors with SMT enabled could\nspeculatively execute instructions using a return address from a sibling\nthread. A local attacker could possibly use this to expose sensitive\ninformation. (CVE-2022-27672)\n\nDaniel Moghimi discovered that some Intel(R) Processors did not properly\nclear microarchitectural state after speculative execution of various\ninstructions. A local unprivileged user could use this to obtain to\nsensitive information. (CVE-2022-40982)\n\nWilliam Zhao discovered that the Traffic Control (TC) subsystem in the\nLinux kernel did not properly handle network packet retransmission in\ncertain situations. A local attacker could use this to cause a denial of\nservice (kernel deadlock). (CVE-2022-4269)\n\nIt was discovered that a race condition existed in the qdisc implementation\nin the Linux kernel, 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-0590)\n\nIt was discovered that a race condition existed in the btrfs file system\nimplementation in the Linux kernel, leading to a use-after-free\nvulnerability. A local attacker could use this to cause a denial of service\n(system crash) or possibly expose sensitive information. (CVE-2023-1611)\n\nIt was discovered that the APM X-Gene SoC hardware monitoring driver in the\nLinux kernel contained a race condition, leading to a use-after-free\nvulnerability. A local attacker could use this to cause a denial of service\n(system crash) or expose sensitive information (kernel memory).\n(CVE-2023-1855)\n\nIt was discovered that the ST NCI NFC driver did not properly handle device\nremoval events. A physically proximate attacker could use this to cause a\ndenial of service (system crash). (CVE-2023-1990)\n\nTavis Ormandy discovered that some AMD processors did not properly handle\nspeculative execution of certain vector register instructions. A local\nattacker could use this to expose sensitive information. (CVE-2023-20593)\n\nIt was discovered that the XFS file system implementation in the Linux\nkernel did not properly perform metadata validation when mounting certain\nimages. An attacker could use this to specially craft a file system image\nthat, when mounted, could cause a denial of service (system crash).\n(CVE-2023-2124)\n\nIt was discovered that the SLIMpro I2C device driver in the Linux kernel\ndid not properly validate user-supplied data in some situations, leading to\nan out-of-bounds write vulnerability. A privileged attacker could use this\nto cause a denial of service (system crash) or possibly execute arbitrary\ncode. (CVE-2023-2194)\n\nIt was discovered that a race condition existed in the TLS subsystem in the\nLinux kernel, leading to a use-after-free or a null pointer dereference\nvulnerability. A local attacker could use this to cause a denial of service\n(system crash) or possibly execute arbitrary code. (CVE-2023-28466)\n\nIt was discovered that the DA9150 charger driver in the Linux kernel did\nnot properly handle device removal, leading to a user-after free\nvulnerability. A physically proximate attacker could use this to cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2023-30772)\n\nIt was discovered that the btrfs file system implementation in the Linux\nkernel did not properly handle error conditions in some situations, leading\nto a use-after-free vulnerability. A local attacker could possibly use this\nto cause a denial of service (system crash). (CVE-2023-3111)\n\nIt was discovered that the Ricoh R5C592 MemoryStick card reader driver in\nthe Linux kernel contained a race condition during module unload, leading\nto a use-after-free vulnerability. A local attacker could use this to cause\na denial of service (system crash) or possibly execute arbitrary code.\n(CVE-2023-3141)\n\nIt was discovered that the Qualcomm EMAC ethernet driver in the Linux\nkernel did not properly handle device removal, leading to a user-after free\nvulnerability. A physically proximate attacker could use this to cause a\ndenial of service (system crash) or possibly execute arbitrary code.\n(CVE-2023-33203)\n\nIt was discovered that the universal 32bit network packet classifier\nimplementation in the Linux kernel did not properly perform reference\ncounting in some situations, leading to a use-after-free vulnerability. A\nlocal attacker could use this to cause a denial of service (system crash)\nor possibly execute arbitrary code. (CVE-2023-3609)\n\nIt was discovered that the Quick Fair Queueing network scheduler\nimplementation in the Linux kernel contained an out-of-bounds write\nvulnerability. A local attacker could use this to cause a denial of service\n(system crash) or possibly execute arbitrary code. (CVE-2023-3611)\n\nIt was discovered that the network packet classifier with\nnetfilter/firewall marks implementation in the Linux kernel did not\nproperly handle reference counting, leading to a use-after-free\nvulnerability. A local attacker could use this to cause a denial of service\n(system crash) or possibly execute arbitrary code. (CVE-2023-3776)\n\n","modified":"2026-02-10T04:43:17Z","published":"2023-08-31T22:31:05Z","related":["UBUNTU-CVE-2020-36691","UBUNTU-CVE-2022-0168","UBUNTU-CVE-2022-1184","UBUNTU-CVE-2022-27672","UBUNTU-CVE-2022-40982","UBUNTU-CVE-2022-4269","UBUNTU-CVE-2023-0590","UBUNTU-CVE-2023-1611","UBUNTU-CVE-2023-1855","UBUNTU-CVE-2023-1990","UBUNTU-CVE-2023-20593","UBUNTU-CVE-2023-2124","UBUNTU-CVE-2023-2194","UBUNTU-CVE-2023-28466","UBUNTU-CVE-2023-30772","UBUNTU-CVE-2023-3111","UBUNTU-CVE-2023-3141","UBUNTU-CVE-2023-33203","UBUNTU-CVE-2023-3609","UBUNTU-CVE-2023-3611","UBUNTU-CVE-2023-3776"],"upstream":["CVE-2020-36691","CVE-2022-0168","CVE-2022-1184","CVE-2022-27672","CVE-2022-40982","CVE-2022-4269","CVE-2023-0590","CVE-2023-1611","CVE-2023-1855","CVE-2023-1990","CVE-2023-20593","CVE-2023-2124","CVE-2023-2194","CVE-2023-28466","CVE-2023-30772","CVE-2023-3111","CVE-2023-3141","CVE-2023-33203","CVE-2023-3609","CVE-2023-3611","CVE-2023-3776","UBUNTU-CVE-2020-36691","UBUNTU-CVE-2022-0168","UBUNTU-CVE-2022-1184","UBUNTU-CVE-2022-27672","UBUNTU-CVE-2022-40982","UBUNTU-CVE-2022-4269","UBUNTU-CVE-2023-0590","UBUNTU-CVE-2023-1611","UBUNTU-CVE-2023-1855","UBUNTU-CVE-2023-1990","UBUNTU-CVE-2023-20593","UBUNTU-CVE-2023-2124","UBUNTU-CVE-2023-2194","UBUNTU-CVE-2023-28466","UBUNTU-CVE-2023-30772","UBUNTU-CVE-2023-3111","UBUNTU-CVE-2023-3141","UBUNTU-CVE-2023-33203","UBUNTU-CVE-2023-3609","UBUNTU-CVE-2023-3611","UBUNTU-CVE-2023-3776"],"references":[{"type":"ADVISORY","url":"https://ubuntu.com/security/notices/USN-6331-1"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2020-36691"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2022-0168"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2022-1184"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2022-4269"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2022-27672"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2022-40982"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2023-0590"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2023-1611"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2023-1855"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2023-1990"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2023-2124"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2023-2194"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2023-3111"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2023-3141"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2023-3609"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2023-3611"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2023-3776"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2023-20593"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2023-28466"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2023-30772"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2023-33203"}],"affected":[{"package":{"name":"linux-azure","ecosystem":"Ubuntu:20.04:LTS","purl":"pkg:deb/ubuntu/linux-azure@5.4.0-1114.120?arch=source&distro=focal"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-1114.120"}]}],"versions":["5.3.0-1003.3","5.3.0-1008.9","5.3.0-1009.10","5.4.0-1006.6","5.4.0-1008.8","5.4.0-1009.9","5.4.0-1010.10","5.4.0-1012.12","5.4.0-1016.16","5.4.0-1019.19","5.4.0-1020.20","5.4.0-1022.22","5.4.0-1023.23","5.4.0-1025.25","5.4.0-1026.26","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1034.35","5.4.0-1035.36","5.4.0-1036.38","5.4.0-1039.41","5.4.0-1040.42","5.4.0-1041.43","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1047.49","5.4.0-1048.50","5.4.0-1049.51","5.4.0-1051.53","5.4.0-1055.57","5.4.0-1056.58","5.4.0-1058.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1064.67","5.4.0-1065.68","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1069.72","5.4.0-1070.73","5.4.0-1072.75","5.4.0-1073.76","5.4.0-1074.77","5.4.0-1077.80","5.4.0-1078.81","5.4.0-1080.83","5.4.0-1083.87","5.4.0-1085.90","5.4.0-1086.91","5.4.0-1089.94","5.4.0-1090.95","5.4.0-1091.96","5.4.0-1094.100","5.4.0-1095.101","5.4.0-1098.104","5.4.0-1100.106","5.4.0-1101.107","5.4.0-1103.109","5.4.0-1104.110","5.4.0-1105.111","5.4.0-1106.112","5.4.0-1107.113","5.4.0-1108.114","5.4.0-1109.115","5.4.0-1110.116","5.4.0-1111.117","5.4.0-1112.118","5.4.0-1113.119"],"ecosystem_specific":{"availability":"No subscription required","binaries":[{"binary_version":"5.4.0-1114.120","binary_name":"linux-azure-cloud-tools-5.4.0-1114"},{"binary_version":"5.4.0-1114.120","binary_name":"linux-azure-headers-5.4.0-1114"},{"binary_version":"5.4.0-1114.120","binary_name":"linux-azure-tools-5.4.0-1114"},{"binary_version":"5.4.0-1114.120","binary_name":"linux-buildinfo-5.4.0-1114-azure"},{"binary_version":"5.4.0-1114.120","binary_name":"linux-cloud-tools-5.4.0-1114-azure"},{"binary_version":"5.4.0-1114.120","binary_name":"linux-headers-5.4.0-1114-azure"},{"binary_version":"5.4.0-1114.120","binary_name":"linux-image-unsigned-5.4.0-1114-azure"},{"binary_version":"5.4.0-1114.120","binary_name":"linux-modules-5.4.0-1114-azure"},{"binary_version":"5.4.0-1114.120","binary_name":"linux-modules-extra-5.4.0-1114-azure"},{"binary_version":"5.4.0-1114.120","binary_name":"linux-tools-5.4.0-1114-azure"}]},"database_specific":{"cves_map":{"ecosystem":"Ubuntu:20.04:LTS","cves":[{"severity":[{"score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","type":"CVSS_V3"},{"score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","type":"CVSS_V3"},{"score":"medium","type":"Ubuntu"}],"id":"CVE-2020-36691"},{"severity":[{"score":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H","type":"CVSS_V3"},{"score":"medium","type":"Ubuntu"}],"id":"CVE-2022-0168"},{"severity":[{"score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","type":"CVSS_V3"},{"score":"medium","type":"Ubuntu"}],"id":"CVE-2022-1184"},{"severity":[{"score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","type":"CVSS_V3"},{"score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","type":"CVSS_V3"},{"score":"medium","type":"Ubuntu"}],"id":"CVE-2022-4269"},{"severity":[{"score":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N","type":"CVSS_V3"},{"score":"medium","type":"Ubuntu"}],"id":"CVE-2022-27672"},{"severity":[{"score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","type":"CVSS_V3"},{"score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","type":"CVSS_V3"},{"score":"medium","type":"Ubuntu"}],"id":"CVE-2022-40982"},{"severity":[{"score":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","type":"CVSS_V3"},{"score":"medium","type":"Ubuntu"}],"id":"CVE-2023-0590"},{"severity":[{"score":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:H","type":"CVSS_V3"},{"score":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:H","type":"CVSS_V3"},{"score":"low","type":"Ubuntu"}],"id":"CVE-2023-1611"},{"severity":[{"score":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:H","type":"CVSS_V3"},{"score":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:H","type":"CVSS_V3"},{"score":"low","type":"Ubuntu"}],"id":"CVE-2023-1855"},{"severity":[{"score":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","type":"CVSS_V3"},{"score":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","type":"CVSS_V3"},{"score":"low","type":"Ubuntu"}],"id":"CVE-2023-1990"},{"severity":[{"score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","type":"CVSS_V3"},{"score":"low","type":"Ubuntu"}],"id":"CVE-2023-2124"},{"severity":[{"score":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","type":"CVSS_V3"},{"score":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","type":"CVSS_V3"},{"score":"medium","type":"Ubuntu"}],"id":"CVE-2023-2194"},{"severity":[{"score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","type":"CVSS_V3"},{"score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","type":"CVSS_V3"},{"score":"medium","type":"Ubuntu"}],"id":"CVE-2023-3111"},{"severity":[{"score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","type":"CVSS_V3"},{"score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","type":"CVSS_V3"},{"score":"low","type":"Ubuntu"}],"id":"CVE-2023-3141"},{"severity":[{"score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","type":"CVSS_V3"},{"score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","type":"CVSS_V3"},{"score":"high","type":"Ubuntu"}],"id":"CVE-2023-3609"},{"severity":[{"score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","type":"CVSS_V3"},{"score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","type":"CVSS_V3"},{"score":"high","type":"Ubuntu"}],"id":"CVE-2023-3611"},{"severity":[{"score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","type":"CVSS_V3"},{"score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","type":"CVSS_V3"},{"score":"high","type":"Ubuntu"}],"id":"CVE-2023-3776"},{"severity":[{"score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","type":"CVSS_V3"},{"score":"high","type":"Ubuntu"}],"id":"CVE-2023-20593"},{"severity":[{"score":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","type":"CVSS_V3"},{"score":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","type":"CVSS_V3"},{"score":"medium","type":"Ubuntu"}],"id":"CVE-2023-28466"},{"severity":[{"score":"CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","type":"CVSS_V3"},{"score":"CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","type":"CVSS_V3"},{"score":"low","type":"Ubuntu"}],"id":"CVE-2023-30772"},{"severity":[{"score":"CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","type":"CVSS_V3"},{"score":"CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","type":"CVSS_V3"},{"score":"low","type":"Ubuntu"}],"id":"CVE-2023-33203"}]},"source":"https://github.com/canonical/ubuntu-security-notices/blob/main/osv/usn/USN-6331-1.json"}}],"schema_version":"1.7.3"}