LiveActive security incident?Get immediate response
CVE Record

CVE-2026-43039: net: ti: icssg-prueth: fix missing data copy and wrong recycle in ZC RX dispatch

In the Linux kernel, the following vulnerability has been resolved: net: ti: icssg-prueth: fix missing data copy and wrong recycle in ZC RX dispatch emac_dispatch_skb_zc() allocates a new skb via napi_alloc_skb() but never copies the packet data from the XDP buffer into it. The skb is passed up the stack containing uninitialized heap memory instead of the actual received packet, leaking kernel heap contents to userspace. Copy the received packet data from the XDP buffer into the skb using skb_copy_to_linear_data(). Additionally, remove the skb_mark_for_recycle() call since the skb is backed by the NAPI page frag allocator, not page_pool. Marking a non-page_pool skb for recycle causes the free path to return pages to a page_pool that does not own them, corrupting page_pool state. The non-ZC path (emac_rx_packet) does not have these issues because it uses napi_build_skb() to wrap the existing page_pool page directly, requiring no copy, and correctly marks for recycle since the page comes from page_pool_dev_alloc_pages().

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A flaw in a Linux network driver can expose kernel memory to userspace and corrupt internal memory-management state while receiving packets. Consequences may include sensitive-data disclosure, system instability, or broader integrity impact. Exposure is limited to systems using the affected TI ICSSG PRU Ethernet zero-copy receive path.

Executive priority

Treat confirmed exposure as urgent because the supplied score is 9.8 and impacts confidentiality, integrity, and availability. Prioritize embedded, industrial, or appliance deployments where the affected driver and receive path are present. Avoid broad emergency action on Linux systems lacking this driver.

Technical view

The zero-copy receive dispatcher allocates an skb without copying packet data, so uninitialized kernel heap contents enter the networking stack. It also incorrectly marks NAPI-fragment memory for page-pool recycling, potentially corrupting page-pool state. The supplied fixes copy the received data and remove the invalid recycling operation.

Likely exposure

The supplied record identifies Linux 6.19 through 6.19.12 as affected, with 7.0 shown as a boundary. Practical exposure requires the TI ICSSG PRU Ethernet driver and the vulnerable zero-copy receive path. Systems without that driver or path are unlikely to be exposed.

Exploitation context

The CVSS vector describes network reachability without privileges or user interaction. However, the bundle provides no public exploitation evidence, and the CVE is not listed as KEV. It does not establish reliable remote code execution; documented outcomes are kernel heap disclosure to userspace and page-pool corruption.

Researcher notes

The vulnerable function is emac_dispatch_skb_zc(). The non-zero-copy emac_rx_packet path is explicitly described as unaffected because it wraps page-pool memory correctly. No CWE mapping, exploit evidence, or complete distribution-specific package guidance is provided. The unusual version boundaries should be reconciled against vendor advisories and fix-commit ancestry.

Mitigation direction

  • Install a vendor-supported kernel update containing the applicable referenced stable fix.
  • Prioritize systems using the TI ICSSG PRU Ethernet zero-copy receive path.
  • If updates are unavailable, request vendor guidance for a supported workaround.
  • Restrict untrusted traffic to exposed interfaces where operationally feasible.

Validation and detection

  • Inventory kernel versions on systems using the TI ICSSG PRU Ethernet driver.
  • Determine whether the zero-copy receive dispatch path is enabled or reachable.
  • Confirm the installed kernel includes the applicable referenced fix commit.
  • After updating, regression-test receive traffic, stability, and packet-data integrity.
Prepared
Confidence
high
Sources
4

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-2026-43039 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
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

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.

1CVSS vectors
3Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-43039Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux7a64bb388df3cf091afdd047c701039a13acd3b4, 7a64bb388df3cf091afdd047c701039a13acd3b4unaffected
LinuxLinux6.19, 0, 6.19.12, 7.0affected
Weakness

CWE details

No CWE listed

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