scsi: lpfc: Fix ioremap issues in lpfc_sli4_pci_mem_setup()
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Fixed version: Linux Linux 631d0fab143bef85ea0813596f1dda36e2b9724c, 74d90f92eafe8ccd12827228236a28a94eda6bcc, 7e5a54d1f00725a739dcd20f616d82eff4f764bd.
Low priority for now. Upgrade to Linux Linux 631d0fab143bef85ea0813596f1dda36e2b9724c, 74d90f92eafe8ccd12827228236a28a94eda6bcc, 7e5a54d1f00725a739dcd20f616d82eff4f764bd or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Dec 7, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.17affected
- 1351e69fc6db30e186295f1c9495d03cef6a01a2 and later · before 74d90f92eafe8ccd12827228236a28a94eda6bccaffected · git
- 1351e69fc6db30e186295f1c9495d03cef6a01a2 and later · before bab8dc38b1a0a12bc064fc064269033bdcf5b88eaffected · git
- 1351e69fc6db30e186295f1c9495d03cef6a01a2 and later · before fd8c83d8375b9dac1949f2753485a5c055ebfad0affected · git
- 1351e69fc6db30e186295f1c9495d03cef6a01a2 and later · before e6f1ef4a53856ed000b0f7265d7e16dcb00f4243affected · git
- 1351e69fc6db30e186295f1c9495d03cef6a01a2 and later · before 631d0fab143bef85ea0813596f1dda36e2b9724caffected · git
- 1351e69fc6db30e186295f1c9495d03cef6a01a2 and later · before 7e5a54d1f00725a739dcd20f616d82eff4f764bdaffected · git
- 1351e69fc6db30e186295f1c9495d03cef6a01a2 and later · before 91a0c0c1413239d0548b5aac4c82f38f6d53a91eaffected · git
- before 4.17not affected · semver
- 5.4.243 and later · up to and including 5.4.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.37-1 | 6.1.37-1 |
| Debian:13 | linux | before 6.3.7-1 | 6.3.7-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-53751Dec 7, 2025 · cifs: fix potential use-after-free bugs in TCP_Server_Info::hostname39Monitor
- ← EarlierCVE-2023-53752Dec 7, 2025 · net: deal with integer overflows in kmalloc_reserve()31Monitor
- Later →CVE-2023-53755Dec 7, 2025 · dmaengine: ptdma: check for null desc before calling pt_cmd_callback0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 631d0fab143bef85ea0813596f1dda36e2b9724c | Vendor (CNA) |
| Linux Linux | 74d90f92eafe8ccd12827228236a28a94eda6bcc | Vendor (CNA) |
| Linux Linux | 7e5a54d1f00725a739dcd20f616d82eff4f764bd | Vendor (CNA) |
| Linux Linux | 91a0c0c1413239d0548b5aac4c82f38f6d53a91e | Vendor (CNA) |
| Linux Linux | bab8dc38b1a0a12bc064fc064269033bdcf5b88e | Vendor (CNA) |
| Linux Linux | e6f1ef4a53856ed000b0f7265d7e16dcb00f4243 | Vendor (CNA) |
| Linux Linux | fd8c83d8375b9dac1949f2753485a5c055ebfad0 | Vendor (CNA) |
| debian:linux | 6.1.37-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/74d90f92eafe8ccd12827228236a28a94eda6bcc
- git.kernel.org/stable/c/7e5a54d1f00725a739dcd20f616d82eff4f764bd
- git.kernel.org/stable/c/91a0c0c1413239d0548b5aac4c82f38f6d53a91e
- git.kernel.org/stable/c/bab8dc38b1a0a12bc064fc064269033bdcf5b88e
- git.kernel.org/stable/c/e6f1ef4a53856ed000b0f7265d7e16dcb00f4243
- git.kernel.org/stable/c/fd8c83d8375b9dac1949f2753485a5c055ebfad0
Vendor advisories and official records. Exploit/PoC links are deliberately left out.