CVE-2024-42138: mlxsw: core_linecards: Fix double memory deallocation in case of invalid INI file
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.23% (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 8ce34dccbe8fa7d2ef86f2d8e7db2a9b67cabfc3, 9af7437669b72f804fc4269f487528dbbed142a2, ab557f5cd993a3201b09593633d04b891263d5c0.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 8ce34dccbe8fa7d2ef86f2d8e7db2a9b67cabfc3, 9af7437669b72f804fc4269f487528dbbed142a2, ab557f5cd993a3201b09593633d04b891263d5c0 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: core_linecards: Fix double memory deallocation in case of invalid INI file In case of invalid INI file mlxsw_linecard_types_init() deallocates memory but doesn't reset pointer to NULL and returns 0. In case of any error occurred after mlxsw_linecard_types_init() call, mlxsw_linecards_init() calls mlxsw_linecard_types_fini() which performs memory deallocation again. Add pointer reset to NULL. Found by Linux Verification Center (linuxtesting.org) with SVACE.
- Published
- Jul 30, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- CWE-415
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 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.
Is your version affected? Check itNoroxi 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 |
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.19affected
- b217127e5e4ee0ecfce7c5f84cfe082238123bda and later · before ab557f5cd993a3201b09593633d04b891263d5c0affected · git
- b217127e5e4ee0ecfce7c5f84cfe082238123bda and later · before f8b55a465b0e8a500179808166fe9420f5c091a1affected · git
- b217127e5e4ee0ecfce7c5f84cfe082238123bda and later · before 9af7437669b72f804fc4269f487528dbbed142a2affected · git
- b217127e5e4ee0ecfce7c5f84cfe082238123bda and later · before 8ce34dccbe8fa7d2ef86f2d8e7db2a9b67cabfc3affected · git
- before 5.19not affected · semver
- 6.1.98 and later · up to and including 6.1.*not affected · semver
- 6.6.39 and later · up to and including 6.6.*not affected · semver
- 6.9.9 and later · up to and including 6.9.*not affected · semver
- 6.10 and laternot affected · original_commit_for_fix
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.19 and later · before 6.1.98
- linux linux kernel6.2 and later · before 6.6.39
- linux linux kernel6.7 and later · before 6.9.9
- linux linux kernel6.10
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.9-1 | 6.9.9-1 |
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-2024-42136Jul 30, 2024 · cdrom: rearrange last_media_change check to avoid unintentional overflow31Monitor
- ← EarlierCVE-2024-42137Jul 30, 2024 · Bluetooth: qca: Fix BT enable failure again for QCA6390 after warm reboot22Monitor
- Later →CVE-2024-42140Jul 30, 2024 · riscv: kexec: Avoid deadlock in kexec crash path22Monitor
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 | 8ce34dccbe8fa7d2ef86f2d8e7db2a9b67cabfc3 | Vendor (CNA) |
| Linux Linux | 9af7437669b72f804fc4269f487528dbbed142a2 | Vendor (CNA) |
| Linux Linux | ab557f5cd993a3201b09593633d04b891263d5c0 | Vendor (CNA) |
| Linux Linux | f8b55a465b0e8a500179808166fe9420f5c091a1 | Vendor (CNA) |
| 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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-3581474 days apartswiotlb: Fix double-allocation of slots due to broken alignment handling35Monitor
- CVE-2024-421470 days apartcrypto: hisilicon/debugfs - Fix debugfs uninit process issue31Monitor
- CVE-2024-410461 days apartnet: ethernet: lantiq_etop: fix double free in detach31Monitor
- CVE-2024-410731 days apartnvme: avoid double free special payload31Monitor
- CVE-2024-410871 days apartata: libata-core: Fix double free on error31Monitor
- CVE-2024-4094018 days apartnet/mlx5: Fix tainted pointer delete is case of flow rules creation fail31Monitor
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1106 · Jul 31, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
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-415 · Double FreeCVSS 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.
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 (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.