CVE-2022-50669: misc: ocxl: fix possible name leak in ocxl_file_register_afu()
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 0cd05062371a49774e8a45258bdedf0bd6d3d327, 2fce8b3583d1641a1716486f408478b58e96ec91, 3299983a6bf628249ac650908e62d12de959341e.
Low priority for now. Upgrade to Linux Linux 0cd05062371a49774e8a45258bdedf0bd6d3d327, 2fce8b3583d1641a1716486f408478b58e96ec91, 3299983a6bf628249ac650908e62d12de959341e 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 name leak in ocxl_file_register_afu() If device_register() returns error in ocxl_file_register_afu(), the name allocated by dev_set_name() need be freed. As comment of device_register() says, it should use put_device() to give up the reference in the error path. So fix this by calling put_device(), then the name can be freed in kobject_cleanup(), and info is freed in info_release().
- Published
- Dec 9, 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
- 75ca758adbafc81804c39b2c200ecdc819a6c042 and later · before 0cd05062371a49774e8a45258bdedf0bd6d3d327affected · git
- 75ca758adbafc81804c39b2c200ecdc819a6c042 and later · before 7525741cb302a1672b8c3a5edb2a08e4229b5c7caffected · git
- 75ca758adbafc81804c39b2c200ecdc819a6c042 and later · before 3299983a6bf628249ac650908e62d12de959341eaffected · git
- 75ca758adbafc81804c39b2c200ecdc819a6c042 and later · before 557b7de055d1e230ddb6664c29d26917b8db9143affected · git
- 75ca758adbafc81804c39b2c200ecdc819a6c042 and later · before 2fce8b3583d1641a1716486f408478b58e96ec91affected · git
- 75ca758adbafc81804c39b2c200ecdc819a6c042 and later · before a4cb1004aeed2ab893a058fad00a5b41a12c4691affected · git
- before 5.2not affected · semver
- 5.4.229 and later · up to and including 5.4.*not affected · semver
- 5.10.163 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.4-1 | 6.1.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-2022-50667Dec 9, 2025 · drm/vmwgfx: Fix memory leak in vmw_mksstat_add_ioctl()0Monitor
- ← EarlierCVE-2022-50668Dec 9, 2025 · ext4: fix deadlock due to mbcache entry corruption30Monitor
- Later →CVE-2022-50670Dec 9, 2025 · mmc: omap_hsmmc: fix return value check of mmc_add_host()0Monitor
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 | 0cd05062371a49774e8a45258bdedf0bd6d3d327 | Vendor (CNA) |
| Linux Linux | 2fce8b3583d1641a1716486f408478b58e96ec91 | Vendor (CNA) |
| Linux Linux | 3299983a6bf628249ac650908e62d12de959341e | Vendor (CNA) |
| Linux Linux | 557b7de055d1e230ddb6664c29d26917b8db9143 | Vendor (CNA) |
| Linux Linux | 7525741cb302a1672b8c3a5edb2a08e4229b5c7c | Vendor (CNA) |
| Linux Linux | a4cb1004aeed2ab893a058fad00a5b41a12c4691 | Vendor (CNA) |
| debian:linux | 6.1.4-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 (5 more)Show less
- git.kernel.org/stable/c/2fce8b3583d1641a1716486f408478b58e96ec91
- git.kernel.org/stable/c/3299983a6bf628249ac650908e62d12de959341e
- git.kernel.org/stable/c/557b7de055d1e230ddb6664c29d26917b8db9143
- git.kernel.org/stable/c/7525741cb302a1672b8c3a5edb2a08e4229b5c7c
- git.kernel.org/stable/c/a4cb1004aeed2ab893a058fad00a5b41a12c4691
Vendor advisories and official records. Exploit/PoC links are deliberately left out.