LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35837: net: mvpp2: clear BM pool before initialization

In the Linux kernel, the following vulnerability has been resolved: net: mvpp2: clear BM pool before initialization Register value persist after booting the kernel using kexec which results in kernel panic. Thus clear the BM pool registers before initialisation to fix the issue.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can cause a kernel panic when a system is booted using kexec because mvpp2 buffer-manager registers may retain old values. The business impact is availability loss on affected systems, not confirmed data theft or remote compromise. It appears most relevant to Linux systems using the mvpp2 network driver and kexec-based reboot workflows.

Executive priority

Treat as a targeted availability-risk patch, not an emergency internet-wide compromise. Prioritize production systems using affected Linux kernels, mvpp2 networking, and kexec. Patch through normal kernel maintenance unless those systems have experienced crashes or support critical services.

Technical view

CVE-2024-35837 is a Linux kernel mvpp2 driver flaw fixed by clearing BM pool registers before initialization. The CVE description states register values can persist after kexec and trigger kernel panic. Upstream stable commits are referenced for multiple kernel branches. No CVSS, CWE, or KEV listing is provided in the source bundle.

Likely exposure

Exposure is likely limited to Linux systems running affected kernel versions with the mvpp2 network driver, especially where kexec is used. The source data lists Linux as affected but does not provide CPEs. Organizations should confirm exposure through kernel version, driver usage, hardware context, and vendor advisories.

Exploitation context

The provided sources do not indicate active exploitation, public exploit use, or remote attack paths. The documented failure mode is kernel panic after kexec due to retained register state. This is primarily an availability and reliability concern for affected deployments.

Researcher notes

Evidence supports a kexec-triggered kernel panic in Linux mvpp2 initialization. The source bundle names upstream stable commits but lacks CVSS and precise product CPEs. Do not assume broad exploitability. Validate against actual driver usage and downstream vendor backports.

Mitigation direction

  • Update to a vendor kernel containing the upstream stable fixes for CVE-2024-35837.
  • Review Linux distribution advisories, including Debian LTS guidance where applicable.
  • Avoid or limit kexec-based reboot workflows on potentially affected systems until patched.
  • Prioritize systems where mvpp2 is used in production network paths.

Validation and detection

  • Inventory Linux hosts and identify kernels using the mvpp2 driver.
  • Check whether deployed kernels include the referenced upstream stable commits.
  • Review crash logs for kernel panics following kexec boot events.
  • Confirm remediation status against your Linux vendor’s CVE-2024-35837 advisory.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-35837 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux3f518509dedc99f0b755d2ce68d24f610e3a005a, 3f518509dedc99f0b755d2ce68d24f610e3a005a, 3f518509dedc99f0b755d2ce68d24f610e3a005a, 3f518509dedc99f0b755d2ce68d24f610e3a005a, 3f518509dedc99f0b755d2ce68d24f610e3a005a, 3f518509dedc99f0b755d2ce68d24f610e3a005aunaffected
LinuxLinux3.17, 0, 5.10.210, 5.15.149, 6.1.76, 6.6.15, 6.7.3, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.