Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-54190: leds: led-core: Fix refcount leak in of_led_get()

—No exploit Fix available

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.19% (FIRST EPSS).
  • Fixed version: Linux Linux 1d6101d9222e1ca8c01b3fa9ebf0dcf7bcd82564, 690efcb5827c3bacbf1de90cd14907b91bf8cb7b, d880981b82223f9bf128dfdd2424abb0c658f345.

Low priority for now. Upgrade to Linux Linux 1d6101d9222e1ca8c01b3fa9ebf0dcf7bcd82564, 690efcb5827c3bacbf1de90cd14907b91bf8cb7b, d880981b82223f9bf128dfdd2424abb0c658f345 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: leds: led-core: Fix refcount leak in of_led_get() class_find_device_by_of_node() calls class_find_device(), it will take the reference, use the put_device() to drop the reference when not need anymore.

Published
Dec 30, 2025
Updated
Oct 28, 2026
EPSS
0.1% · 9th 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.1%

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-2023-54190

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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.

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.6affected
    • 699a8c7c4bd376aee4808e6272188319e900c8af and later · before 1d6101d9222e1ca8c01b3fa9ebf0dcf7bcd82564affected · git
    • 699a8c7c4bd376aee4808e6272188319e900c8af and later · before 690efcb5827c3bacbf1de90cd14907b91bf8cb7baffected · git
    • 699a8c7c4bd376aee4808e6272188319e900c8af and later · before d880981b82223f9bf128dfdd2424abb0c658f345affected · git
    • 699a8c7c4bd376aee4808e6272188319e900c8af and later · before ddf3e82164afd9381b1d52c9f00b3878f7b6d308affected · git
    • 699a8c7c4bd376aee4808e6272188319e900c8af and later · before da1afe8e6099980fe1e2fd7436dca284af9d3f29affected · git
    • before 5.6not affected · semver
    • 5.10.173 and later · up to and including 5.10.*not affected · semver
    • 5.15.99 and later · up to and including 5.15.*not affected · semver
    • 6.1.16 and later · up to and including 6.1.*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.20-16.1.20-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-2023-54173Dec 30, 2025 · bpf: Disable preemption in bpf_event_output
    31Monitor
  • ← EarlierCVE-2023-54189Dec 30, 2025 · pstore/ram: Add check for kstrdup
    0Monitor
  • Later →CVE-2023-54191Dec 30, 2025 · wifi: mt76: mt7996: fix memory leak in mt7996_mcu_exit
    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 Linux1d6101d9222e1ca8c01b3fa9ebf0dcf7bcd82564Vendor (CNA)
Linux Linux690efcb5827c3bacbf1de90cd14907b91bf8cb7bVendor (CNA)
Linux Linuxd880981b82223f9bf128dfdd2424abb0c658f345Vendor (CNA)
Linux Linuxda1afe8e6099980fe1e2fd7436dca284af9d3f29Vendor (CNA)
Linux Linuxddf3e82164afd9381b1d52c9f00b3878f7b6d308Vendor (CNA)
debian:linux6.1.20-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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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.

References

All records