CVE-2023-52811
IBM VMFCS NULL Pointer Dereference
Description
In the Linux kernel, the following vulnerability has been resolved: scsi: ibmvfc: Remove BUG_ON in the case of an empty event pool In practice the driver should never send more commands than are allocated to a queue's event pool. In the unlikely event that this happens, the code asserts a BUG_ON, and in the case that the kernel is not configured to crash on panic returns a junk event pointer from the empty event list causing things to spiral from there. This BUG_ON is a historical artifact of the ibmvfc driver first being upstreamed, and it is well known now that the use of BUG_ON is bad practice except in the most unrecoverable scenario. There is nothing about this scenario that prevents the driver from recovering and carrying on. Remove the BUG_ON in question from ibmvfc_get_event() and return a NULL pointer in the case of an empty event pool. Update all call sites to ibmvfc_get_event() to check for a NULL pointer and perfrom the appropriate failure or recovery action.
INFO
Published Date :
May 21, 2024, 4:15 p.m.
Last Modified :
April 2, 2025, 3 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
3.6
Exploitability Score :
1.8
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2023-52811.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2023-52811 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2023-52811 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Apr. 02, 2025
Action Type Old Value New Value Added CWE CWE-476 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.6 up to (excluding) 6.6.3 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.5.13 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.64 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions up to (excluding) 5.15.140 Added Reference Type CVE: https://git.kernel.org/stable/c/88984ec4792766df5a9de7a2ff2b5f281f94c7d4 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/88984ec4792766df5a9de7a2ff2b5f281f94c7d4 Types: Patch Added Reference Type CVE: https://git.kernel.org/stable/c/8bbe784c2ff28d56ca0c548aaf3e584edc77052d Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/8bbe784c2ff28d56ca0c548aaf3e584edc77052d Types: Patch Added Reference Type CVE: https://git.kernel.org/stable/c/b39f2d10b86d0af353ea339e5815820026bca48f Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/b39f2d10b86d0af353ea339e5815820026bca48f Types: Patch Added Reference Type CVE: https://git.kernel.org/stable/c/d2af4ef80601224b90630c1ddc7cd2c7c8ab4dd8 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/d2af4ef80601224b90630c1ddc7cd2c7c8ab4dd8 Types: Patch Added Reference Type CVE: https://git.kernel.org/stable/c/e1d1f79b1929dce470a5dc9281c574cd58e8c6c0 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/e1d1f79b1929dce470a5dc9281c574cd58e8c6c0 Types: Patch -
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/88984ec4792766df5a9de7a2ff2b5f281f94c7d4 Added Reference https://git.kernel.org/stable/c/8bbe784c2ff28d56ca0c548aaf3e584edc77052d Added Reference https://git.kernel.org/stable/c/b39f2d10b86d0af353ea339e5815820026bca48f Added Reference https://git.kernel.org/stable/c/d2af4ef80601224b90630c1ddc7cd2c7c8ab4dd8 Added Reference https://git.kernel.org/stable/c/e1d1f79b1929dce470a5dc9281c574cd58e8c6c0 -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Oct. 31, 2024
Action Type Old Value New Value Added CVSS V3.1 CISA-ADP AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 29, 2024
Action Type Old Value New Value -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 21, 2024
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: scsi: ibmvfc: Remove BUG_ON in the case of an empty event pool In practice the driver should never send more commands than are allocated to a queue's event pool. In the unlikely event that this happens, the code asserts a BUG_ON, and in the case that the kernel is not configured to crash on panic returns a junk event pointer from the empty event list causing things to spiral from there. This BUG_ON is a historical artifact of the ibmvfc driver first being upstreamed, and it is well known now that the use of BUG_ON is bad practice except in the most unrecoverable scenario. There is nothing about this scenario that prevents the driver from recovering and carrying on. Remove the BUG_ON in question from ibmvfc_get_event() and return a NULL pointer in the case of an empty event pool. Update all call sites to ibmvfc_get_event() to check for a NULL pointer and perfrom the appropriate failure or recovery action. Added Reference kernel.org https://git.kernel.org/stable/c/e1d1f79b1929dce470a5dc9281c574cd58e8c6c0 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/88984ec4792766df5a9de7a2ff2b5f281f94c7d4 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/d2af4ef80601224b90630c1ddc7cd2c7c8ab4dd8 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/8bbe784c2ff28d56ca0c548aaf3e584edc77052d [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/b39f2d10b86d0af353ea339e5815820026bca48f [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2023-52811 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2023-52811
weaknesses.