In the Linux kernel, the following vulnerability has been resolved:
net: xilinx: axienet: Add error handling for RX metadata pointer retrieval
Add proper error checking for dmaengine_desc_get_metadata_ptr() which
can return an error pointer and lead to potential crashes or undefined
behaviour if the pointer retrieval fails.
Properly handle the error by unmapping DMA buffer, freeing the skb and
returning early to prevent further processing with invalid data.
Security readout for executives and security teams
Plain-English summary
A flaw in the Linux Xilinx AXI Ethernet driver can crash a system or cause undefined behavior when receive-metadata retrieval fails. The primary consequence is loss of availability, not data theft or modification. Risk is concentrated in systems using the affected driver and code versions.
Executive priority
Treat as a high-priority availability issue for systems using Xilinx AXI Ethernet, especially remotely reachable or operationally critical devices. Broad emergency action across all Linux systems is not supported by the evidence. Rapidly identify relevant hardware and kernels, then apply the appropriate supported update.
Technical view
The RX path did not check whether dmaengine_desc_get_metadata_ptr() returned an error pointer. Subsequent processing could use invalid metadata, causing a crash or undefined behavior. The kernel fix detects the error, unmaps the DMA buffer, frees the network buffer, and stops processing. The record classifies this as CWE-476 with CVSS 3.1 score 7.5.
Likely exposure
Exposure requires an affected Linux kernel and use of the Xilinx axienet receive path. The bundle lists Linux 6.8, 6.12.46, 6.16.6, and 6.17, but its version boundaries are ambiguous. Confirm exact affected and fixed releases against vendor kernel guidance and the referenced stable commits.
Exploitation context
The supplied CVSS vector treats the flaw as remotely reachable without privileges or user interaction, with availability impact only. However, the sources provide no exploit demonstration or attack prerequisites beyond the affected driver path. The CVE is not listed as KEV, and the bundle supplies no evidence of active exploitation.
Researcher notes
The essential failure is unchecked error-pointer handling during RX metadata retrieval. The corrective behavior is explicit cleanup and early return. The supplied affected-version data contains repeated commit identifiers and unclear release boundaries, so branch-specific exposure should be established from the stable commits or distributor advisories. No confidentiality or integrity impact is identified.
Mitigation direction
Update to a vendor-supported kernel containing the applicable referenced stable fix.
Confirm the selected kernel package includes the fix for the deployed branch.
Prioritize exposed, availability-sensitive systems using the Xilinx axienet driver.
If immediate updating is impossible, consult vendor guidance for supported temporary mitigations.
Validation and detection
Inventory Linux kernel versions on systems using Xilinx AXI Ethernet hardware.
Verify whether the Xilinx axienet driver and affected RX path are active.
Compare deployed kernel source or vendor changelogs with the referenced stable commits.
After updating, confirm the running kernel contains the branch-appropriate fix.
Review crash logs for axienet, DMA metadata, or receive-path failures.
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.
cwe · low confidence lookup
CWE-476: 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.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-476 · source CWE mapping
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.