Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2023-53393: RDMA/mlx5: Fix mlx5_ib_get_hw_stats when used for device

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 38b50aa44495d5eb4218f0b82fc2da76505cec53, 8d89870d63758363b07ace5c2df82d6bf865f78b, 9a97da4674b890b4c28f5f12beba8c33a9cd2f49.

Low priority for now. Upgrade to Linux Linux 38b50aa44495d5eb4218f0b82fc2da76505cec53, 8d89870d63758363b07ace5c2df82d6bf865f78b, 9a97da4674b890b4c28f5f12beba8c33a9cd2f49 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: RDMA/mlx5: Fix mlx5_ib_get_hw_stats when used for device Currently, when mlx5_ib_get_hw_stats() is used for device (port_num = 0), there is a special handling in order to use the correct counters, but, port_num is being passed down the stack without any change. Also, some functions assume that port_num >=1. As a result, the following oops can occur. BUG: unable to handle page fault for address: ffff89510294f1a8 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 0 P4D 0 Oops: 0002 [#1] SMP CPU: 8 PID: 1382 Comm: devlink Tainted: G W 6.1.0-rc4_for_upstream_base_2022_11_10_16_12 #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:_raw_spin_lock+0xc/0x20 Call Trace: <TASK> mlx5_ib_get_native_port_mdev+0x73/0xe0 [mlx5_ib] do_get_hw_stats.constprop.0+0x109/0x160 [mlx5_ib] mlx5_ib_get_hw_stats+0xad/0x180 [mlx5_ib] ib_setup_device_attrs+0xf0/0x290 [ib_core] ib_register_device+0x3bb/0x510 [ib_core] ? atomic_notifier_chain_register+0x67/0x80 __mlx5_ib_add+0x2b/0x80 [mlx5_ib] mlx5r_probe+0xb8/0x150 [mlx5_ib] ? auxiliary_match_id+0x6a/0x90 auxiliary_bus_probe+0x3c/0x70 ? driver_sysfs_add+0x6b/0x90 really_probe+0xcd/0x380 __driver_probe_device+0x80/0x170 driver_probe_device+0x1e/0x90 __device_attach_driver+0x7d/0x100 ? driver_allows_async_probing+0x60/0x60 ? driver_allows_async_probing+0x60/0x60 bus_for_each_drv+0x7b/0xc0 __device_attach+0xbc/0x200 bus_probe_device+0x87/0xa0 device_add+0x404/0x940 ? dev_set_name+0x53/0x70 __auxiliary_device_add+0x43/0x60 add_adev+0x99/0xe0 [mlx5_core] mlx5_attach_device+0xc8/0x120 [mlx5_core] mlx5_load_one_devl_locked+0xb2/0xe0 [mlx5_core] devlink_reload+0x133/0x250 devlink_nl_cmd_reload+0x480/0x570 ? devlink_nl_pre_doit+0x44/0x2b0 genl_family_rcv_msg_doit.isra.0+0xc2/0x110 genl_rcv_msg+0x180/0x2b0 ? devlink_nl_cmd_region_read_dumpit+0x540/0x540 ? devlink_reload+0x250/0x250 ? devlink_put+0x50/0x50 ? genl_family_rcv_msg_doit.isra.0+0x110/0x110 netlink_rcv_skb+0x54/0x100 genl_rcv+0x24/0x40 netlink_unicast+0x1f6/0x2c0 netlink_sendmsg+0x237/0x490 sock_sendmsg+0x33/0x40 __sys_sendto+0x103/0x160 ? handle_mm_fault+0x10e/0x290 ? do_user_addr_fault+0x1c0/0x5f0 __x64_sys_sendto+0x25/0x30 do_syscall_64+0x3d/0x90 entry_SYSCALL_64_after_hwframe+0x46/0xb0 Fix it by setting port_num to 1 in order to get device status and remove unused variable.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Sep 18, 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%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

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-53393

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 kernel4.16 and later · before 5.15.87
  • linux linux kernel5.16 and later · before 6.0.19
  • linux linux kernel6.1 and later · before 6.1.5
  • 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

    • 4.16affected
    • aac4492ef23a176b6f1a41aadb99177eceb1fc06 and later · before 8d89870d63758363b07ace5c2df82d6bf865f78baffected · git
    • aac4492ef23a176b6f1a41aadb99177eceb1fc06 and later · before 9a97da4674b890b4c28f5f12beba8c33a9cd2f49affected · git
    • aac4492ef23a176b6f1a41aadb99177eceb1fc06 and later · before e597b003c736217b0c99ccf1b240c25009105238affected · git
    • aac4492ef23a176b6f1a41aadb99177eceb1fc06 and later · before 38b50aa44495d5eb4218f0b82fc2da76505cec53affected · git
    • before 4.16not affected · semver
    • 5.15.87 and later · up to and including 5.15.*not affected · semver
    • 6.0.19 and later · up to and including 6.0.*not affected · semver
    • 6.1.5 and later · up to and including 6.1.*not affected · semver
    • 6.2 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:12linuxbefore 6.1.7-16.1.7-1
Red Hat:rhel_aus:8.2::baseosbpftoolbefore 0:4.18.0-193.178.1.el8_20:4.18.0-193.178.1.el8_2
Red Hat:rhel_aus:8.2::baseosbpftool-debuginfobefore 0:4.18.0-193.178.1.el8_20:4.18.0-193.178.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernelbefore 0:4.18.0-193.178.1.el8_20:4.18.0-193.178.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-abi-whitelistsbefore 0:4.18.0-193.178.1.el8_20:4.18.0-193.178.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-corebefore 0:4.18.0-193.178.1.el8_20:4.18.0-193.178.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-debugbefore 0:4.18.0-193.178.1.el8_20:4.18.0-193.178.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-debug-corebefore 0:4.18.0-193.178.1.el8_20:4.18.0-193.178.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-debug-debuginfobefore 0:4.18.0-193.178.1.el8_20:4.18.0-193.178.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-debug-develbefore 0:4.18.0-193.178.1.el8_20:4.18.0-193.178.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-debug-modulesbefore 0:4.18.0-193.178.1.el8_20:4.18.0-193.178.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-debug-modules-extrabefore 0:4.18.0-193.178.1.el8_20:4.18.0-193.178.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-debuginfobefore 0:4.18.0-193.178.1.el8_20:4.18.0-193.178.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-debuginfo-common-x86_64before 0:4.18.0-193.178.1.el8_20:4.18.0-193.178.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-develbefore 0:4.18.0-193.178.1.el8_20:4.18.0-193.178.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-docbefore 0:4.18.0-193.178.1.el8_20:4.18.0-193.178.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-modulesbefore 0:4.18.0-193.178.1.el8_20:4.18.0-193.178.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-modules-extrabefore 0:4.18.0-193.178.1.el8_20:4.18.0-193.178.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-toolsbefore 0:4.18.0-193.178.1.el8_20:4.18.0-193.178.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-tools-debuginfobefore 0:4.18.0-193.178.1.el8_20:4.18.0-193.178.1.el8_2
Red Hat:rhel_aus:8.2::baseoskernel-tools-libsbefore 0:4.18.0-193.178.1.el8_20:4.18.0-193.178.1.el8_2
Red Hat:rhel_aus:8.2::baseosperfbefore 0:4.18.0-193.178.1.el8_20:4.18.0-193.178.1.el8_2
Red Hat:rhel_aus:8.2::baseosperf-debuginfobefore 0:4.18.0-193.178.1.el8_20:4.18.0-193.178.1.el8_2
Red Hat:rhel_aus:8.2::baseospython3-perfbefore 0:4.18.0-193.178.1.el8_20:4.18.0-193.178.1.el8_2

+96

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-53391Sep 18, 2025 · shmem: use ramfs_kill_sb() for kill_sb method of ramfs-based tmpfs
    22Monitor
  • ← EarlierCVE-2023-53392Sep 18, 2025 · HID: intel-ish-hid: Fix kernel panic during warm reset
    28Monitor
  • Later →CVE-2023-53394Sep 18, 2025 · net/mlx5e: xsk: Fix crash on regular rq reactivation
    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 Linux38b50aa44495d5eb4218f0b82fc2da76505cec53Vendor (CNA)
Linux Linux8d89870d63758363b07ace5c2df82d6bf865f78bVendor (CNA)
Linux Linux9a97da4674b890b4c28f5f12beba8c33a9cd2f49Vendor (CNA)
Linux Linuxe597b003c736217b0c99ccf1b240c25009105238Vendor (CNA)
debian:linux6.1.7-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-372.170.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-372.170.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-372.170.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-372.170.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-372.170.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-372.170.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-372.170.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-372.170.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-372.170.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug-modules0:4.18.0-372.170.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debug-modules-extra0:4.18.0-372.170.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-debuginfo0:4.18.0-372.170.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage 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.

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

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

All records