Linux Kernel up to 6.3.1 scsi lpfc_sli4_pci_mem_setup null pointer dereference

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Linux Kernel up to 6.3.1. It has been rated as critical. This affects the function lpfc_sli4_pci_mem_setup of the component scsi. This manipulation causes null pointer dereference.
This vulnerability is registered as CVE-2023-53754. No exploit is available.
Upgrading the affected component is advised.
Details
A vulnerability has been found in Linux Kernel up to 6.3.1 and classified as critical. Affected by this vulnerability is the function lpfc_sli4_pci_mem_setup of the component scsi. The manipulation with an unknown input leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. As an impact it is known to affect availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix ioremap issues in lpfc_sli4_pci_mem_setup() When if_type equals zero and pci_resource_start(pdev, PCI_64BIT_BAR4) returns false, drbl_regs_memmap_p is not remapped. This passes a NULL pointer to iounmap(), which can trigger a WARN() on certain arches. When if_type equals six and pci_resource_start(pdev, PCI_64BIT_BAR4) returns true, drbl_regs_memmap_p may has been remapped and ctrl_regs_memmap_p is not remapped. This is a resource leak and passes a NULL pointer to iounmap(). To fix these issues, we need to add null checks before iounmap(), and change some goto labels.
The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2023-53754 since 12/08/2025. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 277771 (Linux Distros Unpatched Vulnerability : CVE-2023-53754), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 5.4.243, 5.10.180, 5.15.111, 6.1.28, 6.2.15 or 6.3.2 eliminates this vulnerability. Applying the patch 74d90f92eafe8ccd12827228236a28a94eda6bcc/bab8dc38b1a0a12bc064fc064269033bdcf5b88e/fd8c83d8375b9dac1949f2753485a5c055ebfad0/e6f1ef4a53856ed000b0f7265d7e16dcb00f4243/631d0fab143bef85ea0813596f1dda36e2b9724c/7e5a54d1f00725a739dcd20f616d82eff4f764bd/91a0c0c1413239d0548b5aac4c82f38f6d53a91e is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (277771), EUVD (EUVD-2023-60074) and CERT Bund (WID-SEC-2025-2756). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- Google Container-Optimized OS
- Debian Linux
- Amazon Linux 2
- Red Hat Enterprise Linux
- Ubuntu Linux
- SUSE Linux
- Oracle Linux
- NetApp FAS
- NetApp AFF
- SUSE openSUSE
- RESF Rocky Linux
- Open Source Linux Kernel
- Microsoft Azure Linux
Product
Type
Vendor
Name
Version
- 5.4.242
- 5.10.179
- 5.15.110
- 6.1.0
- 6.1.1
- 6.1.2
- 6.1.3
- 6.1.4
- 6.1.5
- 6.1.6
- 6.1.7
- 6.1.8
- 6.1.9
- 6.1.10
- 6.1.11
- 6.1.12
- 6.1.13
- 6.1.14
- 6.1.15
- 6.1.16
- 6.1.17
- 6.1.18
- 6.1.19
- 6.1.20
- 6.1.21
- 6.1.22
- 6.1.23
- 6.1.24
- 6.1.25
- 6.1.26
- 6.1.27
- 6.2.0
- 6.2.1
- 6.2.2
- 6.2.3
- 6.2.4
- 6.2.5
- 6.2.6
- 6.2.7
- 6.2.8
- 6.2.9
- 6.2.10
- 6.2.11
- 6.2.12
- 6.2.13
- 6.2.14
- 6.3.0
- 6.3.1
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.7
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 277771
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2023-53754
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 5.4.243/5.10.180/5.15.111/6.1.28/6.2.15/6.3.2
Patch: 74d90f92eafe8ccd12827228236a28a94eda6bcc/bab8dc38b1a0a12bc064fc064269033bdcf5b88e/fd8c83d8375b9dac1949f2753485a5c055ebfad0/e6f1ef4a53856ed000b0f7265d7e16dcb00f4243/631d0fab143bef85ea0813596f1dda36e2b9724c/7e5a54d1f00725a739dcd20f616d82eff4f764bd/91a0c0c1413239d0548b5aac4c82f38f6d53a91e
Timeline
12/08/2025 Advisory disclosed12/08/2025 CVE reserved
12/08/2025 VulDB entry created
02/23/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2023-53754 (🔒)
GCVE (CVE): GCVE-0-2023-53754
GCVE (VulDB): GCVE-100-334705
EUVD: 🔒
CERT Bund: WID-SEC-2025-2756 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service
Entry
Created: 12/08/2025 06:16Updated: 02/23/2026 01:30
Changes: 12/08/2025 06:16 (59), 12/08/2025 10:45 (1), 12/09/2025 03:32 (7), 12/09/2025 06:20 (2), 12/24/2025 05:27 (1), 01/04/2026 10:35 (1), 01/22/2026 05:53 (1), 02/23/2026 01:30 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.