From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: accel/amdxdna: Fix user buffer VMA checking and page pinning locking
Date: Sat, 16 May 2026 08:54:21 +1000 [thread overview]
Message-ID: <review-overall-20260515155423.743134-1-lizhi.hou@amd.com> (raw)
In-Reply-To: <20260515155423.743134-1-lizhi.hou@amd.com>
Overall Series Review
Subject: accel/amdxdna: Fix user buffer VMA checking and page pinning locking
Author: Lizhi Hou <lizhi.hou@amd.com>
Patches: 1
Reviewed: 2026-05-16T08:54:21.992526
---
This is a single-patch fix addressing a real **TOCTOU (time-of-check-time-of-use) vulnerability** in the amdxdna accelerator driver's user buffer handling. The core problem was that VMA permission checking (`readonly_va_entry`) and page pinning (`pin_user_pages_fast`) were done without a common lock, allowing an attacker to modify the VMA (via `mprotect`, `munmap`/`mmap`, etc.) between the check and the pin.
The fix is well-targeted and correct in its approach:
1. Holds `mmap_read_lock` across **both** the VMA permission check and the page pinning.
2. Switches from `pin_user_pages_fast` to `pin_user_pages`, which expects the caller to already hold `mmap_read_lock`.
3. Adds `VM_MAYWRITE` to the writability check to close a `mprotect`-based bypass.
The error paths are correctly restructured (goto → break, with unlock before cleanup jump). The locking semantics are consistent with the GUP API contract.
**One minor concern** exists (detailed below) but overall this is a sound security fix that should be accepted.
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-05-15 22:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 15:54 [PATCH V1] accel/amdxdna: Fix user buffer VMA checking and page pinning locking Lizhi Hou
2026-05-15 22:54 ` Claude Code Review Bot [this message]
2026-05-15 22:54 ` Claude review: " Claude Code Review Bot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=review-overall-20260515155423.743134-1-lizhi.hou@amd.com \
--to=claude-review@example.com \
--cc=dri-devel-reviews@example.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox