Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-50559: clk: imx: scu: fix memleak on platform_device_add() fails

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.21% (FIRST EPSS).
  • Fixed version: Linux Linux 05fe0b3d69b8e094db207648ab21cade56d71cd8, 43c589b7a187ef481b594317eaab8c8f269e4a68, 855ae87a2073ebf1b395e020de54fdf9ce7d166f.

Low priority for now. Upgrade to Linux Linux 05fe0b3d69b8e094db207648ab21cade56d71cd8, 43c589b7a187ef481b594317eaab8c8f269e4a68, 855ae87a2073ebf1b395e020de54fdf9ce7d166f 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: clk: imx: scu: fix memleak on platform_device_add() fails No error handling is performed when platform_device_add() fails. Add error processing before return, and modified the return value.

—No exploit Fix available
Published
Oct 22, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 11th percentile
CWE
—

Report tools

JSON

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.

Follow CVE-2022-50559

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.11affected
    • 77d8f3068c63ee0983f0b5ba3207d3f7cce11be4 and later · before 9209e6bab75d4008d9f4248c66008f3ffd24c931affected · git
    • 77d8f3068c63ee0983f0b5ba3207d3f7cce11be4 and later · before 43c589b7a187ef481b594317eaab8c8f269e4a68affected · git
    • 77d8f3068c63ee0983f0b5ba3207d3f7cce11be4 and later · before 05fe0b3d69b8e094db207648ab21cade56d71cd8affected · git
    • 77d8f3068c63ee0983f0b5ba3207d3f7cce11be4 and later · before 855ae87a2073ebf1b395e020de54fdf9ce7d166faffected · git
    • before 5.11not affected · semver
    • 5.15.75 and later · up to and including 5.15.*not affected · semver
    • 5.19.17 and later · up to and including 5.19.*not affected · semver
    • 6.0.3 and later · up to and including 6.0.*not affected · semver
    • 6.1 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.0.3-16.0.3-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2022-50557Oct 22, 2025 · pinctrl: thunderbay: fix possible memory leak in thunderbay_build_functions()
    0Monitor
  • ← EarlierCVE-2022-50558Oct 22, 2025 · regmap-irq: Use the new num_config_regs property in regmap_add_irq_chip_fwnode
    0Monitor
  • Later →CVE-2022-50560Oct 22, 2025 · drm/meson: explicitly remove aggregate driver at module unload time
    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 / packageFixed versionSource
Linux Linux05fe0b3d69b8e094db207648ab21cade56d71cd8Vendor (CNA)
Linux Linux43c589b7a187ef481b594317eaab8c8f269e4a68Vendor (CNA)
Linux Linux855ae87a2073ebf1b395e020de54fdf9ce7d166fVendor (CNA)
Linux Linux9209e6bab75d4008d9f4248c66008f3ffd24c931Vendor (CNA)
debian:linux6.0.3-1 · Debian:12Package 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 researchers

Finders, 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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records