원문 설명
In the Linux kernel, the following vulnerability has been resolved: usb: gadget: f_fs: copy only received bytes on short ep0 read ffs_ep0_read() allocates its control-OUT data buffer with kmalloc() (not kzalloc) at the Length value from the Setup packet, then copies that full len to userspace regardless of how many bytes were actually received: data = kmalloc(len, GFP_KERNEL); ... ret = __ffs_ep0_queue_wait(ffs, data, len); if ((ret > 0) && (copy_to_user(buf, data, len))) ret = -EFAULT; __ffs_ep0_queue_wait() returns req->actual, which on a short control OUT transfer is strictly less than len. The copy_to_user() call still copies len bytes, so on a short OUT the last (len - ret) bytes of the kmalloc() buffer -- uninitialised slab residue -- are delivered to the FunctionFS daemon. Short ep0 OUT completions are specified USB control-transfer behavior and are produced by in-tree UDCs: * dwc2 continues on req->actual < req->length for ep0 DATA OUT (short-not-ok is the only ep0-OUT stall path). * aspeed_udc ends ep0 OUT on rx_len < ep->ep.maxpacket. * renesas_usbf logs "ep0 short packet" and completes the request. * dwc3 stalls on short IN but not on short OUT. A short ep0 OUT is therefore not evidence of a broken UDC; it is a normal condition f_fs has to cope with. The sibling gadgetfs implementation in drivers/usb/gadget/legacy/inode.c already does this correctly via min(len, dev->req->actual) before copy_to_user(). This patch brings f_fs.c to the same safe pattern rather than trimming at a defensive layer. The bug is reached from the FunctionFS device node, which in real deployments is owned by the privileged gadget daemon (adbd, UMS, composite gadget services, etc.); it is not reachable from unprivileged userspace. Linux host stacks normally reject short-wLength control OUTs before they reach the gadget, so reproducing this required a build that bypasses that host-side check. With the bypass in place, a 1-byte payload on a 64-byte Setup produces 63 bytes of non-canary slab residue in the daemon's read buffer. Fix by copying only ret (actually received) bytes to userspace.
영향받는 소프트웨어
- Linux kernel ≥ 6.13 < 6.18.35≥ 6.19 < 7.0.12≥ 5.16 < 6.1.176= 7.1≥ 2.6.35 < 5.15.210≥ 6.2 < 6.6.143 수정 버전: 6.18.35, 7.0.12, 6.1.176, 5.15.210 정확 일치
상세
- 공개일
- 2026-07-19
- 최종 수정
- 2026-11-16
- CVSS 벡터
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N- CWE
- CWE-125
- EPSS(30일 내 악용 확률)
- 0.26% (백분위 18)
참고 자료
- cve.org/CVE-2026-63895
- nvd.nist.gov/vuln/detail/CVE-2026-63895
- git.kernel.org/stable/c/23c1f7deb9dd8447ecde749850676302aa1e2bd3
- git.kernel.org/stable/c/4e036c10e7f4df5d951c69cc3697bc8e209c6d02
- git.kernel.org/stable/c/607730a414773a7cbe3037a64a6c64e72689ff5e
- git.kernel.org/stable/c/88874a19b2b093bfaaa1c0090fa536c44da8c08b
- git.kernel.org/stable/c/90ccf5fb63243fae1b4b3200f3310500500ecf2e
- git.kernel.org/stable/c/af32dbb2ca0b3d09271ab718d13857a457fa16f2
- git.kernel.org/stable/c/e835bf9a055f71874065a40780ca5560b7df8b33
내 서버의 버전을 직접 추적하세요
InfraGuard 는 모든 서버에 설치된 소프트웨어 버전을 수집하고, 알려진 취약점이 있는 버전을 알려 줍니다. 자체 호스팅이라 데이터가 내 네트워크를 벗어나지 않습니다.
이 제품은 NVD API 데이터를 사용하지만 NVD 의 보증이나 인증을 받은 것은 아닙니다. CVE® 는 The MITRE Corporation 의 등록 상표이며, CVE 레코드는 CVE Program 이용 약관에 따라 사용합니다.