CVE-2023-54307: ptp_qoriq: fix memory leak in probe()
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.20% (FIRST EPSS).
- Fixed version: Linux Linux 3907fcb5a439933cf8c10d6dc300bc11eba30de3, 43b4331ce0cd88ccba425e0702ba35c1a52daccf, 46c4993a1514eea3bbc7147d0c81c23cc06c6bed.
Low priority for now. Upgrade to Linux Linux 3907fcb5a439933cf8c10d6dc300bc11eba30de3, 43b4331ce0cd88ccba425e0702ba35c1a52daccf, 46c4993a1514eea3bbc7147d0c81c23cc06c6bed 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: ptp_qoriq: fix memory leak in probe() Smatch complains that: drivers/ptp/ptp_qoriq.c ptp_qoriq_probe() warn: 'base' from ioremap() not released. Fix this by revising the parameter from 'ptp_qoriq->base' to 'base'. This is only a bug if ptp_qoriq_init() returns on the first -ENODEV error path. For other error paths ptp_qoriq->base and base are the same. And this change makes the code more readable.
- Published
- Dec 30, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 10th 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.2%
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
- 5.2affected
- 7f4399ba405b6201fb318b43091703a34b1489ab and later · before 46c4993a1514eea3bbc7147d0c81c23cc06c6bedaffected · git
- 7f4399ba405b6201fb318b43091703a34b1489ab and later · before 3907fcb5a439933cf8c10d6dc300bc11eba30de3affected · git
- 7f4399ba405b6201fb318b43091703a34b1489ab and later · before c0de1a26e6595b0e7969c5b35990a77a2d93104faffected · git
- 7f4399ba405b6201fb318b43091703a34b1489ab and later · before 43b4331ce0cd88ccba425e0702ba35c1a52daccfaffected · git
- 7f4399ba405b6201fb318b43091703a34b1489ab and later · before c960785c8168d0e572101ed921b9be3934ed0bc9affected · git
- 7f4399ba405b6201fb318b43091703a34b1489ab and later · before f33642224e38d7e0d59336e10e7b4e370b1c4506affected · git
- before 5.2not affected · semver
- 5.4.240 and later · up to and including 5.4.*not affected · semver
- 5.10.177 and later · up to and including 5.10.*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.25-1 | 6.1.25-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-54304Dec 30, 2025 · firmware: meson_sm: fix to avoid potential NULL pointer dereference0Monitor
- ← EarlierCVE-2023-54305Dec 30, 2025 · ext4: refuse to create ea block when umounted0Monitor
- Later →CVE-2023-54309Dec 30, 2025 · tpm: tpm_vtpm_proxy: fix a race condition in /dev/vtpmx creation0Monitor
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 | 3907fcb5a439933cf8c10d6dc300bc11eba30de3 | Vendor (CNA) |
| Linux Linux | 43b4331ce0cd88ccba425e0702ba35c1a52daccf | Vendor (CNA) |
| Linux Linux | 46c4993a1514eea3bbc7147d0c81c23cc06c6bed | Vendor (CNA) |
| Linux Linux | c0de1a26e6595b0e7969c5b35990a77a2d93104f | Vendor (CNA) |
| Linux Linux | c960785c8168d0e572101ed921b9be3934ed0bc9 | Vendor (CNA) |
| Linux Linux | f33642224e38d7e0d59336e10e7b4e370b1c4506 | Vendor (CNA) |
| debian:linux | 6.1.25-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.
No history yet (it accumulates with the daily EPSS job).
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 (5 more)Show less
- git.kernel.org/stable/c/43b4331ce0cd88ccba425e0702ba35c1a52daccf
- git.kernel.org/stable/c/46c4993a1514eea3bbc7147d0c81c23cc06c6bed
- git.kernel.org/stable/c/c0de1a26e6595b0e7969c5b35990a77a2d93104f
- git.kernel.org/stable/c/c960785c8168d0e572101ed921b9be3934ed0bc9
- git.kernel.org/stable/c/f33642224e38d7e0d59336e10e7b4e370b1c4506
Vendor advisories and official records. Exploit/PoC links are deliberately left out.