CVE-2022-50742: misc: ocxl: fix possible refcount leak in afu_ioctl()
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.25% (FIRST EPSS).
- Fixed version: Linux Linux 11bd8bbdf8f6f5c1145bb158793107a57e3a1f07, 66032c43291672bae8b93184d2806f05be3e16df, 7ba19a60c74fb0057d4daef2fa2cbfc9522f3ba1.
Low priority for now. Upgrade to Linux Linux 11bd8bbdf8f6f5c1145bb158793107a57e3a1f07, 66032c43291672bae8b93184d2806f05be3e16df, 7ba19a60c74fb0057d4daef2fa2cbfc9522f3ba1 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: misc: ocxl: fix possible refcount leak in afu_ioctl() eventfd_ctx_put need to be called to put the refcount that gotten by eventfd_ctx_fdget when ocxl_irq_set_handler fails.
- Published
- Dec 24, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 16th 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
- 060146614643ddc5978c73ffac0329762b4651c9 and later · before fc797285c40a9cc441357abb3521d3e51c743f67affected · git
- 060146614643ddc5978c73ffac0329762b4651c9 and later · before 7ba19a60c74fb0057d4daef2fa2cbfc9522f3ba1affected · git
- 060146614643ddc5978c73ffac0329762b4651c9 and later · before 11bd8bbdf8f6f5c1145bb158793107a57e3a1f07affected · git
- 060146614643ddc5978c73ffac0329762b4651c9 and later · before 843433a02e344d30fbb62dfd834c60631baaa527affected · git
- 060146614643ddc5978c73ffac0329762b4651c9 and later · before 66032c43291672bae8b93184d2806f05be3e16dfaffected · git
- 060146614643ddc5978c73ffac0329762b4651c9 and later · before c3b69ba5114c860d730870c03ab4ee45276e5e35affected · git
- before 5.2not affected · semver
- 5.4.220 and later · up to and including 5.4.*not affected · semver
- 5.10.150 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.0.3-1 | 6.0.3-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-2022-50740Dec 24, 2025 · wifi: ath9k: hif_usb: fix memory leak of urbs in ath9k_hif_usb_dealloc_tx_urbs()0Monitor
- ← EarlierCVE-2022-50741Dec 24, 2025 · media: imx-jpeg: Disable useless interrupt to avoid kernel panic0Monitor
- Later →CVE-2022-50743Dec 24, 2025 · erofs: Fix pcluster memleak when its block address is zero0Monitor
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 | 11bd8bbdf8f6f5c1145bb158793107a57e3a1f07 | Vendor (CNA) |
| Linux Linux | 66032c43291672bae8b93184d2806f05be3e16df | Vendor (CNA) |
| Linux Linux | 7ba19a60c74fb0057d4daef2fa2cbfc9522f3ba1 | Vendor (CNA) |
| Linux Linux | 843433a02e344d30fbb62dfd834c60631baaa527 | Vendor (CNA) |
| Linux Linux | c3b69ba5114c860d730870c03ab4ee45276e5e35 | Vendor (CNA) |
| Linux Linux | fc797285c40a9cc441357abb3521d3e51c743f67 | Vendor (CNA) |
| debian:linux | 6.0.3-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/66032c43291672bae8b93184d2806f05be3e16df
- git.kernel.org/stable/c/7ba19a60c74fb0057d4daef2fa2cbfc9522f3ba1
- git.kernel.org/stable/c/843433a02e344d30fbb62dfd834c60631baaa527
- git.kernel.org/stable/c/c3b69ba5114c860d730870c03ab4ee45276e5e35
- git.kernel.org/stable/c/fc797285c40a9cc441357abb3521d3e51c743f67
Vendor advisories and official records. Exploit/PoC links are deliberately left out.