CVE-2026-53230: net/mlx5: Fix slab-out-of-bounds in mlx5_query_nic_vport_mac_list
Noroxi assessment
Priority: Monitor (action score 34/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.12% (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 0f807764bb122fd63aa45f4229cb1ef2679fbd40, 2398e497389ed4be43f7cfbab499b49cec7dae1a, 41781f2789309462520a93822e946521ed78f97f; azl3 kernel 6.6.141.1-1 on Azure Linux 3.0 6.6.143.1-1.
Low priority for now. Upgrade to Linux Linux 0f807764bb122fd63aa45f4229cb1ef2679fbd40, 2398e497389ed4be43f7cfbab499b49cec7dae1a, 41781f2789309462520a93822e946521ed78f97f; azl3 kernel 6.6.141.1-1 on Azure Linux 3.0 6.6.143.1-1 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: net/mlx5: Fix slab-out-of-bounds in mlx5_query_nic_vport_mac_list mlx5_query_nic_vport_mac_list() sizes its firmware command buffer using the PF's log_max_current_uc/mc_list capabilities. When querying a VF vport with a larger configured max (via devlink), the firmware response can overflow this buffer: BUG: KASAN: slab-out-of-bounds in mlx5_query_nic_vport_mac_list+0x453/0x4c0 [mlx5_core] Read of size 4 at addr ff1100013ffc8a12 by task kworker/u96:2/385 CPU: 12 UID: 0 PID: 385 Comm: kworker/u96:2 Not tainted 7.0.0-rc6+ #1 PREEMPT Hardware name: QEMU Standard PC (Q35 + ICH9, 2009) Workqueue: mlx5_esw_wq esw_vport_change_handler [mlx5_core] Call Trace: <TASK> dump_stack_lvl+0x69/0xa0 print_report+0x176/0x4e4 kasan_report+0xc8/0x100 mlx5_query_nic_vport_mac_list+0x453/0x4c0 [mlx5_core] esw_update_vport_addr_list+0x2e3/0xda0 [mlx5_core] esw_vport_change_handle_locked+0xa1f/0x1060 [mlx5_core] esw_vport_change_handler+0x6a/0x90 [mlx5_core] process_one_work+0x87f/0x15e0 worker_thread+0x62b/0x1020 kthread+0x375/0x490 ret_from_fork+0x4dc/0x810 ret_from_fork_asm+0x11/0x20 </TASK> Fix by querying the vport's own HCA caps to size the buffer correctly. Refactor the function to allocate and return the MAC list internally, removing the caller's dependency on knowing the correct max.
- Published
- Jun 25, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-125
Report tools
Action score
34
Monitor
Low priority for now.
- CVSS
- 34 / 40 · 8.7 / 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.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.7
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_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.5 and later · before 6.6.143
- linux linux kernel6.7 and later · before 6.12.94
- linux linux kernel6.13 and later · before 6.18.36
- linux linux kernel6.19 and later · before 7.0.13
- linux linux kernel7.1
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.5affected
- e16aea2744abea612c27ee0eef606c6a6a8204de and later · before 87149f3e53f3839454b837f87a2ec7c926775a6aaffected · git
- e16aea2744abea612c27ee0eef606c6a6a8204de and later · before 41781f2789309462520a93822e946521ed78f97faffected · git
- e16aea2744abea612c27ee0eef606c6a6a8204de and later · before 537d87784e81c3d7037525b99416455cee088cdcaffected · git
- e16aea2744abea612c27ee0eef606c6a6a8204de and later · before 0f807764bb122fd63aa45f4229cb1ef2679fbd40affected · git
- e16aea2744abea612c27ee0eef606c6a6a8204de and later · before 2398e497389ed4be43f7cfbab499b49cec7dae1aaffected · git
- e16aea2744abea612c27ee0eef606c6a6a8204de and later · before 894e036a24a26a6dd7b17d8d3fb5c53ab48a6074affected · git
- before 4.5not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.143 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | bpftool | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-core | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-headers | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-modules | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-modules-extra | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-rt | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-core | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-debug | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-core | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-devel | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-devel | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-modules | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
+65
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-53228Jun 25, 2026 · ipv6: sit: reload inner IPv6 header after GSO offloads39Monitor
- ← EarlierCVE-2026-53229Jun 25, 2026 · net/mlx5e: xsk: Fix DMA and xdp_frame leak on XDP_TX xmit failure30Monitor
- Later →CVE-2026-53232Jun 25, 2026 · net: phy: clean the sfp upstream if phy probing fails35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0f807764bb122fd63aa45f4229cb1ef2679fbd40 | Vendor (CNA) |
| Linux Linux | 2398e497389ed4be43f7cfbab499b49cec7dae1a | Vendor (CNA) |
| Linux Linux | 41781f2789309462520a93822e946521ed78f97f | Vendor (CNA) |
| Linux Linux | 537d87784e81c3d7037525b99416455cee088cdc | Vendor (CNA) |
| Linux Linux | 87149f3e53f3839454b837f87a2ec7c926775a6a | Vendor (CNA) |
| Linux Linux | 894e036a24a26a6dd7b17d8d3fb5c53ab48a6074 | Vendor (CNA) |
| azl3 kernel 6.6.141.1-1 on Azure Linux 3.0 | 6.6.143.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:bpftool | 4.18.0-553.171.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.171.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-core | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-core | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-devel | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-modules | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-modules-extra | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-devel | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-modules | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-modules-extra | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.12.94-1 · Debian:13 | Package registry (OSV) |
| red hat:kernel-rt | 0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-core | 0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug | 0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-core | 0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-debuginfo | 0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-devel | 0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-kvm | 0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-modules | 0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-modules-extra | 0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debuginfo | 0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
+4
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 researchersFinders, 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
- high · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- Low
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/2398e497389ed4be43f7cfbab499b49cec7dae1a
- git.kernel.org/stable/c/41781f2789309462520a93822e946521ed78f97f
- git.kernel.org/stable/c/537d87784e81c3d7037525b99416455cee088cdc
- git.kernel.org/stable/c/87149f3e53f3839454b837f87a2ec7c926775a6a
- git.kernel.org/stable/c/894e036a24a26a6dd7b17d8d3fb5c53ab48a6074
Vendor advisories and official records. Exploit/PoC links are deliberately left out.