{"id":"CVE-2025-38667","state":"PUBLISHED","title":"iio: fix potential out-of-bound write","description":"In the Linux kernel, the following vulnerability has been resolved:\n\niio: fix potential out-of-bound write\n\nThe buffer is set to 20 characters. If a caller write more characters,\ncount is truncated to the max available space in \"simple_write_to_buffer\".\nTo protect from OoB access, check that the input size fit into buffer and\nadd a zero terminator after copy to the end of the copied data.","publishedAt":"2025-08-22T16:02:58.865Z","updatedAt":"2026-08-05T12:03:50.401Z","severity":{"score":7.8,"label":"High","version":"3.1","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","source":"Linux"},"assigner":"Linux","products":["Linux Linux"],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"6d5dd486c715908b5a6ed02315a15ff044a91025","status":"affected","lessThan":"81a635b6eccd6fc889f6d07ab9583b705f739ce1","versionType":"git"},{"version":"6d5dd486c715908b5a6ed02315a15ff044a91025","status":"affected","lessThan":"16285a0931869baa618b1f5d304e1e9d090470a8","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/iio/industrialio-core.c"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"6.15","status":"affected"},{"version":"0","status":"unaffected","lessThan":"6.15","versionType":"semver"},{"version":"6.15.9","status":"unaffected","lessThanOrEqual":"6.15.*","versionType":"semver"},{"version":"6.16","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/iio/industrialio-core.c"]}],"references":["https://git.kernel.org/stable/c/81a635b6eccd6fc889f6d07ab9583b705f739ce1","https://git.kernel.org/stable/c/16285a0931869baa618b1f5d304e1e9d090470a8"],"weaknesses":[],"ingestedAt":"2026-10-29T20:09:09.358Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2025/38xxx/CVE-2025-38667.json","commit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2025-38667","state":"PUBLISHED","datePublished":"2025-08-22T16:02:58.865Z","dateUpdated":"2026-08-05T12:03:50.401Z","assignerShortName":"Linux","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateReserved":"2025-04-16T04:51:24.031Z"},"containers":{"cna":{"title":"iio: fix potential out-of-bound write","descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\niio: fix potential out-of-bound write\n\nThe buffer is set to 20 characters. If a caller write more characters,\ncount is truncated to the max available space in \"simple_write_to_buffer\".\nTo protect from OoB access, check that the input size fit into buffer and\nadd a zero terminator after copy to the end of the copied data."}],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"6d5dd486c715908b5a6ed02315a15ff044a91025","status":"affected","lessThan":"81a635b6eccd6fc889f6d07ab9583b705f739ce1","versionType":"git"},{"version":"6d5dd486c715908b5a6ed02315a15ff044a91025","status":"affected","lessThan":"16285a0931869baa618b1f5d304e1e9d090470a8","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/iio/industrialio-core.c"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"6.15","status":"affected"},{"version":"0","status":"unaffected","lessThan":"6.15","versionType":"semver"},{"version":"6.15.9","status":"unaffected","lessThanOrEqual":"6.15.*","versionType":"semver"},{"version":"6.16","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/iio/industrialio-core.c"]}],"references":[{"url":"https://git.kernel.org/stable/c/81a635b6eccd6fc889f6d07ab9583b705f739ce1"},{"url":"https://git.kernel.org/stable/c/16285a0931869baa618b1f5d304e1e9d090470a8"}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - The bug is triggered by a plain write(2) syscall on the debugfs file /sys/kernel/debug/iio/<dev>/direct_reg_access, which requires local access to the system. There is no network-facing path to iio_debugfs_write_reg.\nAC:L - A single write() with an oversized count and a 79-byte userspace buffer deterministically produces the out-of-bounds write; the attacker fully controls the offset (80 up to MAX_RW_COUNT) with no race, no memory-layout dependency, and no retries needed.\nPR:L - Reaching the node needs only local access to a mounted debugfs, whose IIO sensor nodes are routinely relaxed to service/HAL accounts on Android, embedded and industrial deployments where IIO drivers live; consistent with prior kernel-CNA scoring of debugfs-reachable memory-safety bugs (CVE-2026-43380, CVE-2026-46190) this is Low rather than High.\nUI:N - The attacker performs the entire attack themselves with an open() plus write() on an already-present debugfs node; no victim action, mount, or file-open by another user is required.\nS:U - The corruption is confined to kernel memory managed by the same kernel security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - The attacker-controlled NUL write into the kernel stack can zero bytes of saved pointers, length, or index fields in adjacent frames, which is leverageable into arbitrary kernel-memory disclosure; per guidance, memory corruption exploitable for info disclosure scores High.\nI:H - This is a genuine out-of-bounds write with a fully attacker-controlled offset, allowing a zero byte to be placed over saved return addresses, stack canary bytes, or (without VMAP_STACK) adjacent kernel heap data, giving a control-flow-hijack primitive.\nA:H - Large count values drive the write into the VMAP_STACK guard page or corrupt saved stack state, producing an oops, double fault, or panic that can be triggered repeatedly."}]}],"providerMetadata":{"shortName":"Linux","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateUpdated":"2026-08-05T12:03:50.401Z"},"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.15","versionEndExcluding":"6.15.9"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.15","versionEndExcluding":"6.16"}]}]}],"x_generator":{"engine":"bippy-1.2.0"}}}}}