Skip to content
Noroxi
CVE-2023-53496· NVD / CVE Program· CNA Linux

x86/platform/uv: Use alternate source for socket to node data

Noroxi assessment

Priority: Monitor (action score 22/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.14% (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 0d01a0c3046d1545391ef7bb1f114743d00e3793, 5290e88ba2c742ca77c5f5b690e5af549cfd8591.

Low priority for now. Upgrade to Linux Linux 0d01a0c3046d1545391ef7bb1f114743d00e3793, 5290e88ba2c742ca77c5f5b690e5af549cfd8591 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: x86/platform/uv: Use alternate source for socket to node data The UV code attempts to build a set of tables to allow it to do bidirectional socket<=>node lookups. But when nr_cpus is set to a smaller number than actually present, the cpu_to_node() mapping information for unused CPUs is not available to build_socket_tables(). This results in skipping some nodes or sockets when creating the tables and leaving some -1's for later code to trip. over, causing oopses. The problem is that the socket<=>node lookups are created by doing a loop over all CPUs, then looking up the CPU's APICID and socket. But if a CPU is not present, there is no way to start this lookup. Instead of looping over all CPUs, take CPUs out of the equation entirely. Loop over all APICIDs which are mapped to a valid NUMA node. Then just extract the socket-id from the APICID. This avoid tripping over disabled CPUs.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Oct 1, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 3th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
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-53496

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 kernel6.5 and later · before 6.5.5
  • linux linux kernel6.6

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

    • 6.5affected
    • 8a50c58519271dd24ba760bb282875f6ad66ee71 and later · before 0d01a0c3046d1545391ef7bb1f114743d00e3793affected · git
    • 8a50c58519271dd24ba760bb282875f6ad66ee71 and later · before 5290e88ba2c742ca77c5f5b690e5af549cfd8591affected · git
    • before 6.5not affected · semver
    • 6.5.5 and later · up to and including 6.5.*not affected · semver
    • 6.6 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:13linuxbefore 6.5.6-16.5.6-1
Red Hat:rhel_eus:9.2::appstreambpftool-debuginfobefore 0:7.0.0-284.71.1.el9_20:7.0.0-284.71.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-284.71.1.el9_20:5.14.0-284.71.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-debug-develbefore 0:5.14.0-284.71.1.el9_20:5.14.0-284.71.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-284.71.1.el9_20:5.14.0-284.71.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-debuginfobefore 0:5.14.0-284.71.1.el9_20:5.14.0-284.71.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-develbefore 0:5.14.0-284.71.1.el9_20:5.14.0-284.71.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-284.71.1.el9_20:5.14.0-284.71.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debug-debuginfobefore 0:5.14.0-284.71.1.el9_20:5.14.0-284.71.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debug-develbefore 0:5.14.0-284.71.1.el9_20:5.14.0-284.71.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-284.71.1.el9_20:5.14.0-284.71.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfobefore 0:5.14.0-284.71.1.el9_20:5.14.0-284.71.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-284.71.1.el9_20:5.14.0-284.71.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-284.71.1.el9_20:5.14.0-284.71.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-284.71.1.el9_20:5.14.0-284.71.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-284.71.1.el9_20:5.14.0-284.71.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-develbefore 0:5.14.0-284.71.1.el9_20:5.14.0-284.71.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-devel-matchedbefore 0:5.14.0-284.71.1.el9_20:5.14.0-284.71.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-docbefore 0:5.14.0-284.71.1.el9_20:5.14.0-284.71.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-tools-debuginfobefore 0:5.14.0-284.71.1.el9_20:5.14.0-284.71.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-284.71.1.el9_20:5.14.0-284.71.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-zfcpdump-develbefore 0:5.14.0-284.71.1.el9_20:5.14.0-284.71.1.el9_2
Red Hat:rhel_eus:9.2::appstreamkernel-zfcpdump-devel-matchedbefore 0:5.14.0-284.71.1.el9_20:5.14.0-284.71.1.el9_2
Red Hat:rhel_eus:9.2::appstreamperfbefore 0:5.14.0-284.71.1.el9_20:5.14.0-284.71.1.el9_2

+36

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • 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
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now

Published before and after this one in the same product

  • ← EarlierCVE-2023-53494Oct 1, 2025 · crypto: xts - Handle EBUSY correctly
    31Monitor
  • ← EarlierCVE-2023-53495Oct 1, 2025 · net: ethernet: mvpp2_main: fix possible OOB write in mvpp2_ethtool_get_rxnfc()
    31Monitor
  • Later →CVE-2023-53497Oct 1, 2025 · media: vsp1: Replace vb2_is_streaming() with vb2_start_streaming_called()
    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 Linux0d01a0c3046d1545391ef7bb1f114743d00e3793Vendor (CNA)
Linux Linux5290e88ba2c742ca77c5f5b690e5af549cfd8591Vendor (CNA)
debian:linux6.5.6-1 · Debian:13Package registry (OSV)
red hat:bpftool-debuginfo0:7.0.0-284.71.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-284.71.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-284.71.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-284.71.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-284.71.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-284.71.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-284.71.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-284.71.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-284.71.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-284.71.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-284.71.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-284.71.1.el9_2 · Red Hat:rhel_eus:9.2::appstreamPackage 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.

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

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
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.

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 (1 more)

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

All records