aboutsummaryrefslogtreecommitdiffstats
path: root/cve/published/2024/CVE-2024-26655.mbox
diff options
context:
space:
mode:
Diffstat (limited to 'cve/published/2024/CVE-2024-26655.mbox')
-rw-r--r--cve/published/2024/CVE-2024-26655.mbox17
1 files changed, 5 insertions, 12 deletions
diff --git a/cve/published/2024/CVE-2024-26655.mbox b/cve/published/2024/CVE-2024-26655.mbox
index 09d2dc47..1f1b2266 100644
--- a/cve/published/2024/CVE-2024-26655.mbox
+++ b/cve/published/2024/CVE-2024-26655.mbox
@@ -1,19 +1,8 @@
-From bippy-b4257b672505 Mon Sep 17 00:00:00 2001
+From bippy-d3b290d2becc 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-26655: Fix memory leak in posix_clock_open()
-Message-Id: <2024040124-CVE-2024-26655-265a@gregkh>
-Content-Length: 1586
-Lines: 48
-X-Developer-Signature: v=1; a=openpgp-sha256; l=1635;
- i=gregkh@linuxfoundation.org; h=from:subject:message-id;
- bh=a5i7wrJFzySBsggnfUflXDMhVjseuVn8CX4H+NNZQvE=;
- b=owGbwMvMwCRo6H6F97bub03G02pJDGlcpye0z9XYtpCvO4tpLqeTCOMmw/YTy0VKkrbcUWzWP
- jVJZYpBRywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAEykzoZhfnqcy/xDL87cr1yZ
- v/W7pdG1LV90uRgWXF4ge/BpoNL7i2VaRRwrJvvM3fH1LAA=
-X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp;
- fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29
Description
===========
@@ -33,6 +22,8 @@ The Linux kernel CVE team has assigned CVE-2024-26655 to this issue.
Affected and fixed versions
===========================
+ Issue introduced in 6.7 with commit 60c6946675fc and fixed in 6.7.12 with commit a88649b49523
+ Issue introduced in 6.7 with commit 60c6946675fc and fixed in 6.8.3 with commit 0200dd7ed233
Issue introduced in 6.7 with commit 60c6946675fc and fixed in 6.9-rc2 with commit 5b4cdd9c5676
Please see https://www.kernel.org for a full list of currently supported
@@ -62,4 +53,6 @@ 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/a88649b49523e8cbe95254440d803e38c19d2341
+ https://git.kernel.org/stable/c/0200dd7ed2335469955d7e69cc1a6fa7df1f3847
https://git.kernel.org/stable/c/5b4cdd9c5676559b8a7c944ac5269b914b8c0bb8