[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024102106-CVE-2024-47731-fd73@gregkh>
Date: Mon, 21 Oct 2024 14:16:10 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-47731: drivers/perf: Fix ali_drw_pmu driver interrupt status clearing
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drivers/perf: Fix ali_drw_pmu driver interrupt status clearing
The alibaba_uncore_pmu driver forgot to clear all interrupt status
in the interrupt processing function. After the PMU counter overflow
interrupt occurred, an interrupt storm occurred, causing the system
to hang.
Therefore, clear the correct interrupt status in the interrupt handling
function to fix it.
The Linux kernel CVE team has assigned CVE-2024-47731 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.1 with commit cf7b61073e45 and fixed in 6.1.113 with commit 24f30b34ff76
Issue introduced in 6.1 with commit cf7b61073e45 and fixed in 6.6.54 with commit 3b839d461904
Issue introduced in 6.1 with commit cf7b61073e45 and fixed in 6.10.13 with commit 062b7176e484
Issue introduced in 6.1 with commit cf7b61073e45 and fixed in 6.11.2 with commit 85702fddba70
Issue introduced in 6.1 with commit cf7b61073e45 and fixed in 6.12-rc1 with commit a3dd920977dc
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-47731
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/perf/alibaba_uncore_drw_pmu.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/24f30b34ff76648d26872dd4eaa002f074225058
https://git.kernel.org/stable/c/3b839d4619042b02eecdfc986484ac6e6be6acbf
https://git.kernel.org/stable/c/062b7176e484678b2c9072d28fbecea47846b274
https://git.kernel.org/stable/c/85702fddba70d2b63f5646793d77de2ad4fc3784
https://git.kernel.org/stable/c/a3dd920977dccc453c550260c4b7605b280b79c3
Powered by blists - more mailing lists