Security readout for executives and security teams
Plain-English summary
A memory-management error in the Linux Vertexcom MSE102x network driver can free transmitted packet memory twice, causing a kernel crash. Business exposure is concentrated in systems using this specific driver and hardware; ordinary Linux installations without it are unlikely to reach the vulnerable path.
Executive priority
Treat confirmed MSE102x deployments as urgent because a kernel crash can interrupt networked operations. Rapidly scope first: systems not using this specialized driver have materially lower practical exposure. Patch confirmed deployments through supported kernel channels and validate critical appliances after rollout.
Technical view
When transmit-buffer space must be expanded, the driver can free the original socket buffer instead of a temporary buffer. The transmit worker later frees the original pointer again, producing a CWE-415 double free and kernel oops. Stable-kernel commits change the cleanup target. The supplied record rates this CVSS 9.8, although its demonstrated consequence is a crash.
Likely exposure
Potentially exposed systems run an affected Linux kernel with the Vertexcom MSE102x driver active and exercise its transmit path. The supplied version data is irregular, so determine exposure from distribution or appliance vendor advisories and fix backports rather than version numbers alone.
Exploitation context
The bundle does not identify CISA KEV listing, active exploitation, or a public exploit. It documents a reproducible kernel crash. The supplied CVSS vector asserts network reachability and full confidentiality, integrity, and availability impact, but the technical description only substantiates crashing; broader impact remains unproven here.
Researcher notes
The fault is in TX socket-buffer ownership during expansion and later worker cleanup. Four stable-kernel fixes are referenced, suggesting branch-specific backports. Do not infer remote code execution or data compromise from the CVSS vector alone; the supplied crash trace establishes availability impact, while exploitability and other impacts are not demonstrated.
Mitigation direction
- Install a vendor-supported kernel containing the applicable stable fix commit or backport.
- Check appliance and Linux distribution advisories for package-specific fixed versions.
- If patching is delayed, avoid or disable the MSE102x driver where operationally safe and vendor-supported.
- Prioritize affected network appliances whose unexpected reboot or outage would disrupt critical operations.
Validation and detection
- Inventory kernels, loaded modules, and hardware for active Vertexcom MSE102x use.
- Compare the running kernel package against vendor advisories and documented backports.
- Confirm the applicable stable fix commit exists in the deployed kernel source or package changelog.
- Review kernel logs for mse102x_tx_work, skb_release_data, double-free, oops, or unexplained crashes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-415: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-50276 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/2cf0e77f5a0aa1ff336aa71743eda55c73902187CVE reference, Linux
- https://git.kernel.org/stable/c/1325e838089da25217f4b403318a270fcdf88f34CVE reference, Linux
- https://git.kernel.org/stable/c/91c9daa21f3ff8668f9e1d6c860024ce7ad64137CVE reference, Linux
- https://git.kernel.org/stable/c/1f26339b2ed63d1e8e18a18674fb73a392f3660eCVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2025/01/msg00001.htmlCVE reference, CVE
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Double Free
Double Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.