Back to skill

Security audit

Zynq Linux Hardware Debug

Security checks for vulnerabilities and agentic risk

Overview

This is a legitimate Zynq hardware-debugging guide, but it includes commands that can change or disrupt live hardware without enough safety warnings.

Review before using on real boards. Install only if you understand Zynq hardware debugging, and treat write examples as live hardware mutations: verify every address, register, GPIO, bitstream, and module action against board documentation, prefer read-only checks first, and avoid production or unrecoverable systems.

Vulnerability Patterns
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

Missing User Warnings

Medium
Confidence
88% confidence
Finding
The skill includes state-changing hardware commands such as I2C register writes without any warning, guardrails, or guidance to verify target devices and register maps first. In a hardware-debugging context, these commands can misconfigure peripherals, disrupt buses, or place devices into unsafe states if copied blindly, especially by less experienced users.

Static analysis

No suspicious patterns detected.