CVE-2023-53746: s390/vfio-ap: fix memory leak in vfio_ap device driver
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 5195de1d5f66b276683240a896783f7f43c4f664, 6a40fda14b4be3e38f03cc42ffd4efbc64fb3e67, 7b6a02f5bf15931464c79dfd487c57f76aae3496.
Low priority for now. Upgrade to Linux Linux 5195de1d5f66b276683240a896783f7f43c4f664, 6a40fda14b4be3e38f03cc42ffd4efbc64fb3e67, 7b6a02f5bf15931464c79dfd487c57f76aae3496 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: s390/vfio-ap: fix memory leak in vfio_ap device driver The device release callback function invoked to release the matrix device uses the dev_get_drvdata(device *dev) function to retrieve the pointer to the vfio_matrix_dev object in order to free its storage. The problem is, this object is not stored as drvdata with the device; since the kfree function will accept a NULL pointer, the memory for the vfio_matrix_dev object is never freed. Since the device being released is contained within the vfio_matrix_dev object, the container_of macro will be used to retrieve its pointer.
- 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.20affected
- 1fde573413b549d52183382e639c1d6ce88f5959 and later · before 5195de1d5f66b276683240a896783f7f43c4f664affected · git
- 1fde573413b549d52183382e639c1d6ce88f5959 and later · before ee17dea3072dec0bc34399a32fa884e26342e4eaaffected · git
- 1fde573413b549d52183382e639c1d6ce88f5959 and later · before aa2bff25e9bb10c935c7ffe3d5f5975bdccb1749affected · git
- 1fde573413b549d52183382e639c1d6ce88f5959 and later · before 6a40fda14b4be3e38f03cc42ffd4efbc64fb3e67affected · git
- 1fde573413b549d52183382e639c1d6ce88f5959 and later · before 7b6a02f5bf15931464c79dfd487c57f76aae3496affected · git
- 1fde573413b549d52183382e639c1d6ce88f5959 and later · before 8f8cf767589f2131ae5d40f3758429095c701c84affected · git
- before 4.20not 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-53744Dec 7, 2025 · soc: ti: pm33xx: Fix refcount leak in am33xx_pm_probe0Monitor
- ← EarlierCVE-2023-53745Dec 7, 2025 · um: vector: Fix memory leak in vector_config0Monitor
- Later →CVE-2023-53748Dec 7, 2025 · media: mediatek: vcodec: Fix potential array out-of-bounds in decoder queue_setup28Monitor
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 | 5195de1d5f66b276683240a896783f7f43c4f664 | Vendor (CNA) |
| Linux Linux | 6a40fda14b4be3e38f03cc42ffd4efbc64fb3e67 | Vendor (CNA) |
| Linux Linux | 7b6a02f5bf15931464c79dfd487c57f76aae3496 | Vendor (CNA) |
| Linux Linux | 8f8cf767589f2131ae5d40f3758429095c701c84 | Vendor (CNA) |
| Linux Linux | aa2bff25e9bb10c935c7ffe3d5f5975bdccb1749 | Vendor (CNA) |
| Linux Linux | ee17dea3072dec0bc34399a32fa884e26342e4ea | 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/6a40fda14b4be3e38f03cc42ffd4efbc64fb3e67
- git.kernel.org/stable/c/7b6a02f5bf15931464c79dfd487c57f76aae3496
- git.kernel.org/stable/c/8f8cf767589f2131ae5d40f3758429095c701c84
- git.kernel.org/stable/c/aa2bff25e9bb10c935c7ffe3d5f5975bdccb1749
- git.kernel.org/stable/c/ee17dea3072dec0bc34399a32fa884e26342e4ea
Vendor advisories and official records. Exploit/PoC links are deliberately left out.