staging: gpib: fix unset padding field copy back to userspace
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.16.1
- CVEs
- CVE-2025-38613
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 18:19 UTC · Revision 1
Source evidence
staging: gpib: fix unset padding field copy back to userspace
core-osv · Original sourcePublished 19 Aug 2025, 17:03 UTC
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.
osv:CVE-2025-38613
Kernel
Fixed versions: 6.16.1
Complete source record
{
"id": "278a6f846b4ada2b7866bd8f3ac0cc92135a6ce43d36ae1746ae0c7e577c51f4",
"url": "https://osv.dev/vulnerability/CVE-2025-38613",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "staging: gpib: fix unset padding field copy back to userspace",
"summary": "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.",
"evidence": "osv:CVE-2025-38613",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.16.1",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2025-38613",
"aliases": [
"CVE-2025-38613"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "9dde4559e93955ccc47d588f7fd051684d55c4e7"
},
{
"fixed": "19dedd4f70f5a6505e7c601ef7dd40542d1d9aa5"
},
{
"fixed": "a739d3b13bff0dfa1aec679d08c7062131a2a425"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38613.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.16.1"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-38613.json"
}
}
],
"modified": "2026-10-28T02:30:51.528966558Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/19dedd4f70f5a6505e7c601ef7dd40542d1d9aa5",
"https://git.kernel.org/stable/c/a739d3b13bff0dfa1aec679d08c7062131a2a425",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38613.json",
"https://nvd.nist.gov/vuln/detail/CVE-2025-38613",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/38xxx/CVE-2025-38613.json"
}
},
"related_cves": [
{
"value": "CVE-2025-38613",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 520079,
"published_at": "2025-08-19T17:03:55.457+00:00"
}