Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-53818: ARM: zynq: Fix refcount leak in zynq_early_slcr_init

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 1cc12d10d13ae5ad8d3f7432a4c0156d221fc99b, 227f8c1c5c4b3d131b66e57e58d38054f441b915, 351b7e93d02b50b2faae2d4bda28e16a8389cbb7.

Low priority for now. Upgrade to Linux Linux 1cc12d10d13ae5ad8d3f7432a4c0156d221fc99b, 227f8c1c5c4b3d131b66e57e58d38054f441b915, 351b7e93d02b50b2faae2d4bda28e16a8389cbb7 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: ARM: zynq: Fix refcount leak in zynq_early_slcr_init of_find_compatible_node() returns a node pointer with refcount incremented, we should use of_node_put() on error path. Add missing of_node_put() to avoid refcount leak.

—No exploit Fix available
Published
Dec 8, 2025
Updated
Jun 17, 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-53818

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

    • 4.0affected
    • 3329659df0300d1d0aa22f5e7063f83a88ef92aa and later · before f00bc6727adf840eb208700ea27cda4f3742629daffected · git
    • 3329659df0300d1d0aa22f5e7063f83a88ef92aa and later · before 351b7e93d02b50b2faae2d4bda28e16a8389cbb7affected · git
    • 3329659df0300d1d0aa22f5e7063f83a88ef92aa and later · before ede0334bf4df360f4f9446075cffbbb3bc54d0b6affected · git
    • 3329659df0300d1d0aa22f5e7063f83a88ef92aa and later · before 227f8c1c5c4b3d131b66e57e58d38054f441b915affected · git
    • 3329659df0300d1d0aa22f5e7063f83a88ef92aa and later · before 1cc12d10d13ae5ad8d3f7432a4c0156d221fc99baffected · git
    • 3329659df0300d1d0aa22f5e7063f83a88ef92aa and later · before e43a06c73be4b93d308f0df809ee0023b7c37b54affected · git
    • 3329659df0300d1d0aa22f5e7063f83a88ef92aa and later · before 4c22ee805202087c2553c9175968e9e922d75bc1affected · git
    • 3329659df0300d1d0aa22f5e7063f83a88ef92aa and later · before 9eedb910a3be0005b88c696a8552c0d4c9937cd4affected · git
    • before 4.0not 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-53815Dec 8, 2025 · posix-timers: Prevent RT livelock in itimer_delete()
    0Monitor
  • ← EarlierCVE-2023-53817Dec 8, 2025 · crypto: lib/mpi - avoid null pointer deref in mpi_cmp_ui()
    30Monitor
  • Later →CVE-2023-53819Dec 8, 2025 · amdgpu: validate offset_in_bo of drm_amdgpu_gem_va
    31Monitor

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 Linux1cc12d10d13ae5ad8d3f7432a4c0156d221fc99bVendor (CNA)
Linux Linux227f8c1c5c4b3d131b66e57e58d38054f441b915Vendor (CNA)
Linux Linux351b7e93d02b50b2faae2d4bda28e16a8389cbb7Vendor (CNA)
Linux Linux4c22ee805202087c2553c9175968e9e922d75bc1Vendor (CNA)
Linux Linux9eedb910a3be0005b88c696a8552c0d4c9937cd4Vendor (CNA)
Linux Linuxe43a06c73be4b93d308f0df809ee0023b7c37b54Vendor (CNA)
Linux Linuxede0334bf4df360f4f9446075cffbbb3bc54d0b6Vendor (CNA)
Linux Linuxf00bc6727adf840eb208700ea27cda4f3742629dVendor (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.

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.

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