CVE-2025-38613: Linux kernel · staging: gpib: fix unset padding field copy back to userspace
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 19 Nov 2026, 02:37 UTC
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
AI-suggested
A fix has been implemented in the Linux kernel by zero-initializing the entire gpib_board_info_ioctl structure before copying it back to userspace. Users should update to the fixed kernel version once available. No additional mitigation is indicated.
Description
A vulnerability in the Linux kernel's gpib driver was fixed by ensuring that padding fields in the gpib_board_info_ioctl structure are properly zero-initialized before being copied back to userspace. This prevents uninitialized stack data from being exposed. The issue was addressed by initializing the entire structure to zero.