diff options
| author | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2024-05-01 15:00:38 +0200 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2024-05-01 15:00:38 +0200 |
| commit | bef2fe7ec5cf8f6b32927949179a3c5b4263992b (patch) | |
| tree | 30e570d7f9e1ca978e993e89a69de65c989c988e | |
| parent | bf81d2fa4fec1c3fa41a3ac16222ebbf7003854c (diff) | |
| download | vulns-bef2fe7ec5cf8f6b32927949179a3c5b4263992b.tar.gz | |
some cves for 6.7.12 review
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
24 files changed, 1323 insertions, 0 deletions
diff --git a/cve/reserved/2024/CVE-2024-27058 b/cve/published/2024/CVE-2024-27058 index e69de29b..e69de29b 100644 --- a/cve/reserved/2024/CVE-2024-27058 +++ b/cve/published/2024/CVE-2024-27058 diff --git a/cve/published/2024/CVE-2024-27058.json b/cve/published/2024/CVE-2024-27058.json new file mode 100644 index 00000000..ce178c92 --- /dev/null +++ b/cve/published/2024/CVE-2024-27058.json @@ -0,0 +1,118 @@ +{ + "containers": { + "cna": { + "providerMetadata": { + "orgId": "f4215fc3-5b6b-47ff-a258-f7189bd81038" + }, + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ntmpfs: fix race on handling dquot rbtree\n\nA syzkaller reproducer found a race while attempting to remove dquot\ninformation from the rb tree.\n\nFetching the rb_tree root node must also be protected by the\ndqopt->dqio_sem, otherwise, giving the right timing, shmem_release_dquot()\nwill trigger a warning because it couldn't find a node in the tree, when\nthe real reason was the root node changing before the search starts:\n\nThread 1\t\t\t\tThread 2\n- shmem_release_dquot()\t\t\t- shmem_{acquire,release}_dquot()\n\n- fetch ROOT\t\t\t\t- Fetch ROOT\n\n\t\t\t\t\t- acquire dqio_sem\n- wait dqio_sem\n\n\t\t\t\t\t- do something, triger a tree rebalance\n\t\t\t\t\t- release dqio_sem\n\n- acquire dqio_sem\n- start searching for the node, but\n from the wrong location, missing\n the node, and triggering a warning." + } + ], + "affected": [ + { + "product": "Linux", + "vendor": "Linux", + "defaultStatus": "unaffected", + "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", + "versions": [ + { + "version": "eafc474e2029", + "lessThan": "c7077f43f30d", + "status": "affected", + "versionType": "git" + }, + { + "version": "eafc474e2029", + "lessThan": "617d55b90e73", + "status": "affected", + "versionType": "git" + }, + { + "version": "eafc474e2029", + "lessThan": "f82f184874d2", + "status": "affected", + "versionType": "git" + }, + { + "version": "eafc474e2029", + "lessThan": "0a69b6b3a026", + "status": "affected", + "versionType": "git" + } + ] + }, + { + "product": "Linux", + "vendor": "Linux", + "defaultStatus": "affected", + "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", + "versions": [ + { + "version": "6.6", + "status": "affected" + }, + { + "version": "0", + "lessThan": "6.6", + "status": "unaffected", + "versionType": "custom" + }, + { + "version": "6.6.24", + "lessThanOrEqual": "6.6.*", + "status": "unaffected", + "versionType": "custom" + }, + { + "version": "6.7.12", + "lessThanOrEqual": "6.7.*", + "status": "unaffected", + "versionType": "custom" + }, + { + "version": "6.8.3", + "lessThanOrEqual": "6.8.*", + "status": "unaffected", + "versionType": "custom" + }, + { + "version": "6.9-rc2", + "lessThanOrEqual": "*", + "status": "unaffected", + "versionType": "original_commit_for_fix" + } + ] + } + ], + "references": [ + { + "url": "https://git.kernel.org/stable/c/c7077f43f30d817d10a9f8245e51576ac114b2f0" + }, + { + "url": "https://git.kernel.org/stable/c/617d55b90e73c7b4aa2733ca6cc3f9b72d1124bb" + }, + { + "url": "https://git.kernel.org/stable/c/f82f184874d2761ebaa60dccf577921a0dbb3810" + }, + { + "url": "https://git.kernel.org/stable/c/0a69b6b3a026543bc215ccc866d0aea5579e6ce2" + } + ], + "title": "tmpfs: fix race on handling dquot rbtree", + "x_generator": { + "engine": "bippy-d175d3acf727" + } + } + }, + "cveMetadata": { + "assignerOrgId": "f4215fc3-5b6b-47ff-a258-f7189bd81038", + "cveID": "CVE-2024-27058", + "requesterUserId": "gregkh@kernel.org", + "serial": "1", + "state": "PUBLISHED" + }, + "dataType": "CVE_RECORD", + "dataVersion": "5.0" +} diff --git a/cve/published/2024/CVE-2024-27058.mbox b/cve/published/2024/CVE-2024-27058.mbox new file mode 100644 index 00000000..7951d07a --- /dev/null +++ b/cve/published/2024/CVE-2024-27058.mbox @@ -0,0 +1,90 @@ +From bippy-d175d3acf727 Mon Sep 17 00:00:00 2001 +From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> +To: <linux-cve-announce@vger.kernel.org> +Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> +Subject: CVE-2024-27058: tmpfs: fix race on handling dquot rbtree +Message-Id: <2024050130-CVE-2024-27058-e8f6@gregkh> +Content-Length: 2647 +Lines: 73 +X-Developer-Signature: v=1; a=openpgp-sha256; l=2721; + i=gregkh@linuxfoundation.org; h=from:subject:message-id; + bh=9EPdpcCB62Qsv2u+0lc92Wii/U/QlSp71RIv0bUQnP0=; + b=owGbwMvMwCRo6H6F97bub03G02pJDGlGNu9Ot8iylEWssnndvaSaZ9LGvboZu/gbP385Zv9q3 + d7kGfyzO2JZGASZGGTFFFm+bOM5ur/ikKKXoe1pmDmsTCBDGLg4BWAiz1kZFmzYdzhTxqjaoepn + 4Ve7f4Vu4ptuP2WYyfhh/vSgl1oXpga2bWBvKQh5tzTfHwA= +X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; + fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 + +Description +=========== + +In the Linux kernel, the following vulnerability has been resolved: + +tmpfs: fix race on handling dquot rbtree + +A syzkaller reproducer found a race while attempting to remove dquot +information from the rb tree. + +Fetching the rb_tree root node must also be protected by the +dqopt->dqio_sem, otherwise, giving the right timing, shmem_release_dquot() +will trigger a warning because it couldn't find a node in the tree, when +the real reason was the root node changing before the search starts: + +Thread 1 Thread 2 +- shmem_release_dquot() - shmem_{acquire,release}_dquot() + +- fetch ROOT - Fetch ROOT + + - acquire dqio_sem +- wait dqio_sem + + - do something, triger a tree rebalance + - release dqio_sem + +- acquire dqio_sem +- start searching for the node, but + from the wrong location, missing + the node, and triggering a warning. + +The Linux kernel CVE team has assigned CVE-2024-27058 to this issue. + + +Affected and fixed versions +=========================== + + Issue introduced in 6.6 with commit eafc474e2029 and fixed in 6.6.24 with commit c7077f43f30d + Issue introduced in 6.6 with commit eafc474e2029 and fixed in 6.7.12 with commit 617d55b90e73 + Issue introduced in 6.6 with commit eafc474e2029 and fixed in 6.8.3 with commit f82f184874d2 + Issue introduced in 6.6 with commit eafc474e2029 and fixed in 6.9-rc2 with commit 0a69b6b3a026 + +Please see https://www.kernel.org for a full list of currently supported +kernel versions by the kernel community. + +Unaffected versions might change over time as fixes are backported to +older supported kernel versions. The official CVE entry at + https://cve.org/CVERecord/?id=CVE-2024-27058 +will be updated if fixes are backported, please check that for the most +up to date information about this issue. + + +Affected files +============== + +The file(s) affected by this issue are: + mm/shmem_quota.c + + +Mitigation +========== + +The Linux kernel CVE team recommends that you update to the latest +stable kernel version for this, and many other bugfixes. Individual +changes are never tested alone, but rather are part of a larger kernel +release. Cherry-picking individual commits is not recommended or +supported by the Linux kernel community at all. If however, updating to +the latest release is impossible, the individual changes to resolve this +issue can be found at these commits: + https://git.kernel.org/stable/c/c7077f43f30d817d10a9f8245e51576ac114b2f0 + https://git.kernel.org/stable/c/617d55b90e73c7b4aa2733ca6cc3f9b72d1124bb + https://git.kernel.org/stable/c/f82f184874d2761ebaa60dccf577921a0dbb3810 + https://git.kernel.org/stable/c/0a69b6b3a026543bc215ccc866d0aea5579e6ce2 diff --git a/cve/published/2024/CVE-2024-27058.sha1 b/cve/published/2024/CVE-2024-27058.sha1 new file mode 100644 index 00000000..ed53547f --- /dev/null +++ b/cve/published/2024/CVE-2024-27058.sha1 @@ -0,0 +1 @@ +0a69b6b3a026543bc215ccc866d0aea5579e6ce2 diff --git a/cve/reserved/2024/CVE-2024-27059 b/cve/published/2024/CVE-2024-27059 index e69de29b..e69de29b 100644 --- a/cve/reserved/2024/CVE-2024-27059 +++ b/cve/published/2024/CVE-2024-27059 diff --git a/cve/published/2024/CVE-2024-27059.json b/cve/published/2024/CVE-2024-27059.json new file mode 100644 index 00000000..452e64f9 --- /dev/null +++ b/cve/published/2024/CVE-2024-27059.json @@ -0,0 +1,178 @@ +{ + "containers": { + "cna": { + "providerMetadata": { + "orgId": "f4215fc3-5b6b-47ff-a258-f7189bd81038" + }, + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nUSB: usb-storage: Prevent divide-by-0 error in isd200_ata_command\n\nThe isd200 sub-driver in usb-storage uses the HEADS and SECTORS values\nin the ATA ID information to calculate cylinder and head values when\ncreating a CDB for READ or WRITE commands. The calculation involves\ndivision and modulus operations, which will cause a crash if either of\nthese values is 0. While this never happens with a genuine device, it\ncould happen with a flawed or subversive emulation, as reported by the\nsyzbot fuzzer.\n\nProtect against this possibility by refusing to bind to the device if\neither the ATA_ID_HEADS or ATA_ID_SECTORS value in the device's ID\ninformation is 0. This requires isd200_Initialization() to return a\nnegative error code when initialization fails; currently it always\nreturns 0 (even when there is an error)." + } + ], + "affected": [ + { + "product": "Linux", + "vendor": "Linux", + "defaultStatus": "unaffected", + "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", + "versions": [ + { + "version": "1da177e4c3f4", + "lessThan": "9968c701cba7", + "status": "affected", + "versionType": "git" + }, + { + "version": "1da177e4c3f4", + "lessThan": "eb7b01ca7781", + "status": "affected", + "versionType": "git" + }, + { + "version": "1da177e4c3f4", + "lessThan": "284fb1003d5d", + "status": "affected", + "versionType": "git" + }, + { + "version": "1da177e4c3f4", + "lessThan": "6c1f36d92c0a", + "status": "affected", + "versionType": "git" + }, + { + "version": "1da177e4c3f4", + "lessThan": "f42ba916689f", + "status": "affected", + "versionType": "git" + }, + { + "version": "1da177e4c3f4", + "lessThan": "871fd7b10b56", + "status": "affected", + "versionType": "git" + }, + { + "version": "1da177e4c3f4", + "lessThan": "3a67d4ab9e73", + "status": "affected", + "versionType": "git" + }, + { + "version": "1da177e4c3f4", + "lessThan": "014bcf41d946", + "status": "affected", + "versionType": "git" + } + ] + }, + { + "product": "Linux", + "vendor": "Linux", + "defaultStatus": "affected", + "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", + "versions": [ + { + "version": "2.6.12", + "status": "affected" + }, + { + "version": "0", + "lessThan": "2.6.12", + "status": "unaffected", + "versionType": "custom" + }, + { + "version": "4.19.312", + "lessThanOrEqual": "4.19.*", + "status": "unaffected", + "versionType": "custom" + }, + { + "version": "5.4.274", + "lessThanOrEqual": "5.4.*", + "status": "unaffected", + "versionType": "custom" + }, + { + "version": "5.10.215", + "lessThanOrEqual": "5.10.*", + "status": "unaffected", + "versionType": "custom" + }, + { + "version": "5.15.154", + "lessThanOrEqual": "5.15.*", + "status": "unaffected", + "versionType": "custom" + }, + { + "version": "6.1.84", + "lessThanOrEqual": "6.1.*", + "status": "unaffected", + "versionType": "custom" + }, + { + "version": "6.6.24", + "lessThanOrEqual": "6.6.*", + "status": "unaffected", + "versionType": "custom" + }, + { + "version": "6.7.12", + "lessThanOrEqual": "6.7.*", + "status": "unaffected", + "versionType": "custom" + }, + { + "version": "6.8", + "lessThanOrEqual": "*", + "status": "unaffected", + "versionType": "original_commit_for_fix" + } + ] + } + ], + "references": [ + { + "url": "https://git.kernel.org/stable/c/9968c701cba7eda42e5f0052b040349d6222ae34" + }, + { + "url": "https://git.kernel.org/stable/c/eb7b01ca778170654e1c76950024270ba74b121f" + }, + { + "url": "https://git.kernel.org/stable/c/284fb1003d5da111019b9e0bf99b084fd71ac133" + }, + { + "url": "https://git.kernel.org/stable/c/6c1f36d92c0a8799569055012665d2bb066fb964" + }, + { + "url": "https://git.kernel.org/stable/c/f42ba916689f5c7b1642092266d2f53cf527aaaa" + }, + { + "url": "https://git.kernel.org/stable/c/871fd7b10b56d280990b7e754f43d888382ca325" + }, + { + "url": "https://git.kernel.org/stable/c/3a67d4ab9e730361d183086dfb0ddd8c61f01636" + }, + { + "url": "https://git.kernel.org/stable/c/014bcf41d946b36a8f0b8e9b5d9529efbb822f49" + } + ], + "title": "USB: usb-storage: Prevent divide-by-0 error in isd200_ata_command", + "x_generator": { + "engine": "bippy-d175d3acf727" + } + } + }, + "cveMetadata": { + "assignerOrgId": "f4215fc3-5b6b-47ff-a258-f7189bd81038", + "cveID": "CVE-2024-27059", + "requesterUserId": "gregkh@kernel.org", + "serial": "1", + "state": "PUBLISHED" + }, + "dataType": "CVE_RECORD", + "dataVersion": "5.0" +} diff --git a/cve/published/2024/CVE-2024-27059.mbox b/cve/published/2024/CVE-2024-27059.mbox new file mode 100644 index 00000000..f3e17564 --- /dev/null +++ b/cve/published/2024/CVE-2024-27059.mbox @@ -0,0 +1,88 @@ +From bippy-d175d3acf727 Mon Sep 17 00:00:00 2001 +From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> +To: <linux-cve-announce@vger.kernel.org> +Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> +Subject: CVE-2024-27059: USB: usb-storage: Prevent divide-by-0 error in isd200_ata_command +Message-Id: <2024050130-CVE-2024-27059-baaa@gregkh> +Content-Length: 3410 +Lines: 71 +X-Developer-Signature: v=1; a=openpgp-sha256; l=3482; + i=gregkh@linuxfoundation.org; h=from:subject:message-id; + bh=OC76nA173pxrwiQyrt+4LKOnrcXGkh/rVBlPiyg/vl8=; + b=owGbwMvMwCRo6H6F97bub03G02pJDGlGNu9yDuV+u/lY4ri6cQKPie/DsMP981uLGjYb3kuqs + C8XePyvI5aFQZCJQVZMkeXLNp6j+ysOKXoZ2p6GmcPKBDKEgYtTACayM4hhDs/sHMPf2iUFv6d4 + xN6/53+BYdOXIoYF0+o8ja4lcCqt8bGVjuF3m+DwbO1sAA== +X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; + fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 + +Description +=========== + +In the Linux kernel, the following vulnerability has been resolved: + +USB: usb-storage: Prevent divide-by-0 error in isd200_ata_command + +The isd200 sub-driver in usb-storage uses the HEADS and SECTORS values +in the ATA ID information to calculate cylinder and head values when +creating a CDB for READ or WRITE commands. The calculation involves +division and modulus operations, which will cause a crash if either of +these values is 0. While this never happens with a genuine device, it +could happen with a flawed or subversive emulation, as reported by the +syzbot fuzzer. + +Protect against this possibility by refusing to bind to the device if +either the ATA_ID_HEADS or ATA_ID_SECTORS value in the device's ID +information is 0. This requires isd200_Initialization() to return a +negative error code when initialization fails; currently it always +returns 0 (even when there is an error). + +The Linux kernel CVE team has assigned CVE-2024-27059 to this issue. + + +Affected and fixed versions +=========================== + + Issue introduced in 2.6.12 with commit 1da177e4c3f4 and fixed in 4.19.312 with commit 9968c701cba7 + Issue introduced in 2.6.12 with commit 1da177e4c3f4 and fixed in 5.4.274 with commit eb7b01ca7781 + Issue introduced in 2.6.12 with commit 1da177e4c3f4 and fixed in 5.10.215 with commit 284fb1003d5d + Issue introduced in 2.6.12 with commit 1da177e4c3f4 and fixed in 5.15.154 with commit 6c1f36d92c0a + Issue introduced in 2.6.12 with commit 1da177e4c3f4 and fixed in 6.1.84 with commit f42ba916689f + Issue introduced in 2.6.12 with commit 1da177e4c3f4 and fixed in 6.6.24 with commit 871fd7b10b56 + Issue introduced in 2.6.12 with commit 1da177e4c3f4 and fixed in 6.7.12 with commit 3a67d4ab9e73 + Issue introduced in 2.6.12 with commit 1da177e4c3f4 and fixed in 6.8 with commit 014bcf41d946 + +Please see https://www.kernel.org for a full list of currently supported +kernel versions by the kernel community. + +Unaffected versions might change over time as fixes are backported to +older supported kernel versions. The official CVE entry at + https://cve.org/CVERecord/?id=CVE-2024-27059 +will be updated if fixes are backported, please check that for the most +up to date information about this issue. + + +Affected files +============== + +The file(s) affected by this issue are: + drivers/usb/storage/isd200.c + + +Mitigation +========== + +The Linux kernel CVE team recommends that you update to the latest +stable kernel version for this, and many other bugfixes. Individual +changes are never tested alone, but rather are part of a larger kernel +release. Cherry-picking individual commits is not recommended or +supported by the Linux kernel community at all. If however, updating to +the latest release is impossible, the individual changes to resolve this +issue can be found at these commits: + https://git.kernel.org/stable/c/9968c701cba7eda42e5f0052b040349d6222ae34 + https://git.kernel.org/stable/c/eb7b01ca778170654e1c76950024270ba74b121f + https://git.kernel.org/stable/c/284fb1003d5da111019b9e0bf99b084fd71ac133 + https://git.kernel.org/stable/c/6c1f36d92c0a8799569055012665d2bb066fb964 + https://git.kernel.org/stable/c/f42ba916689f5c7b1642092266d2f53cf527aaaa + https://git.kernel.org/stable/c/871fd7b10b56d280990b7e754f43d888382ca325 + https://git.kernel.org/stable/c/3a67d4ab9e730361d183086dfb0ddd8c61f01636 + https://git.kernel.org/stable/c/014bcf41d946b36a8f0b8e9b5d9529efbb822f49 diff --git a/cve/published/2024/CVE-2024-27059.sha1 b/cve/published/2024/CVE-2024-27059.sha1 new file mode 100644 index 00000000..81197202 --- /dev/null +++ b/cve/published/2024/CVE-2024-27059.sha1 @@ -0,0 +1 @@ +014bcf41d946b36a8f0b8e9b5d9529efbb822f49 diff --git a/cve/reserved/2024/CVE-2024-27060 b/cve/published/2024/CVE-2024-27060 index e69de29b..e69de29b 100644 --- a/cve/reserved/2024/CVE-2024-27060 +++ b/cve/published/2024/CVE-2024-27060 diff --git a/cve/published/2024/CVE-2024-27060.json b/cve/published/2024/CVE-2024-27060.json new file mode 100644 index 00000000..69589d62 --- /dev/null +++ b/cve/published/2024/CVE-2024-27060.json @@ -0,0 +1,88 @@ +{ + "containers": { + "cna": { + "providerMetadata": { + "orgId": "f4215fc3-5b6b-47ff-a258-f7189bd81038" + }, + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nthunderbolt: Fix NULL pointer dereference in tb_port_update_credits()\n\nOlliver reported that his system crashes when plugging in Thunderbolt 1\ndevice:\n\n BUG: kernel NULL pointer dereference, address: 0000000000000020\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\n PGD 0 P4D 0\n Oops: 0000 [#1] PREEMPT SMP NOPTI\n RIP: 0010:tb_port_do_update_credits+0x1b/0x130 [thunderbolt]\n Call Trace:\n <TASK>\n ? __die+0x23/0x70\n ? page_fault_oops+0x171/0x4e0\n ? exc_page_fault+0x7f/0x180\n ? asm_exc_page_fault+0x26/0x30\n ? tb_port_do_update_credits+0x1b/0x130\n ? tb_switch_update_link_attributes+0x83/0xd0\n tb_switch_add+0x7a2/0xfe0\n tb_scan_port+0x236/0x6f0\n tb_handle_hotplug+0x6db/0x900\n process_one_work+0x171/0x340\n worker_thread+0x27b/0x3a0\n ? __pfx_worker_thread+0x10/0x10\n kthread+0xe5/0x120\n ? __pfx_kthread+0x10/0x10\n ret_from_fork+0x31/0x50\n ? __pfx_kthread+0x10/0x10\n ret_from_fork_asm+0x1b/0x30\n </TASK>\n\nThis is due the fact that some Thunderbolt 1 devices only have one lane\nadapter. Fix this by checking for the lane 1 before we read its credits." + } + ], + "affected": [ + { + "product": "Linux", + "vendor": "Linux", + "defaultStatus": "unaffected", + "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", + "versions": [ + { + "version": "81af2952e606", + "lessThan": "ce64ba1f6ec3", + "status": "affected", + "versionType": "git" + }, + { + "version": "81af2952e606", + "lessThan": "d3d17e23d1a0", + "status": "affected", + "versionType": "git" + } + ] + }, + { + "product": "Linux", + "vendor": "Linux", + "defaultStatus": "affected", + "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", + "versions": [ + { + "version": "6.7", + "status": "affected" + }, + { + "version": "0", + "lessThan": "6.7", + "status": "unaffected", + "versionType": "custom" + }, + { + "version": "6.7.12", + "lessThanOrEqual": "6.7.*", + "status": "unaffected", + "versionType": "custom" + }, + { + "version": "6.8", + "lessThanOrEqual": "*", + "status": "unaffected", + "versionType": "original_commit_for_fix" + } + ] + } + ], + "references": [ + { + "url": "https://git.kernel.org/stable/c/ce64ba1f6ec3439e4b4d880b4db99673f4507228" + }, + { + "url": "https://git.kernel.org/stable/c/d3d17e23d1a0d1f959b4fa55b35f1802d9c584fa" + } + ], + "title": "thunderbolt: Fix NULL pointer dereference in tb_port_update_credits()", + "x_generator": { + "engine": "bippy-d175d3acf727" + } + } + }, + "cveMetadata": { + "assignerOrgId": "f4215fc3-5b6b-47ff-a258-f7189bd81038", + "cveID": "CVE-2024-27060", + "requesterUserId": "gregkh@kernel.org", + "serial": "1", + "state": "PUBLISHED" + }, + "dataType": "CVE_RECORD", + "dataVersion": "5.0" +} diff --git a/cve/published/2024/CVE-2024-27060.mbox b/cve/published/2024/CVE-2024-27060.mbox new file mode 100644 index 00000000..d328871a --- /dev/null +++ b/cve/published/2024/CVE-2024-27060.mbox @@ -0,0 +1,95 @@ +From bippy-d175d3acf727 Mon Sep 17 00:00:00 2001 +From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> +To: <linux-cve-announce@vger.kernel.org> +Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> +Subject: CVE-2024-27060: thunderbolt: Fix NULL pointer dereference in tb_port_update_credits() +Message-Id: <2024050130-CVE-2024-27060-8a1c@gregkh> +Content-Length: 2655 +Lines: 78 +X-Developer-Signature: v=1; a=openpgp-sha256; l=2734; + i=gregkh@linuxfoundation.org; h=from:subject:message-id; + bh=dQO9jbStC1+cMicosFmNmRmze4h4dhTt8BItmdbj51Y=; + b=kA0DAAIRMUfUDdst+ykByyZiAGYyPO6i0sbRGub5LVFaFEouSR1SzmiU+LbOksiaqrel17U1U + 4hdBAARAgAdFiEE9LYMxb94wiFKMT3LMUfUDdst+ykFAmYyPO4ACgkQMUfUDdst+ymz4QCgh0p8 + mnRbs5SmlAQDrzxEIwot9sAAoJ/BamnThOquW5/op9USNwuB+55Y +X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; + fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 + +Description +=========== + +In the Linux kernel, the following vulnerability has been resolved: + +thunderbolt: Fix NULL pointer dereference in tb_port_update_credits() + +Olliver reported that his system crashes when plugging in Thunderbolt 1 +device: + + BUG: kernel NULL pointer dereference, address: 0000000000000020 + #PF: supervisor read access in kernel mode + #PF: error_code(0x0000) - not-present page + PGD 0 P4D 0 + Oops: 0000 [#1] PREEMPT SMP NOPTI + RIP: 0010:tb_port_do_update_credits+0x1b/0x130 [thunderbolt] + Call Trace: + <TASK> + ? __die+0x23/0x70 + ? page_fault_oops+0x171/0x4e0 + ? exc_page_fault+0x7f/0x180 + ? asm_exc_page_fault+0x26/0x30 + ? tb_port_do_update_credits+0x1b/0x130 + ? tb_switch_update_link_attributes+0x83/0xd0 + tb_switch_add+0x7a2/0xfe0 + tb_scan_port+0x236/0x6f0 + tb_handle_hotplug+0x6db/0x900 + process_one_work+0x171/0x340 + worker_thread+0x27b/0x3a0 + ? __pfx_worker_thread+0x10/0x10 + kthread+0xe5/0x120 + ? __pfx_kthread+0x10/0x10 + ret_from_fork+0x31/0x50 + ? __pfx_kthread+0x10/0x10 + ret_from_fork_asm+0x1b/0x30 + </TASK> + +This is due the fact that some Thunderbolt 1 devices only have one lane +adapter. Fix this by checking for the lane 1 before we read its credits. + +The Linux kernel CVE team has assigned CVE-2024-27060 to this issue. + + +Affected and fixed versions +=========================== + + Issue introduced in 6.7 with commit 81af2952e606 and fixed in 6.7.12 with commit ce64ba1f6ec3 + Issue introduced in 6.7 with commit 81af2952e606 and fixed in 6.8 with commit d3d17e23d1a0 + +Please see https://www.kernel.org for a full list of currently supported +kernel versions by the kernel community. + +Unaffected versions might change over time as fixes are backported to +older supported kernel versions. The official CVE entry at + https://cve.org/CVERecord/?id=CVE-2024-27060 +will be updated if fixes are backported, please check that for the most +up to date information about this issue. + + +Affected files +============== + +The file(s) affected by this issue are: + drivers/thunderbolt/switch.c + + +Mitigation +========== + +The Linux kernel CVE team recommends that you update to the latest +stable kernel version for this, and many other bugfixes. Individual +changes are never tested alone, but rather are part of a larger kernel +release. Cherry-picking individual commits is not recommended or +supported by the Linux kernel community at all. If however, updating to +the latest release is impossible, the individual changes to resolve this +issue can be found at these commits: + https://git.kernel.org/stable/c/ce64ba1f6ec3439e4b4d880b4db99673f4507228 + https://git.kernel.org/stable/c/d3d17e23d1a0d1f959b4fa55b35f1802d9c584fa diff --git a/cve/published/2024/CVE-2024-27060.sha1 b/cve/published/2024/CVE-2024-27060.sha1 new file mode 100644 index 00000000..5990b2a0 --- /dev/null +++ b/cve/published/2024/CVE-2024-27060.sha1 @@ -0,0 +1 @@ +d3d17e23d1a0d1f959b4fa55b35f1802d9c584fa diff --git a/cve/reserved/2024/CVE-2024-27061 b/cve/published/2024/CVE-2024-27061 index e69de29b..e69de29b 100644 --- a/cve/reserved/2024/CVE-2024-27061 +++ b/cve/published/2024/CVE-2024-27061 diff --git a/cve/published/2024/CVE-2024-27061.json b/cve/published/2024/CVE-2024-27061.json new file mode 100644 index 00000000..09859384 --- /dev/null +++ b/cve/published/2024/CVE-2024-27061.json @@ -0,0 +1,103 @@ +{ + "containers": { + "cna": { + "providerMetadata": { + "orgId": "f4215fc3-5b6b-47ff-a258-f7189bd81038" + }, + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: sun8i-ce - Fix use after free in unprepare\n\nsun8i_ce_cipher_unprepare should be called before\ncrypto_finalize_skcipher_request, because client callbacks may\nimmediately free memory, that isn't needed anymore. But it will be\nused by unprepare after free. Before removing prepare/unprepare\ncallbacks it was handled by crypto engine in crypto_finalize_request.\n\nUsually that results in a pointer dereference problem during a in\ncrypto selftest.\n Unable to handle kernel NULL pointer dereference at\n virtual address 0000000000000030\n Mem abort info:\n ESR = 0x0000000096000004\n EC = 0x25: DABT (current EL), IL = 32 bits\n SET = 0, FnV = 0\n EA = 0, S1PTW = 0\n FSC = 0x04: level 0 translation fault\n Data abort info:\n ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000\n CM = 0, WnR = 0, TnD = 0, TagAccess = 0\n GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0\n user pgtable: 4k pages, 48-bit VAs, pgdp=000000004716d000\n [0000000000000030] pgd=0000000000000000, p4d=0000000000000000\n Internal error: Oops: 0000000096000004 [#1] SMP\n\nThis problem is detected by KASAN as well.\n ==================================================================\n BUG: KASAN: slab-use-after-free in sun8i_ce_cipher_do_one+0x6e8/0xf80 [sun8i_ce]\n Read of size 8 at addr ffff00000dcdc040 by task 1c15000.crypto-/373\n\n Hardware name: Pine64 PinePhone (1.2) (DT)\n Call trace:\n dump_backtrace+0x9c/0x128\n show_stack+0x20/0x38\n dump_stack_lvl+0x48/0x60\n print_report+0xf8/0x5d8\n kasan_report+0x90/0xd0\n __asan_load8+0x9c/0xc0\n sun8i_ce_cipher_do_one+0x6e8/0xf80 [sun8i_ce]\n crypto_pump_work+0x354/0x620 [crypto_engine]\n kthread_worker_fn+0x244/0x498\n kthread+0x168/0x178\n ret_from_fork+0x10/0x20\n\n Allocated by task 379:\n kasan_save_stack+0x3c/0x68\n kasan_set_track+0x2c/0x40\n kasan_save_alloc_info+0x24/0x38\n __kasan_kmalloc+0xd4/0xd8\n __kmalloc+0x74/0x1d0\n alg_test_skcipher+0x90/0x1f0\n alg_test+0x24c/0x830\n cryptomgr_test+0x38/0x60\n kthread+0x168/0x178\n ret_from_fork+0x10/0x20\n\n Freed by task 379:\n kasan_save_stack+0x3c/0x68\n kasan_set_track+0x2c/0x40\n kasan_save_free_info+0x38/0x60\n __kasan_slab_free+0x100/0x170\n slab_free_freelist_hook+0xd4/0x1e8\n __kmem_cache_free+0x15c/0x290\n kfree+0x74/0x100\n kfree_sensitive+0x80/0xb0\n alg_test_skcipher+0x12c/0x1f0\n alg_test+0x24c/0x830\n cryptomgr_test+0x38/0x60\n kthread+0x168/0x178\n ret_from_fork+0x10/0x20\n\n The buggy address belongs to the object at ffff00000dcdc000\n which belongs to the cache kmalloc-256 of size 256\n The buggy address is located 64 bytes inside of\n freed 256-byte region [ffff00000dcdc000, ffff00000dcdc100)" + } + ], + "affected": [ + { + "product": "Linux", + "vendor": "Linux", + "defaultStatus": "unaffected", + "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", + "versions": [ + { + "version": "4136212ab18e", + "lessThan": "dc60b25540c8", + "status": "affected", + "versionType": "git" + }, + { + "version": "4136212ab18e", + "lessThan": "51a7d338c212", + "status": "affected", + "versionType": "git" + }, + { + "version": "4136212ab18e", + "lessThan": "183420038444", + "status": "affected", + "versionType": "git" + } + ] + }, + { + "product": "Linux", + "vendor": "Linux", + "defaultStatus": "affected", + "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", + "versions": [ + { + "version": "6.6", + "status": "affected" + }, + { + "version": "0", + "lessThan": "6.6", + "status": "unaffected", + "versionType": "custom" + }, + { + "version": "6.6.24", + "lessThanOrEqual": "6.6.*", + "status": "unaffected", + "versionType": "custom" + }, + { + "version": "6.7.12", + "lessThanOrEqual": "6.7.*", + "status": "unaffected", + "versionType": "custom" + }, + { + "version": "6.8", + "lessThanOrEqual": "*", + "status": "unaffected", + "versionType": "original_commit_for_fix" + } + ] + } + ], + "references": [ + { + "url": "https://git.kernel.org/stable/c/dc60b25540c82fc4baa95d1458ae96ead21859e0" + }, + { + "url": "https://git.kernel.org/stable/c/51a7d338c212e0640b1aca52ba6590d5bea49879" + }, + { + "url": "https://git.kernel.org/stable/c/183420038444547c149a0fc5f58e792c2752860c" + } + ], + "title": "crypto: sun8i-ce - Fix use after free in unprepare", + "x_generator": { + "engine": "bippy-d175d3acf727" + } + } + }, + "cveMetadata": { + "assignerOrgId": "f4215fc3-5b6b-47ff-a258-f7189bd81038", + "cveID": "CVE-2024-27061", + "requesterUserId": "gregkh@kernel.org", + "serial": "1", + "state": "PUBLISHED" + }, + "dataType": "CVE_RECORD", + "dataVersion": "5.0" +} diff --git a/cve/published/2024/CVE-2024-27061.mbox b/cve/published/2024/CVE-2024-27061.mbox new file mode 100644 index 00000000..a766b0f4 --- /dev/null +++ b/cve/published/2024/CVE-2024-27061.mbox @@ -0,0 +1,139 @@ +From bippy-d175d3acf727 Mon Sep 17 00:00:00 2001 +From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> +To: <linux-cve-announce@vger.kernel.org> +Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> +Subject: CVE-2024-27061: crypto: sun8i-ce - Fix use after free in unprepare +Message-Id: <2024050130-CVE-2024-27061-fef2@gregkh> +Content-Length: 4371 +Lines: 122 +X-Developer-Signature: v=1; a=openpgp-sha256; l=4494; + i=gregkh@linuxfoundation.org; h=from:subject:message-id; + bh=X8gPaSAy34FOahfLT3KrnSEkrgMi6Z/sUAqjaHU8eGE=; + b=kA0DAAIRMUfUDdst+ykByyZiAGYyPO6h+frs2uzOFDQ5awt6L/uQ5RUDzlm1qPS2hdSKdqbao + IhdBAARAgAdFiEE9LYMxb94wiFKMT3LMUfUDdst+ykFAmYyPO4ACgkQMUfUDdst+ynhoQCeM9YL + P7s+ZDLWUBl+sNvTpWprM4UAoKrEzXDSk2Fk+y5OwQpvFUECWO7D +X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; + fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 + +Description +=========== + +In the Linux kernel, the following vulnerability has been resolved: + +crypto: sun8i-ce - Fix use after free in unprepare + +sun8i_ce_cipher_unprepare should be called before +crypto_finalize_skcipher_request, because client callbacks may +immediately free memory, that isn't needed anymore. But it will be +used by unprepare after free. Before removing prepare/unprepare +callbacks it was handled by crypto engine in crypto_finalize_request. + +Usually that results in a pointer dereference problem during a in +crypto selftest. + Unable to handle kernel NULL pointer dereference at + virtual address 0000000000000030 + Mem abort info: + ESR = 0x0000000096000004 + EC = 0x25: DABT (current EL), IL = 32 bits + SET = 0, FnV = 0 + EA = 0, S1PTW = 0 + FSC = 0x04: level 0 translation fault + Data abort info: + ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 + CM = 0, WnR = 0, TnD = 0, TagAccess = 0 + GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 + user pgtable: 4k pages, 48-bit VAs, pgdp=000000004716d000 + [0000000000000030] pgd=0000000000000000, p4d=0000000000000000 + Internal error: Oops: 0000000096000004 [#1] SMP + +This problem is detected by KASAN as well. + ================================================================== + BUG: KASAN: slab-use-after-free in sun8i_ce_cipher_do_one+0x6e8/0xf80 [sun8i_ce] + Read of size 8 at addr ffff00000dcdc040 by task 1c15000.crypto-/373 + + Hardware name: Pine64 PinePhone (1.2) (DT) + Call trace: + dump_backtrace+0x9c/0x128 + show_stack+0x20/0x38 + dump_stack_lvl+0x48/0x60 + print_report+0xf8/0x5d8 + kasan_report+0x90/0xd0 + __asan_load8+0x9c/0xc0 + sun8i_ce_cipher_do_one+0x6e8/0xf80 [sun8i_ce] + crypto_pump_work+0x354/0x620 [crypto_engine] + kthread_worker_fn+0x244/0x498 + kthread+0x168/0x178 + ret_from_fork+0x10/0x20 + + Allocated by task 379: + kasan_save_stack+0x3c/0x68 + kasan_set_track+0x2c/0x40 + kasan_save_alloc_info+0x24/0x38 + __kasan_kmalloc+0xd4/0xd8 + __kmalloc+0x74/0x1d0 + alg_test_skcipher+0x90/0x1f0 + alg_test+0x24c/0x830 + cryptomgr_test+0x38/0x60 + kthread+0x168/0x178 + ret_from_fork+0x10/0x20 + + Freed by task 379: + kasan_save_stack+0x3c/0x68 + kasan_set_track+0x2c/0x40 + kasan_save_free_info+0x38/0x60 + __kasan_slab_free+0x100/0x170 + slab_free_freelist_hook+0xd4/0x1e8 + __kmem_cache_free+0x15c/0x290 + kfree+0x74/0x100 + kfree_sensitive+0x80/0xb0 + alg_test_skcipher+0x12c/0x1f0 + alg_test+0x24c/0x830 + cryptomgr_test+0x38/0x60 + kthread+0x168/0x178 + ret_from_fork+0x10/0x20 + + The buggy address belongs to the object at ffff00000dcdc000 + which belongs to the cache kmalloc-256 of size 256 + The buggy address is located 64 bytes inside of + freed 256-byte region [ffff00000dcdc000, ffff00000dcdc100) + +The Linux kernel CVE team has assigned CVE-2024-27061 to this issue. + + +Affected and fixed versions +=========================== + + Issue introduced in 6.6 with commit 4136212ab18e and fixed in 6.6.24 with commit dc60b25540c8 + Issue introduced in 6.6 with commit 4136212ab18e and fixed in 6.7.12 with commit 51a7d338c212 + Issue introduced in 6.6 with commit 4136212ab18e and fixed in 6.8 with commit 183420038444 + +Please see https://www.kernel.org for a full list of currently supported +kernel versions by the kernel community. + +Unaffected versions might change over time as fixes are backported to +older supported kernel versions. The official CVE entry at + https://cve.org/CVERecord/?id=CVE-2024-27061 +will be updated if fixes are backported, please check that for the most +up to date information about this issue. + + +Affected files +============== + +The file(s) affected by this issue are: + drivers/crypto/allwinner/sun8i-ce/sun8i-ce-cipher.c + + +Mitigation +========== + +The Linux kernel CVE team recommends that you update to the latest +stable kernel version for this, and many other bugfixes. Individual +changes are never tested alone, but rather are part of a larger kernel +release. Cherry-picking individual commits is not recommended or +supported by the Linux kernel community at all. If however, updating to +the latest release is impossible, the individual changes to resolve this +issue can be found at these commits: + https://git.kernel.org/stable/c/dc60b25540c82fc4baa95d1458ae96ead21859e0 + https://git.kernel.org/stable/c/51a7d338c212e0640b1aca52ba6590d5bea49879 + https://git.kernel.org/stable/c/183420038444547c149a0fc5f58e792c2752860c diff --git a/cve/published/2024/CVE-2024-27061.sha1 b/cve/published/2024/CVE-2024-27061.sha1 new file mode 100644 index 00000000..2f7ced0b --- /dev/null +++ b/cve/published/2024/CVE-2024-27061.sha1 @@ -0,0 +1 @@ +183420038444547c149a0fc5f58e792c2752860c diff --git a/cve/reserved/2024/CVE-2024-27062 b/cve/published/2024/CVE-2024-27062 index e69de29b..e69de29b 100644 --- a/cve/reserved/2024/CVE-2024-27062 +++ b/cve/published/2024/CVE-2024-27062 diff --git a/cve/published/2024/CVE-2024-27062.json b/cve/published/2024/CVE-2024-27062.json new file mode 100644 index 00000000..ffa52c15 --- /dev/null +++ b/cve/published/2024/CVE-2024-27062.json @@ -0,0 +1,93 @@ +{ + "containers": { + "cna": { + "providerMetadata": { + "orgId": "f4215fc3-5b6b-47ff-a258-f7189bd81038" + }, + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnouveau: lock the client object tree.\n\nIt appears the client object tree has no locking unless I've missed\nsomething else. Fix races around adding/removing client objects,\nmostly vram bar mappings.\n\n 4562.099306] general protection fault, probably for non-canonical address 0x6677ed422bceb80c: 0000 [#1] PREEMPT SMP PTI\n[ 4562.099314] CPU: 2 PID: 23171 Comm: deqp-vk Not tainted 6.8.0-rc6+ #27\n[ 4562.099324] Hardware name: Gigabyte Technology Co., Ltd. Z390 I AORUS PRO WIFI/Z390 I AORUS PRO WIFI-CF, BIOS F8 11/05/2021\n[ 4562.099330] RIP: 0010:nvkm_object_search+0x1d/0x70 [nouveau]\n[ 4562.099503] Code: 90 90 90 90 90 90 90 90 90 90 90 90 90 66 0f 1f 00 0f 1f 44 00 00 48 89 f8 48 85 f6 74 39 48 8b 87 a0 00 00 00 48 85 c0 74 12 <48> 8b 48 f8 48 39 ce 73 15 48 8b 40 10 48 85 c0 75 ee 48 c7 c0 fe\n[ 4562.099506] RSP: 0000:ffffa94cc420bbf8 EFLAGS: 00010206\n[ 4562.099512] RAX: 6677ed422bceb814 RBX: ffff98108791f400 RCX: ffff9810f26b8f58\n[ 4562.099517] RDX: 0000000000000000 RSI: ffff9810f26b9158 RDI: ffff98108791f400\n[ 4562.099519] RBP: ffff9810f26b9158 R08: 0000000000000000 R09: 0000000000000000\n[ 4562.099521] R10: ffffa94cc420bc48 R11: 0000000000000001 R12: ffff9810f02a7cc0\n[ 4562.099526] R13: 0000000000000000 R14: 00000000000000ff R15: 0000000000000007\n[ 4562.099528] FS: 00007f629c5017c0(0000) GS:ffff98142c700000(0000) knlGS:0000000000000000\n[ 4562.099534] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 4562.099536] CR2: 00007f629a882000 CR3: 000000017019e004 CR4: 00000000003706f0\n[ 4562.099541] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[ 4562.099542] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\n[ 4562.099544] Call Trace:\n[ 4562.099555] <TASK>\n[ 4562.099573] ? die_addr+0x36/0x90\n[ 4562.099583] ? exc_general_protection+0x246/0x4a0\n[ 4562.099593] ? asm_exc_general_protection+0x26/0x30\n[ 4562.099600] ? nvkm_object_search+0x1d/0x70 [nouveau]\n[ 4562.099730] nvkm_ioctl+0xa1/0x250 [nouveau]\n[ 4562.099861] nvif_object_map_handle+0xc8/0x180 [nouveau]\n[ 4562.099986] nouveau_ttm_io_mem_reserve+0x122/0x270 [nouveau]\n[ 4562.100156] ? dma_resv_test_signaled+0x26/0xb0\n[ 4562.100163] ttm_bo_vm_fault_reserved+0x97/0x3c0 [ttm]\n[ 4562.100182] ? __mutex_unlock_slowpath+0x2a/0x270\n[ 4562.100189] nouveau_ttm_fault+0x69/0xb0 [nouveau]\n[ 4562.100356] __do_fault+0x32/0x150\n[ 4562.100362] do_fault+0x7c/0x560\n[ 4562.100369] __handle_mm_fault+0x800/0xc10\n[ 4562.100382] handle_mm_fault+0x17c/0x3e0\n[ 4562.100388] do_user_addr_fault+0x208/0x860\n[ 4562.100395] exc_page_fault+0x7f/0x200\n[ 4562.100402] asm_exc_page_fault+0x26/0x30\n[ 4562.100412] RIP: 0033:0x9b9870\n[ 4562.100419] Code: 85 a8 f7 ff ff 8b 8d 80 f7 ff ff 89 08 e9 18 f2 ff ff 0f 1f 84 00 00 00 00 00 44 89 32 e9 90 fa ff ff 0f 1f 84 00 00 00 00 00 <44> 89 32 e9 f8 f1 ff ff 0f 1f 84 00 00 00 00 00 66 44 89 32 e9 e7\n[ 4562.100422] RSP: 002b:00007fff9ba2dc70 EFLAGS: 00010246\n[ 4562.100426] RAX: 0000000000000004 RBX: 000000000dd65e10 RCX: 000000fff0000000\n[ 4562.100428] RDX: 00007f629a882000 RSI: 00007f629a882000 RDI: 0000000000000066\n[ 4562.100432] RBP: 00007fff9ba2e570 R08: 0000000000000000 R09: 0000000123ddf000\n[ 4562.100434] R10: 0000000000000001 R11: 0000000000000246 R12: 000000007fffffff\n[ 4562.100436] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000\n[ 4562.100446] </TASK>\n[ 4562.100448] Modules linked in: nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables libcrc32c nfnetlink cmac bnep sunrpc iwlmvm intel_rapl_msr intel_rapl_common snd_sof_pci_intel_cnl x86_pkg_temp_thermal intel_powerclamp snd_sof_intel_hda_common mac80211 coretemp snd_soc_acpi_intel_match kvm_intel snd_soc_acpi snd_soc_hdac_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof_intel_hda_mlink \n---truncated---" + } + ], + "affected": [ + { + "product": "Linux", + "vendor": "Linux", + "defaultStatus": "unaffected", + "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", + "versions": [ + { + "version": "1da177e4c3f4", + "lessThan": "6887314f5356", + "status": "affected", + "versionType": "git" + }, + { + "version": "1da177e4c3f4", + "lessThan": "96c875184417", + "status": "affected", + "versionType": "git" + }, + { + "version": "1da177e4c3f4", + "lessThan": "b7cc4ff787a5", + "status": "affected", + "versionType": "git" + } + ] + }, + { + "product": "Linux", + "vendor": "Linux", + "defaultStatus": "affected", + "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", + "versions": [ + { + "version": "6.6.24", + "lessThanOrEqual": "6.6.*", + "status": "unaffected", + "versionType": "custom" + }, + { + "version": "6.7.12", + "lessThanOrEqual": "6.7.*", + "status": "unaffected", + "versionType": "custom" + }, + { + "version": "6.8", + "lessThanOrEqual": "*", + "status": "unaffected", + "versionType": "original_commit_for_fix" + } + ] + } + ], + "references": [ + { + "url": "https://git.kernel.org/stable/c/6887314f5356389fc219b8152e951ac084a10ef7" + }, + { + "url": "https://git.kernel.org/stable/c/96c8751844171af4b3898fee3857ee180586f589" + }, + { + "url": "https://git.kernel.org/stable/c/b7cc4ff787a572edf2c55caeffaa88cd801eb135" + } + ], + "title": "nouveau: lock the client object tree.", + "x_generator": { + "engine": "bippy-d175d3acf727" + } + } + }, + "cveMetadata": { + "assignerOrgId": "f4215fc3-5b6b-47ff-a258-f7189bd81038", + "cveID": "CVE-2024-27062", + "requesterUserId": "gregkh@kernel.org", + "serial": "1", + "state": "PUBLISHED" + }, + "dataType": "CVE_RECORD", + "dataVersion": "5.0" +} diff --git a/cve/published/2024/CVE-2024-27062.mbox b/cve/published/2024/CVE-2024-27062.mbox new file mode 100644 index 00000000..b9fbf000 --- /dev/null +++ b/cve/published/2024/CVE-2024-27062.mbox @@ -0,0 +1,119 @@ +From bippy-d175d3acf727 Mon Sep 17 00:00:00 2001 +From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> +To: <linux-cve-announce@vger.kernel.org> +Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> +Subject: CVE-2024-27062: nouveau: lock the client object tree. +Message-Id: <2024050130-CVE-2024-27062-3291@gregkh> +Content-Length: 6430 +Lines: 102 +X-Developer-Signature: v=1; a=openpgp-sha256; l=6533; + i=gregkh@linuxfoundation.org; h=from:subject:message-id; + bh=DzblqxNx/CJg2Dvrvs8J44BziAJzWzU/MxvU6WIhrRc=; + b=owGbwMvMwCRo6H6F97bub03G02pJDGlGNu96opNk9QSMq7S8Z5urSr1iKn6lc45rw04Tfq3UV + bbzOpg6YlkYBJkYZMUUWb5s4zm6v+KQopeh7WmYOaxMIEMYuDgFYCKPJBnm2aa8cLm6iNPks6lO + pmOR6sFZnCd3M8wP5KjKqrKvnqzTGCPx80DSh+u/Kn4BAA== +X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; + fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 + +Description +=========== + +In the Linux kernel, the following vulnerability has been resolved: + +nouveau: lock the client object tree. + +It appears the client object tree has no locking unless I've missed +something else. Fix races around adding/removing client objects, +mostly vram bar mappings. + + 4562.099306] general protection fault, probably for non-canonical address 0x6677ed422bceb80c: 0000 [#1] PREEMPT SMP PTI +[ 4562.099314] CPU: 2 PID: 23171 Comm: deqp-vk Not tainted 6.8.0-rc6+ #27 +[ 4562.099324] Hardware name: Gigabyte Technology Co., Ltd. Z390 I AORUS PRO WIFI/Z390 I AORUS PRO WIFI-CF, BIOS F8 11/05/2021 +[ 4562.099330] RIP: 0010:nvkm_object_search+0x1d/0x70 [nouveau] +[ 4562.099503] Code: 90 90 90 90 90 90 90 90 90 90 90 90 90 66 0f 1f 00 0f 1f 44 00 00 48 89 f8 48 85 f6 74 39 48 8b 87 a0 00 00 00 48 85 c0 74 12 <48> 8b 48 f8 48 39 ce 73 15 48 8b 40 10 48 85 c0 75 ee 48 c7 c0 fe +[ 4562.099506] RSP: 0000:ffffa94cc420bbf8 EFLAGS: 00010206 +[ 4562.099512] RAX: 6677ed422bceb814 RBX: ffff98108791f400 RCX: ffff9810f26b8f58 +[ 4562.099517] RDX: 0000000000000000 RSI: ffff9810f26b9158 RDI: ffff98108791f400 +[ 4562.099519] RBP: ffff9810f26b9158 R08: 0000000000000000 R09: 0000000000000000 +[ 4562.099521] R10: ffffa94cc420bc48 R11: 0000000000000001 R12: ffff9810f02a7cc0 +[ 4562.099526] R13: 0000000000000000 R14: 00000000000000ff R15: 0000000000000007 +[ 4562.099528] FS: 00007f629c5017c0(0000) GS:ffff98142c700000(0000) knlGS:0000000000000000 +[ 4562.099534] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 +[ 4562.099536] CR2: 00007f629a882000 CR3: 000000017019e004 CR4: 00000000003706f0 +[ 4562.099541] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 +[ 4562.099542] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 +[ 4562.099544] Call Trace: +[ 4562.099555] <TASK> +[ 4562.099573] ? die_addr+0x36/0x90 +[ 4562.099583] ? exc_general_protection+0x246/0x4a0 +[ 4562.099593] ? asm_exc_general_protection+0x26/0x30 +[ 4562.099600] ? nvkm_object_search+0x1d/0x70 [nouveau] +[ 4562.099730] nvkm_ioctl+0xa1/0x250 [nouveau] +[ 4562.099861] nvif_object_map_handle+0xc8/0x180 [nouveau] +[ 4562.099986] nouveau_ttm_io_mem_reserve+0x122/0x270 [nouveau] +[ 4562.100156] ? dma_resv_test_signaled+0x26/0xb0 +[ 4562.100163] ttm_bo_vm_fault_reserved+0x97/0x3c0 [ttm] +[ 4562.100182] ? __mutex_unlock_slowpath+0x2a/0x270 +[ 4562.100189] nouveau_ttm_fault+0x69/0xb0 [nouveau] +[ 4562.100356] __do_fault+0x32/0x150 +[ 4562.100362] do_fault+0x7c/0x560 +[ 4562.100369] __handle_mm_fault+0x800/0xc10 +[ 4562.100382] handle_mm_fault+0x17c/0x3e0 +[ 4562.100388] do_user_addr_fault+0x208/0x860 +[ 4562.100395] exc_page_fault+0x7f/0x200 +[ 4562.100402] asm_exc_page_fault+0x26/0x30 +[ 4562.100412] RIP: 0033:0x9b9870 +[ 4562.100419] Code: 85 a8 f7 ff ff 8b 8d 80 f7 ff ff 89 08 e9 18 f2 ff ff 0f 1f 84 00 00 00 00 00 44 89 32 e9 90 fa ff ff 0f 1f 84 00 00 00 00 00 <44> 89 32 e9 f8 f1 ff ff 0f 1f 84 00 00 00 00 00 66 44 89 32 e9 e7 +[ 4562.100422] RSP: 002b:00007fff9ba2dc70 EFLAGS: 00010246 +[ 4562.100426] RAX: 0000000000000004 RBX: 000000000dd65e10 RCX: 000000fff0000000 +[ 4562.100428] RDX: 00007f629a882000 RSI: 00007f629a882000 RDI: 0000000000000066 +[ 4562.100432] RBP: 00007fff9ba2e570 R08: 0000000000000000 R09: 0000000123ddf000 +[ 4562.100434] R10: 0000000000000001 R11: 0000000000000246 R12: 000000007fffffff +[ 4562.100436] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 +[ 4562.100446] </TASK> +[ 4562.100448] Modules linked in: nf_conntrack_netbios_ns nf_conntrack_broadcast nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set nf_tables libcrc32c nfnetlink cmac bnep sunrpc iwlmvm intel_rapl_msr intel_rapl_common snd_sof_pci_intel_cnl x86_pkg_temp_thermal intel_powerclamp snd_sof_intel_hda_common mac80211 coretemp snd_soc_acpi_intel_match kvm_intel snd_soc_acpi snd_soc_hdac_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof_intel_hda_mlink snd_sof_intel_hda snd_sof kvm snd_sof_utils snd_soc_core snd_hda_codec_realtek libarc4 snd_hda_codec_generic snd_compress snd_hda_ext_core vfat fat snd_hda_intel snd_intel_dspcfg irqbypass iwlwifi snd_hda_codec snd_hwdep snd_hda_core btusb btrtl mei_hdcp iTCO_wdt rapl mei_pxp btintel snd_seq iTCO_vendor_support btbcm snd_seq_device intel_cstate bluetooth snd_pcm cfg80211 intel_wmi_thunderbolt wmi_bmof intel_uncore snd_timer mei_me snd ecdh_generic i2c_i801 +[ 4562.100541] ecc mei i2c_smbus soundcore rfkill intel_pch_thermal acpi_pad zram nouveau drm_ttm_helper ttm gpu_sched i2c_algo_bit drm_gpuvm drm_exec mxm_wmi drm_display_helper drm_kms_helper drm crct10dif_pclmul crc32_pclmul nvme e1000e crc32c_intel nvme_core ghash_clmulni_intel video wmi pinctrl_cannonlake ip6_tables ip_tables fuse +[ 4562.100616] ---[ end trace 0000000000000000 ]--- + +The Linux kernel CVE team has assigned CVE-2024-27062 to this issue. + + +Affected and fixed versions +=========================== + + Fixed in 6.6.24 with commit 6887314f5356 + Fixed in 6.7.12 with commit 96c875184417 + Fixed in 6.8 with commit b7cc4ff787a5 + +Please see https://www.kernel.org for a full list of currently supported +kernel versions by the kernel community. + +Unaffected versions might change over time as fixes are backported to +older supported kernel versions. The official CVE entry at + https://cve.org/CVERecord/?id=CVE-2024-27062 +will be updated if fixes are backported, please check that for the most +up to date information about this issue. + + +Affected files +============== + +The file(s) affected by this issue are: + drivers/gpu/drm/nouveau/include/nvkm/core/client.h + drivers/gpu/drm/nouveau/nvkm/core/client.c + drivers/gpu/drm/nouveau/nvkm/core/object.c + + +Mitigation +========== + +The Linux kernel CVE team recommends that you update to the latest +stable kernel version for this, and many other bugfixes. Individual +changes are never tested alone, but rather are part of a larger kernel +release. Cherry-picking individual commits is not recommended or +supported by the Linux kernel community at all. If however, updating to +the latest release is impossible, the individual changes to resolve this +issue can be found at these commits: + https://git.kernel.org/stable/c/6887314f5356389fc219b8152e951ac084a10ef7 + https://git.kernel.org/stable/c/96c8751844171af4b3898fee3857ee180586f589 + https://git.kernel.org/stable/c/b7cc4ff787a572edf2c55caeffaa88cd801eb135 diff --git a/cve/published/2024/CVE-2024-27062.sha1 b/cve/published/2024/CVE-2024-27062.sha1 new file mode 100644 index 00000000..079cfa83 --- /dev/null +++ b/cve/published/2024/CVE-2024-27062.sha1 @@ -0,0 +1 @@ +b7cc4ff787a572edf2c55caeffaa88cd801eb135 diff --git a/cve/reserved/2024/CVE-2024-27063 b/cve/published/2024/CVE-2024-27063 index e69de29b..e69de29b 100644 --- a/cve/reserved/2024/CVE-2024-27063 +++ b/cve/published/2024/CVE-2024-27063 diff --git a/cve/published/2024/CVE-2024-27063.json b/cve/published/2024/CVE-2024-27063.json new file mode 100644 index 00000000..2a70df5b --- /dev/null +++ b/cve/published/2024/CVE-2024-27063.json @@ -0,0 +1,118 @@ +{ + "containers": { + "cna": { + "providerMetadata": { + "orgId": "f4215fc3-5b6b-47ff-a258-f7189bd81038" + }, + "descriptions": [ + { + "lang": "en", + "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nleds: trigger: netdev: Fix kernel panic on interface rename trig notify\n\nCommit d5e01266e7f5 (\"leds: trigger: netdev: add additional specific link\nspeed mode\") in the various changes, reworked the way to set the LINKUP\nmode in commit cee4bd16c319 (\"leds: trigger: netdev: Recheck\nNETDEV_LED_MODE_LINKUP on dev rename\") and moved it to a generic function.\n\nThis changed the logic where, in the previous implementation the dev\nfrom the trigger event was used to check if the carrier was ok, but in\nthe new implementation with the generic function, the dev in\ntrigger_data is used instead.\n\nThis is problematic and cause a possible kernel panic due to the fact\nthat the dev in the trigger_data still reference the old one as the\nnew one (passed from the trigger event) still has to be hold and saved\nin the trigger_data struct (done in the NETDEV_REGISTER case).\n\nOn calling of get_device_state(), an invalid net_dev is used and this\ncause a kernel panic.\n\nTo handle this correctly, move the call to get_device_state() after the\nnew net_dev is correctly set in trigger_data (in the NETDEV_REGISTER\ncase) and correctly parse the new dev." + } + ], + "affected": [ + { + "product": "Linux", + "vendor": "Linux", + "defaultStatus": "unaffected", + "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", + "versions": [ + { + "version": "d5e01266e7f5", + "lessThan": "10f2af1af8ab", + "status": "affected", + "versionType": "git" + }, + { + "version": "d5e01266e7f5", + "lessThan": "acd025c7a7d1", + "status": "affected", + "versionType": "git" + }, + { + "version": "d5e01266e7f5", + "lessThan": "3f360227cb46", + "status": "affected", + "versionType": "git" + }, + { + "version": "d5e01266e7f5", + "lessThan": "415798bc07dd", + "status": "affected", + "versionType": "git" + } + ] + }, + { + "product": "Linux", + "vendor": "Linux", + "defaultStatus": "affected", + "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", + "versions": [ + { + "version": "6.5", + "status": "affected" + }, + { + "version": "0", + "lessThan": "6.5", + "status": "unaffected", + "versionType": "custom" + }, + { + "version": "6.6.24", + "lessThanOrEqual": "6.6.*", + "status": "unaffected", + "versionType": "custom" + }, + { + "version": "6.7.12", + "lessThanOrEqual": "6.7.*", + "status": "unaffected", + "versionType": "custom" + }, + { + "version": "6.8.3", + "lessThanOrEqual": "6.8.*", + "status": "unaffected", + "versionType": "custom" + }, + { + "version": "6.9-rc1", + "lessThanOrEqual": "*", + "status": "unaffected", + "versionType": "original_commit_for_fix" + } + ] + } + ], + "references": [ + { + "url": "https://git.kernel.org/stable/c/10f2af1af8ab8a7064f193446abd5579d3def7e3" + }, + { + "url": "https://git.kernel.org/stable/c/acd025c7a7d151261533016a6ca2d38f2de04e87" + }, + { + "url": "https://git.kernel.org/stable/c/3f360227cb46edb2cd2494128e1e06ed5768a62e" + }, + { + "url": "https://git.kernel.org/stable/c/415798bc07dd1c1ae3a656aa026580816e0b9fe8" + } + ], + "title": "leds: trigger: netdev: Fix kernel panic on interface rename trig notify", + "x_generator": { + "engine": "bippy-d175d3acf727" + } + } + }, + "cveMetadata": { + "assignerOrgId": "f4215fc3-5b6b-47ff-a258-f7189bd81038", + "cveID": "CVE-2024-27063", + "requesterUserId": "gregkh@kernel.org", + "serial": "1", + "state": "PUBLISHED" + }, + "dataType": "CVE_RECORD", + "dataVersion": "5.0" +} diff --git a/cve/published/2024/CVE-2024-27063.mbox b/cve/published/2024/CVE-2024-27063.mbox new file mode 100644 index 00000000..c2507954 --- /dev/null +++ b/cve/published/2024/CVE-2024-27063.mbox @@ -0,0 +1,88 @@ +From bippy-d175d3acf727 Mon Sep 17 00:00:00 2001 +From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> +To: <linux-cve-announce@vger.kernel.org> +Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> +Subject: CVE-2024-27063: leds: trigger: netdev: Fix kernel panic on interface rename trig notify +Message-Id: <2024050131-CVE-2024-27063-c356@gregkh> +Content-Length: 3030 +Lines: 71 +X-Developer-Signature: v=1; a=openpgp-sha256; l=3102; + i=gregkh@linuxfoundation.org; h=from:subject:message-id; + bh=AwCHilB9Y67d3bnYyyeA4ceCbP2WH8R34UfVyDtj6oc=; + b=owGbwMvMwCRo6H6F97bub03G02pJDGlGNu8/NKxqnJh044f8FfcH24uMrDcGavf9n85vHuDr8 + WFL5rPojlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZhI8zyGeYomb/dOyTAVFZVQ + NM9i8lwRWPHmDsOCm7xab3PKxNO+5C1VvXoxk8OA8cA7AA== +X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; + fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 + +Description +=========== + +In the Linux kernel, the following vulnerability has been resolved: + +leds: trigger: netdev: Fix kernel panic on interface rename trig notify + +Commit d5e01266e7f5 ("leds: trigger: netdev: add additional specific link +speed mode") in the various changes, reworked the way to set the LINKUP +mode in commit cee4bd16c319 ("leds: trigger: netdev: Recheck +NETDEV_LED_MODE_LINKUP on dev rename") and moved it to a generic function. + +This changed the logic where, in the previous implementation the dev +from the trigger event was used to check if the carrier was ok, but in +the new implementation with the generic function, the dev in +trigger_data is used instead. + +This is problematic and cause a possible kernel panic due to the fact +that the dev in the trigger_data still reference the old one as the +new one (passed from the trigger event) still has to be hold and saved +in the trigger_data struct (done in the NETDEV_REGISTER case). + +On calling of get_device_state(), an invalid net_dev is used and this +cause a kernel panic. + +To handle this correctly, move the call to get_device_state() after the +new net_dev is correctly set in trigger_data (in the NETDEV_REGISTER +case) and correctly parse the new dev. + +The Linux kernel CVE team has assigned CVE-2024-27063 to this issue. + + +Affected and fixed versions +=========================== + + Issue introduced in 6.5 with commit d5e01266e7f5 and fixed in 6.6.24 with commit 10f2af1af8ab + Issue introduced in 6.5 with commit d5e01266e7f5 and fixed in 6.7.12 with commit acd025c7a7d1 + Issue introduced in 6.5 with commit d5e01266e7f5 and fixed in 6.8.3 with commit 3f360227cb46 + Issue introduced in 6.5 with commit d5e01266e7f5 and fixed in 6.9-rc1 with commit 415798bc07dd + +Please see https://www.kernel.org for a full list of currently supported +kernel versions by the kernel community. + +Unaffected versions might change over time as fixes are backported to +older supported kernel versions. The official CVE entry at + https://cve.org/CVERecord/?id=CVE-2024-27063 +will be updated if fixes are backported, please check that for the most +up to date information about this issue. + + +Affected files +============== + +The file(s) affected by this issue are: + drivers/leds/trigger/ledtrig-netdev.c + + +Mitigation +========== + +The Linux kernel CVE team recommends that you update to the latest +stable kernel version for this, and many other bugfixes. Individual +changes are never tested alone, but rather are part of a larger kernel +release. Cherry-picking individual commits is not recommended or +supported by the Linux kernel community at all. If however, updating to +the latest release is impossible, the individual changes to resolve this +issue can be found at these commits: + https://git.kernel.org/stable/c/10f2af1af8ab8a7064f193446abd5579d3def7e3 + https://git.kernel.org/stable/c/acd025c7a7d151261533016a6ca2d38f2de04e87 + https://git.kernel.org/stable/c/3f360227cb46edb2cd2494128e1e06ed5768a62e + https://git.kernel.org/stable/c/415798bc07dd1c1ae3a656aa026580816e0b9fe8 diff --git a/cve/published/2024/CVE-2024-27063.sha1 b/cve/published/2024/CVE-2024-27063.sha1 new file mode 100644 index 00000000..90339a4d --- /dev/null +++ b/cve/published/2024/CVE-2024-27063.sha1 @@ -0,0 +1 @@ +415798bc07dd1c1ae3a656aa026580816e0b9fe8 |