Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-53000: netlink: prevent potential spectre v1 gadgets

Noroxi assessment

Priority: Monitor (action score 31/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).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 3e5082b1c66c7783fbcd79b5b178573230e528ff, 41b74e95f297ac360ca7ed6bf200100717cb6c45, 539ca5dcbc91134bbe2c45677811c31d8b030d2d.

Low priority for now. Upgrade to Linux Linux 3e5082b1c66c7783fbcd79b5b178573230e528ff, 41b74e95f297ac360ca7ed6bf200100717cb6c45, 539ca5dcbc91134bbe2c45677811c31d8b030d2d 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: netlink: prevent potential spectre v1 gadgets Most netlink attributes are parsed and validated from __nla_validate_parse() or validate_nla() u16 type = nla_type(nla); if (type == 0 || type > maxtype) { /* error or continue */ } @type is then used as an array index and can be used as a Spectre v1 gadget. array_index_nospec() can be used to prevent leaking content of kernel memory to malicious users. This should take care of vast majority of netlink uses, but an audit is needed to take care of others where validation is not yet centralized in core netlink functions.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Mar 27, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 12th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
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-2023-53000

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.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel2.6.15 and later · before 5.4.231
  • linux linux kernel5.5 and later · before 5.10.166
  • linux linux kernel5.11 and later · before 5.15.91
  • linux linux kernel5.16 and later · before 6.1.9
  • linux linux kernel6.2

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

    • 2.6.15affected
    • bfa83a9e03cf8d501c6272999843470afecb32ed and later · before 3e5082b1c66c7783fbcd79b5b178573230e528ffaffected · git
    • bfa83a9e03cf8d501c6272999843470afecb32ed and later · before 539ca5dcbc91134bbe2c45677811c31d8b030d2daffected · git
    • bfa83a9e03cf8d501c6272999843470afecb32ed and later · before 41b74e95f297ac360ca7ed6bf200100717cb6c45affected · git
    • bfa83a9e03cf8d501c6272999843470afecb32ed and later · before 992e4ff7116a77968039277b5d6aaa535c2f2184affected · git
    • bfa83a9e03cf8d501c6272999843470afecb32ed and later · before f0950402e8c76e7dcb08563f1b4e8000fbc62455affected · git
    • before 2.6.15not affected · semver
    • 5.4.231 and later · up to and including 5.4.*not affected · semver
    • 5.10.166 and later · up to and including 5.10.*not affected · semver
    • 5.15.91 and later · up to and including 5.15.*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.11-16.1.11-1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-defaultbefore 3.0.101-108.183.13.0.101-108.183.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-ec2before 3.0.101-108.183.13.0.101-108.183.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-sourcebefore 3.0.101-108.183.13.0.101-108.183.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-symsbefore 3.0.101-108.183.13.0.101-108.183.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-tracebefore 3.0.101-108.183.13.0.101-108.183.1
SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREkernel-xenbefore 3.0.101-108.183.13.0.101-108.183.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2023-52998Mar 27, 2025 · net: fec: Use page_pool_put_full_page when freeing rx buffers
    22Monitor
  • ← EarlierCVE-2023-52999Mar 27, 2025 · net: fix UaF in netns ops registration error path
    31Monitor
  • Later →CVE-2023-53002Mar 27, 2025 · drm/i915: Fix a memory leak with reused mmap_offset
    22Monitor

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 Linux3e5082b1c66c7783fbcd79b5b178573230e528ffVendor (CNA)
Linux Linux41b74e95f297ac360ca7ed6bf200100717cb6c45Vendor (CNA)
Linux Linux539ca5dcbc91134bbe2c45677811c31d8b030d2dVendor (CNA)
Linux Linux992e4ff7116a77968039277b5d6aaa535c2f2184Vendor (CNA)
Linux Linuxf0950402e8c76e7dcb08563f1b4e8000fbc62455Vendor (CNA)
debian:linux6.1.11-1 · Debian:12Package registry (OSV)
suse:kernel-default3.0.101-108.183.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-ec23.0.101-108.183.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-source3.0.101-108.183.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-syms3.0.101-108.183.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-trace3.0.101-108.183.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage registry (OSV)
suse:kernel-xen3.0.101-108.183.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME COREPackage 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.

  • CVE-2021-47548307 days apartethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port()
    39Monitor
  • CVE-2026-64018479 days apartnet: mana: validate rx_req_idx to prevent out-of-bounds array access
    37Monitor
  • CVE-2026-23246356 days apartwifi: mac80211: bounds-check link_id in ieee80211_ml_reconfiguration
    35Monitor
  • CVE-2026-43110405 days apartwifi: brcmfmac: validate bsscfg indices in IF events
    35Monitor
  • CVE-2026-43172405 days apartwifi: iwlwifi: fix 22000 series SMEM parsing
    35Monitor
  • CVE-2023-530190 days apartnet: mdio: validate parameter addr in mdiobus_get_phy()
    31Monitor

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

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-129 · Improper Validation of Array Index

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

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

References

Show all references (4 more)

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

All records