Skip to content
Noroxi
CVE-2022-50834· NVD / CVE Program· CNA Linux

nfc: Fix potential resource leaks

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 277f0d0a9084e7454e5532c823a7a876a7b00af7, a743128fca394a43425020a4f287d3168d94d04f, b32f6bef248562bb5191ada527717ea50b319466.

Low priority for now. Upgrade to Linux Linux 277f0d0a9084e7454e5532c823a7a876a7b00af7, a743128fca394a43425020a4f287d3168d94d04f, b32f6bef248562bb5191ada527717ea50b319466 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: nfc: Fix potential resource leaks nfc_get_device() take reference for the device, add missing nfc_put_device() to release it when not need anymore. Also fix the style warnning by use error EOPNOTSUPP instead of ENOTSUPP.

—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-50834

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.

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

    • 3.13affected
    • 5ce3f32b5264b337bfd13a780452a17705307725 and later · before 277f0d0a9084e7454e5532c823a7a876a7b00af7affected · git
    • 5ce3f32b5264b337bfd13a780452a17705307725 and later · before d1d912e7f82d7216ba4e266048ec1d1f5ea93839affected · git
    • 5ce3f32b5264b337bfd13a780452a17705307725 and later · before d8e410315ad393b23520b5db0706be853589c548affected · git
    • 5ce3f32b5264b337bfd13a780452a17705307725 and later · before e0f5c962c066e769c187f037fedc883f8abd4e82affected · git
    • 5ce3f32b5264b337bfd13a780452a17705307725 and later · before b63bc2db244c1b57e36f16ea5f2a1becda413f68affected · git
    • 5ce3f32b5264b337bfd13a780452a17705307725 and later · before a743128fca394a43425020a4f287d3168d94d04faffected · git
    • 5ce3f32b5264b337bfd13a780452a17705307725 and later · before b32f6bef248562bb5191ada527717ea50b319466affected · git
    • 5ce3f32b5264b337bfd13a780452a17705307725 and later · before df49908f3c52d211aea5e2a14a93bbe67a2cb3afaffected · git
    • before 3.13not 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.7-16.1.7-1

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-50832Dec 30, 2025 · wifi: wilc1000: fix potential memory leak in wilc_mac_xmit()
    0Monitor
  • ← EarlierCVE-2022-50833Dec 30, 2025 · Bluetooth: use hdev->workqueue when queuing hdev->{cmd,ncmd}_timer works
    0Monitor
  • Later →CVE-2022-50835Dec 30, 2025 · jbd2: add miss release buffer head in fc_do_one_pass()
    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 Linux277f0d0a9084e7454e5532c823a7a876a7b00af7Vendor (CNA)
Linux Linuxa743128fca394a43425020a4f287d3168d94d04fVendor (CNA)
Linux Linuxb32f6bef248562bb5191ada527717ea50b319466Vendor (CNA)
Linux Linuxb63bc2db244c1b57e36f16ea5f2a1becda413f68Vendor (CNA)
Linux Linuxd1d912e7f82d7216ba4e266048ec1d1f5ea93839Vendor (CNA)
Linux Linuxd8e410315ad393b23520b5db0706be853589c548Vendor (CNA)
Linux Linuxdf49908f3c52d211aea5e2a14a93bbe67a2cb3afVendor (CNA)
Linux Linuxe0f5c962c066e769c187f037fedc883f8abd4e82Vendor (CNA)
debian:linux6.1.7-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.

EPSS, last 120 days

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.

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

All records