LiveActive security incident?Get immediate response
CVE Record

CVE-2026-43173: net: ethernet: xscale: Check for PTP support properly

In the Linux kernel, the following vulnerability has been resolved: net: ethernet: xscale: Check for PTP support properly In ixp4xx_get_ts_info() ixp46x_ptp_find() is called unconditionally despite this feature only existing on ixp46x, leading to the following splat from tcpdump: root@OpenWrt:~# tcpdump -vv -X -i eth0 (...) Unable to handle kernel NULL pointer dereference at virtual address 00000238 when read (...) Call trace: ptp_clock_index from ixp46x_ptp_find+0x1c/0x38 ixp46x_ptp_find from ixp4xx_get_ts_info+0x4c/0x64 ixp4xx_get_ts_info from __ethtool_get_ts_info+0x90/0x108 __ethtool_get_ts_info from __dev_ethtool+0xa00/0x2648 __dev_ethtool from dev_ethtool+0x160/0x234 dev_ethtool from dev_ioctl+0x2cc/0x460 dev_ioctl from sock_ioctl+0x1ec/0x524 sock_ioctl from sys_ioctl+0x51c/0xa94 sys_ioctl from ret_fast_syscall+0x0/0x44 (...) Segmentation fault Check for ixp46x in ixp46x_ptp_find() before trying to set up PTP to avoid this. To avoid altering the returned error code from ixp4xx_hwtstamp_set() which before this patch was -EOPNOTSUPP, we return -EOPNOTSUPP from ixp4xx_hwtstamp_set() if ixp46x_ptp_find() fails no matter the error code. The helper function ixp46x_ptp_find() helper returns -ENODEV.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can cause a crash path when software asks an affected XScale IXP4xx Ethernet driver for timestamping information. It is hardware-specific and appears most relevant to embedded Linux systems using this legacy network driver. The source does not provide CVSS, broad product impact, or evidence of active exploitation.

Executive priority

Treat this as targeted remediation for niche Linux network hardware, not a broad enterprise emergency. Patch affected embedded or appliance kernels through normal maintenance unless those systems are availability-critical or internet-facing.

Technical view

ixp4xx_get_ts_info() called ixp46x_ptp_find() without first confirming IXP46x PTP support. On unsupported hardware, the call could dereference a null pointer through the PTP path during ethtool timestamp-info handling. Stable kernel commits add the missing platform check and preserve -EOPNOTSUPP behavior for hwtstamp setup.

Likely exposure

Exposure is likely limited to Linux systems using the XScale IXP4xx Ethernet driver on affected kernel versions or commits. The source names Linux only; it does not enumerate distributions, appliances, or downstream packages.

Exploitation context

No CISA KEV listing is provided, and the bundle gives no evidence of exploitation in the wild. The report shows a local network-interface inspection path triggering a kernel null pointer dereference, but does not establish remote exploitation.

Researcher notes

Key uncertainty remains around privilege requirements, downstream distribution status, and practical impact beyond the reported crash path. The source gives fix commits and a kernel trace, but no CVSS vector, exploit report, or affected distribution matrix.

Mitigation direction

  • Apply the relevant Linux stable kernel fix for your maintained branch.
  • Check vendor or distribution advisories for backported kernel updates.
  • Prioritize embedded systems using IXP4xx Ethernet hardware.
  • Avoid assuming non-Linux or unrelated Ethernet drivers are affected.
  • Track downstream firmware updates where direct kernel updates are impractical.

Validation and detection

  • Inventory systems using the IXP4xx Ethernet driver or XScale Ethernet hardware.
  • Compare running kernel versions against vendor fixed builds.
  • Review kernel logs for null pointer dereferences in ixp46x_ptp_find or ixp4xx_get_ts_info.
  • Confirm the stable commit or equivalent backport is present.
  • Document any exposed embedded devices awaiting vendor firmware.
Prepared
Confidence
medium
Sources
7

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-43173 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
0ADP providers
6Source links

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
LinuxLinux9055a2f591629b952910503e72ddae1371c44bf1, 9055a2f591629b952910503e72ddae1371c44bf1, 9055a2f591629b952910503e72ddae1371c44bf1, 9055a2f591629b952910503e72ddae1371c44bf1, 9055a2f591629b952910503e72ddae1371c44bf1unaffected
LinuxLinux5.15, 0, 6.6.128, 6.12.75, 6.18.16, 6.19.6, 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.