CVE-2023-54315: powerpc/powernv/sriov: perform null check on iov before dereferencing iov
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 07c19c0ad4b07f4b598da369714de028f6a6a323, 6314465b88072a6b6f3b3c12a7898abe09095f95, 72990144e17e5e2cb378f1d9b10530b85b9bc382.
Low priority for now. Upgrade to Linux Linux 07c19c0ad4b07f4b598da369714de028f6a6a323, 6314465b88072a6b6f3b3c12a7898abe09095f95, 72990144e17e5e2cb378f1d9b10530b85b9bc382 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: powerpc/powernv/sriov: perform null check on iov before dereferencing iov Currently pointer iov is being dereferenced before the null check of iov which can lead to null pointer dereference errors. Fix this by moving the iov null check before the dereferencing. Detected using cppcheck static analysis: linux/arch/powerpc/platforms/powernv/pci-sriov.c:597:12: warning: Either the condition '!iov' is redundant or there is possible null pointer dereference: iov. [nullPointerRedundantCheck] num_vfs = iov->num_vfs; ^
- Published
- Dec 30, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- —
Report tools
Action score
0
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.
Is your version affected? Check itNoroxi 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
- 5.9affected
- 052da31d45fc71238ea8bed7e9a84648a1ee0bf3 and later · before 07c19c0ad4b07f4b598da369714de028f6a6a323affected · git
- 052da31d45fc71238ea8bed7e9a84648a1ee0bf3 and later · before d3a0d96c16e5f8d55e2c70163abda3c7c8328106affected · git
- 052da31d45fc71238ea8bed7e9a84648a1ee0bf3 and later · before d9a1aaea856002cb58dfb7c8d8770400fa1a0299affected · git
- 052da31d45fc71238ea8bed7e9a84648a1ee0bf3 and later · before 6314465b88072a6b6f3b3c12a7898abe09095f95affected · git
- 052da31d45fc71238ea8bed7e9a84648a1ee0bf3 and later · before 72990144e17e5e2cb378f1d9b10530b85b9bc382affected · git
- 052da31d45fc71238ea8bed7e9a84648a1ee0bf3 and later · before f4f913c980bc6abe0ccfe88fe3909c125afe4a2daffected · git
- before 5.9not affected · semver
- 5.10.188 and later · up to and including 5.10.*not affected · semver
- 5.15.121 and later · up to and including 5.15.*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.52-1 | 6.1.52-1 |
| Debian:13 | linux | before 6.4.4-1 | 6.4.4-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-54313Dec 30, 2025 · ovl: fix null pointer dereference in ovl_get_acl_rcu()0Monitor
- ← EarlierCVE-2023-54314Dec 30, 2025 · media: af9005: Fix null-ptr-deref in af9005_i2c_xfer0Monitor
- Later →CVE-2023-54316Dec 30, 2025 · refscale: Fix uninitalized use of wait_queue_head_t0Monitor
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 | 07c19c0ad4b07f4b598da369714de028f6a6a323 | Vendor (CNA) |
| Linux Linux | 6314465b88072a6b6f3b3c12a7898abe09095f95 | Vendor (CNA) |
| Linux Linux | 72990144e17e5e2cb378f1d9b10530b85b9bc382 | Vendor (CNA) |
| Linux Linux | d3a0d96c16e5f8d55e2c70163abda3c7c8328106 | Vendor (CNA) |
| Linux Linux | d9a1aaea856002cb58dfb7c8d8770400fa1a0299 | Vendor (CNA) |
| Linux Linux | f4f913c980bc6abe0ccfe88fe3909c125afe4a2d | Vendor (CNA) |
| debian:linux | 6.1.52-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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/6314465b88072a6b6f3b3c12a7898abe09095f95
- git.kernel.org/stable/c/72990144e17e5e2cb378f1d9b10530b85b9bc382
- git.kernel.org/stable/c/d3a0d96c16e5f8d55e2c70163abda3c7c8328106
- git.kernel.org/stable/c/d9a1aaea856002cb58dfb7c8d8770400fa1a0299
- git.kernel.org/stable/c/f4f913c980bc6abe0ccfe88fe3909c125afe4a2d
Vendor advisories and official records. Exploit/PoC links are deliberately left out.