NVD / CVE Program· CNA Linux

CVE-2024-42073: mlxsw: spectrum_buffers: Fix memory corruptions on Spectrum-4 systems

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.22% (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 942901e0fc74ad4b7992ef7ca9336e68d5fd6d36, bf8781ede7bd9a37c0fcabca78976e61300b5a1a, bfa86a96912faa0b6142a918db88cc0c738a769e; azl3 kernel 6.6.35.1-5 on Azure Linux 3.0 6.6.43.1-7; azl3 kernel 6.6.43.1-7 on Azure Linux 3.0 6.6.43.1-7.

Low priority for now. Upgrade to Linux Linux 942901e0fc74ad4b7992ef7ca9336e68d5fd6d36, bf8781ede7bd9a37c0fcabca78976e61300b5a1a, bfa86a96912faa0b6142a918db88cc0c738a769e; azl3 kernel 6.6.35.1-5 on Azure Linux 3.0 6.6.43.1-7; azl3 kernel 6.6.43.1-7 on Azure Linux 3.0 6.6.43.1-7 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: mlxsw: spectrum_buffers: Fix memory corruptions on Spectrum-4 systems The following two shared buffer operations make use of the Shared Buffer Status Register (SBSR): # devlink sb occupancy snapshot pci/0000:01:00.0 # devlink sb occupancy clearmax pci/0000:01:00.0 The register has two masks of 256 bits to denote on which ingress / egress ports the register should operate on. Spectrum-4 has more than 256 ports, so the register was extended by cited commit with a new 'port_page' field. However, when filling the register's payload, the driver specifies the ports as absolute numbers and not relative to the first port of the port page, resulting in memory corruptions [1]. Fix by specifying the ports relative to the first port of the port page. [1] BUG: KASAN: slab-use-after-free in mlxsw_sp_sb_occ_snapshot+0xb6d/0xbc0 Read of size 1 at addr ffff8881068cb00f by task devlink/1566 [...] Call Trace: <TASK> dump_stack_lvl+0xc6/0x120 print_report+0xce/0x670 kasan_report+0xd7/0x110 mlxsw_sp_sb_occ_snapshot+0xb6d/0xbc0 mlxsw_devlink_sb_occ_snapshot+0x75/0xb0 devlink_nl_sb_occ_snapshot_doit+0x1f9/0x2a0 genl_family_rcv_msg_doit+0x20c/0x300 genl_rcv_msg+0x567/0x800 netlink_rcv_skb+0x170/0x450 genl_rcv+0x2d/0x40 netlink_unicast+0x547/0x830 netlink_sendmsg+0x8d4/0xdb0 __sys_sendto+0x49b/0x510 __x64_sys_sendto+0xe5/0x1c0 do_syscall_64+0xc1/0x1d0 entry_SYSCALL_64_after_hwframe+0x77/0x7f [...] Allocated by task 1: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 __kasan_kmalloc+0x8f/0xa0 copy_verifier_state+0xbc2/0xfb0 do_check_common+0x2c51/0xc7e0 bpf_check+0x5107/0x9960 bpf_prog_load+0xf0e/0x2690 __sys_bpf+0x1a61/0x49d0 __x64_sys_bpf+0x7d/0xc0 do_syscall_64+0xc1/0x1d0 entry_SYSCALL_64_after_hwframe+0x77/0x7f Freed by task 1: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3b/0x60 poison_slab_object+0x109/0x170 __kasan_slab_free+0x14/0x30 kfree+0xca/0x2b0 free_verifier_state+0xce/0x270 do_check_common+0x4828/0xc7e0 bpf_check+0x5107/0x9960 bpf_prog_load+0xf0e/0x2690 __sys_bpf+0x1a61/0x49d0 __x64_sys_bpf+0x7d/0xc0 do_syscall_64+0xc1/0x1d0 entry_SYSCALL_64_after_hwframe+0x77/0x7f

MediumCVSS 5.5 · v3.1—No exploit Fix available

BDU:2025-01035

Published: Jul 29, 2024
Updated: Jun 17, 2026
EPSS: 0.2% · 12th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 22 / 40 · 5.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

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.

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.

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 kernelbefore 5.17
linux linux kernel6.1 and later · before 6.1.97
linux linux kernel6.2 and later · before 6.6.37
linux linux kernel6.7 and later · before 6.9.8

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
- 5.17affected
- f8538aec88b46642553a9ba9efa0952f5958dbed and later · before bfa86a96912faa0b6142a918db88cc0c738a769eaffected · git
- f8538aec88b46642553a9ba9efa0952f5958dbed and later · before 942901e0fc74ad4b7992ef7ca9336e68d5fd6d36affected · git
- f8538aec88b46642553a9ba9efa0952f5958dbed and later · before bf8781ede7bd9a37c0fcabca78976e61300b5a1aaffected · git
- f8538aec88b46642553a9ba9efa0952f5958dbed and later · before c28947de2bed40217cf256c5d0d16880054fcf13affected · git
- before 5.17not affected · semver
- 6.1.97 and later · up to and including 6.1.*not affected · semver
- 6.6.37 and later · up to and including 6.6.*not affected · semver
- 6.9.8 and later · up to and including 6.9.*not affected · semver
- 6.10 and laternot affected · original_commit_for_fix

Package-level exposure

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

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.98-1	6.1.98-1
Debian:13	linux	before 6.9.8-1	6.9.8-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-2024-42071Jul 29, 2024 · ionic: use dev_consume_skb_any outside of napi
22Monitor
← EarlierCVE-2024-42072Jul 29, 2024 · bpf: Fix may_goto with negative offset.
31Monitor
Later →CVE-2024-42074Jul 29, 2024 · ASoC: amd: acp: add a null check for chip_pdev structure
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 / package	Fixed version	Source
Linux Linux	942901e0fc74ad4b7992ef7ca9336e68d5fd6d36	Vendor (CNA)
Linux Linux	bf8781ede7bd9a37c0fcabca78976e61300b5a1a	Vendor (CNA)
Linux Linux	bfa86a96912faa0b6142a918db88cc0c738a769e	Vendor (CNA)
Linux Linux	c28947de2bed40217cf256c5d0d16880054fcf13	Vendor (CNA)
azl3 kernel 6.6.35.1-5 on Azure Linux 3.0	6.6.43.1-7 · CBL-Mariner Releases	Microsoft (MSRC)
azl3 kernel 6.6.43.1-7 on Azure Linux 3.0	6.6.43.1-7 · CBL-Mariner Releases	Microsoft (MSRC)
cbl2 kernel 5.15.162.2-1 on CBL Mariner 2.0	5.15.162.2-1 · CBL-Mariner Releases	Microsoft (MSRC)
cbl2 kernel 5.15.180.1-1 on CBL Mariner 2.0	5.15.162.2-1 · CBL-Mariner Releases	Microsoft (MSRC)
cbl2 kernel 5.15.180.1-1 on CBL-Mariner 2.0	5.15.162.2-1 · CBL-Mariner Releases	Microsoft (MSRC)
debian:linux	6.1.98-1 · Debian:12	Package 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)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

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

Fix✗ → ✓Sep 28, 2026, 10:09 PM UTC

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

References

git.kernel.org/stable/c/942901e0fc74ad4b7992ef7ca9336e68d5fd6d36

Show all references (4 more)

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

All records