Security readout for executives and security teams
Plain-English summary
A Linux kernel networking flaw can mishandle socket ownership when GRO fraglist packets are later segmented. The supplied record reports a possible kernel BUG and rates potential confidentiality, integrity, and availability impact as high. Exploitation requires local access with low privileges according to the CVSS vector; no active exploitation evidence is provided.
Executive priority
Treat this as a high-priority kernel maintenance issue, especially on shared Linux hosts or systems running untrusted workloads. Schedule vendor-approved updates promptly, but avoid declaring an emergency based solely on the score: the supplied evidence indicates local access is required and does not establish active exploitation.
Technical view
The GRO receive paths remove an skb destructor without also clearing its socket reference. Reused skbs therefore cannot be orphaned during later segmentation, potentially triggering a kernel BUG in skb_orphan. The upstream resolution removes the socket reference in both skb_gro_receive_list and the similar skb_gro_receive path.
Likely exposure
Exposure applies to Linux systems running affected kernel builds where GRO fraglist packet processing is reachable. The bundle lists affected 5.15, 5.15.154, 6.1.85, 6.6.26, 6.8.5, and 6.9 entries, but its version structure is ambiguous. Confirm status against the distribution or appliance vendor's exact build.
Exploitation context
The CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction, with high potential impact. The bundle marks this CVE as absent from KEV and provides no evidence of exploitation in the wild, public exploit availability, or reliable privilege escalation.
Researcher notes
The observable failure is a kernel BUG associated with stale skb socket ownership after GRO fraglist segmentation. The record supplies multiple stable-tree fixes but no CWE, exploit analysis, or demonstrated attack outcome. Package backports may make upstream version comparisons unreliable; validate using vendor build metadata and commit inclusion.
Mitigation direction
- Upgrade to a vendor-supported kernel release containing the GRO ownership-transfer fix.
- Check distribution or appliance advisories for the fixed package corresponding to the deployed kernel.
- Prioritize multi-user systems where untrusted users or workloads have local access.
- Use vendor-recommended mitigations if an immediate kernel update is unavailable.
Validation and detection
- Record each system's exact kernel and vendor package version.
- Confirm the vendor package changelog references CVE-2024-35890 or a listed stable fix commit.
- Verify the updated kernel is running after installation and reboot.
- Review kernel logs for matching skb_orphan BUG traces, while recognizing absence does not prove safety.
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.
CVE-2024-35890 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
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/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
1 official scoreWe 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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
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/d225b0ac96dc40d7e8ae2bc227eb2c56e130975fCVE reference, Linux
- https://git.kernel.org/stable/c/2eeab8c47c3c0276e0746bc382f405c9a236a5adCVE reference, Linux
- https://git.kernel.org/stable/c/fc126c1d51e9552eacd2d717b9ffe9262a8a4cd6CVE reference, Linux
- https://git.kernel.org/stable/c/5b3b67f731296027cceb3efad881ae281213f86fCVE reference, Linux
- https://git.kernel.org/stable/c/ed4cccef64c1d0d5b91e69f7a8a6697c3a865486CVE reference, Linux
- https://security.netapp.com/advisory/ntap-20250509-0008/CVE 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.