Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-50836: remoteproc: sysmon: fix memory leak in qcom_add_sysmon_subdev()

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 131c0a3ead78d45f0f39ddb42cf1bd9be26239b0, 1a62bebe0705556d37cfa8409ddc759b11d404f6, 27441fab2651cd909d8a5440ca079bc50245f427.

Low priority for now. Upgrade to Linux Linux 131c0a3ead78d45f0f39ddb42cf1bd9be26239b0, 1a62bebe0705556d37cfa8409ddc759b11d404f6, 27441fab2651cd909d8a5440ca079bc50245f427 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: remoteproc: sysmon: fix memory leak in qcom_add_sysmon_subdev() The kfree() should be called when of_irq_get_byname() fails or devm_request_threaded_irq() fails in qcom_add_sysmon_subdev(), otherwise there will be a memory leak, so add kfree() to fix it.

—No exploit Fix available
Published
Dec 30, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 16th 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-50836

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.1affected
    • 027045a6e2b7cd81216e8a559534a30fb0782702 and later · before 27441fab2651cd909d8a5440ca079bc50245f427affected · git
    • 027045a6e2b7cd81216e8a559534a30fb0782702 and later · before e4539eb5c0c342567183fe386d0699c8dab49490affected · git
    • 027045a6e2b7cd81216e8a559534a30fb0782702 and later · before 131c0a3ead78d45f0f39ddb42cf1bd9be26239b0affected · git
    • 027045a6e2b7cd81216e8a559534a30fb0782702 and later · before 1a62bebe0705556d37cfa8409ddc759b11d404f6affected · git
    • 027045a6e2b7cd81216e8a559534a30fb0782702 and later · before ec97e9a5c2f25d2f9f9d7005e9ac67f23cc751cdaffected · git
    • 027045a6e2b7cd81216e8a559534a30fb0782702 and later · before e01ce676aaef3b13d02343d7e70f9637d93a3367affected · git
    • before 5.1not 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.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.4-16.1.4-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-50834Dec 30, 2025 · nfc: Fix potential resource leaks
    0Monitor
  • ← EarlierCVE-2022-50835Dec 30, 2025 · jbd2: add miss release buffer head in fc_do_one_pass()
    0Monitor
  • Later →CVE-2022-50837Dec 30, 2025 · net: dsa: tag_8021q: avoid leaking ctx on dsa_tag_8021q_register() error path
    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 Linux131c0a3ead78d45f0f39ddb42cf1bd9be26239b0Vendor (CNA)
Linux Linux1a62bebe0705556d37cfa8409ddc759b11d404f6Vendor (CNA)
Linux Linux27441fab2651cd909d8a5440ca079bc50245f427Vendor (CNA)
Linux Linuxe01ce676aaef3b13d02343d7e70f9637d93a3367Vendor (CNA)
Linux Linuxe4539eb5c0c342567183fe386d0699c8dab49490Vendor (CNA)
Linux Linuxec97e9a5c2f25d2f9f9d7005e9ac67f23cc751cdVendor (CNA)
debian:linux6.1.4-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 (5 more)

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

All records