{"id":"CVE-2026-23424","state":"PUBLISHED","title":"accel/amdxdna: Validate command buffer payload count","description":"In the Linux kernel, the following vulnerability has been resolved:\n\naccel/amdxdna: Validate command buffer payload count\n\nThe count field in the command header is used to determine the valid\npayload size. Verify that the valid payload does not exceed the remaining\nbuffer space.","publishedAt":"2026-04-03T13:24:32.622Z","updatedAt":"2026-08-05T12:21:38.064Z","severity":{"score":7.1,"label":"High","version":"3.1","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","source":"Linux"},"assigner":"Linux","products":["Linux Linux"],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"aac243092b707bb3018e951d470cc1a9bcbaba6c","status":"affected","lessThan":"3464e751755172ddbb849c1bd92f5f59e95c59a1","versionType":"git"},{"version":"aac243092b707bb3018e951d470cc1a9bcbaba6c","status":"affected","lessThan":"3ed2ae6b3fe869f99b75afd02045ba5c0c0773e2","versionType":"git"},{"version":"aac243092b707bb3018e951d470cc1a9bcbaba6c","status":"affected","lessThan":"901ec3470994006bc8dd02399e16b675566c3416","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/accel/amdxdna/amdxdna_ctx.c"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"6.14","status":"affected"},{"version":"0","status":"unaffected","lessThan":"6.14","versionType":"semver"},{"version":"6.18.17","status":"unaffected","lessThanOrEqual":"6.18.*","versionType":"semver"},{"version":"6.19.7","status":"unaffected","lessThanOrEqual":"6.19.*","versionType":"semver"},{"version":"7.0","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/accel/amdxdna/amdxdna_ctx.c"]}],"references":["https://git.kernel.org/stable/c/3464e751755172ddbb849c1bd92f5f59e95c59a1","https://git.kernel.org/stable/c/3ed2ae6b3fe869f99b75afd02045ba5c0c0773e2","https://git.kernel.org/stable/c/901ec3470994006bc8dd02399e16b675566c3416"],"weaknesses":[],"ingestedAt":"2026-10-29T20:11:21.040Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2026/23xxx/CVE-2026-23424.json","commit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-23424","state":"PUBLISHED","datePublished":"2026-04-03T13:24:32.622Z","dateUpdated":"2026-08-05T12:21:38.064Z","assignerShortName":"Linux","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateReserved":"2026-01-13T15:37:46.015Z"},"containers":{"cna":{"title":"accel/amdxdna: Validate command buffer payload count","descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\naccel/amdxdna: Validate command buffer payload count\n\nThe count field in the command header is used to determine the valid\npayload size. Verify that the valid payload does not exceed the remaining\nbuffer space."}],"affected":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"aac243092b707bb3018e951d470cc1a9bcbaba6c","status":"affected","lessThan":"3464e751755172ddbb849c1bd92f5f59e95c59a1","versionType":"git"},{"version":"aac243092b707bb3018e951d470cc1a9bcbaba6c","status":"affected","lessThan":"3ed2ae6b3fe869f99b75afd02045ba5c0c0773e2","versionType":"git"},{"version":"aac243092b707bb3018e951d470cc1a9bcbaba6c","status":"affected","lessThan":"901ec3470994006bc8dd02399e16b675566c3416","versionType":"git"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/accel/amdxdna/amdxdna_ctx.c"]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"6.14","status":"affected"},{"version":"0","status":"unaffected","lessThan":"6.14","versionType":"semver"},{"version":"6.18.17","status":"unaffected","lessThanOrEqual":"6.18.*","versionType":"semver"},{"version":"6.19.7","status":"unaffected","lessThanOrEqual":"6.19.*","versionType":"semver"},{"version":"7.0","status":"unaffected","lessThanOrEqual":"*","versionType":"original_commit_for_fix"}],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/accel/amdxdna/amdxdna_ctx.c"]}],"references":[{"url":"https://git.kernel.org/stable/c/3464e751755172ddbb849c1bd92f5f59e95c59a1"},{"url":"https://git.kernel.org/stable/c/3ed2ae6b3fe869f99b75afd02045ba5c0c0773e2"},{"url":"https://git.kernel.org/stable/c/901ec3470994006bc8dd02399e16b675566c3416"}],"metrics":[{"cvssV3_1":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","baseScore":7.1,"baseSeverity":"HIGH"},"scenarios":[{"lang":"en","value":"AV:L - The vulnerable command payload parsing is reached through local DRM accel device ioctls on /dev/accel/accelN, after creating and submitting an AMDXDNA command BO. It is not reachable from network or adjacent protocols.\nAC:L - The attacker controls the command BO header count and size and can trigger the over-read through normal create-hwctx/create-bo/exec-cmd ioctl flow. No race or condition outside attacker control is required.\nPR:L - The relevant amdxdna ioctls are not marked DRM_ROOT_ONLY and do not require CAP_SYS_ADMIN; a local unprivileged user with access to the accel device can reach them. This is basic local user access, not real root.\nUI:N - Exploitation is performed entirely by the attacking process issuing ioctls and submitting crafted command buffers. No victim user action is needed.\nS:U - The impact is within the local kernel/driver security authority on the same host. I found no VM escape, IOMMU bypass, or cross-authority boundary change.\nC:H - The missing count validation permits out-of-bounds reads past the user command BO, with lengths large enough to copy substantial adjacent kernel-mapped memory into firmware/device command buffers. Under the higher-severity rule, this is a high confidentiality impact.\nI:N - The vulnerable count path over-reads the source command BO, while the observed destination copies are separately bounded. I did not find a kernel out-of-bounds write or control-flow modification primitive caused by this specific missing check.\nA:H - The out-of-bounds kernel read can fault/oops when it crosses unmapped vmalloc or invalid mapped memory, and it is repeatable through crafted command submissions. Kernel crash or scheduler/firmware destabilization is high availability impact."}]}],"providerMetadata":{"shortName":"Linux","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","dateUpdated":"2026-08-05T12:21:38.064Z"},"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.14","versionEndExcluding":"6.18.17"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.14","versionEndExcluding":"6.19.7"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"6.14","versionEndExcluding":"7.0"}]}]}],"x_generator":{"engine":"bippy-1.2.0"}}}}}