Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

usbip: CCID usage can trigger a kernel bug #261

Open
robin-nitrokey opened this issue May 5, 2023 · 0 comments
Open

usbip: CCID usage can trigger a kernel bug #261

robin-nitrokey opened this issue May 5, 2023 · 0 comments
Labels
bug Something isn't working runner:usbip

Comments

@robin-nitrokey
Copy link
Member

As discussed in #149, using the usbip runner with CCID can trigger a kernel bug:

usercopy: Kernel memory exposure attempt detected from SLUB object 'kmalloc-16' (offset 0, size 64)!
kernel BUG at mm/usercopy.c:99

This is probably caused by usbip-device ignoring the maximum packet length configured by the kernel, see this discussion.
@robin-nitrokey robin-nitrokey added bug Something isn't working runner:usbip labels May 5, 2023
@robin-nitrokey robin-nitrokey mentioned this issue Jul 19, 2023
Closed
robin-nitrokey added a commit that referenced this issue Jul 19, 2023
@robin-nitrokey
usbip: Disable CCID by default
53178b6 
This patch adds a ccid feature to the usbip runner for the CCID
transport and disables it by default.  This is to avoid accidentally
triggering the kernel bug described in this issue:
    #261

Fixes: #325
@robin-nitrokey robin-nitrokey mentioned this issue Jul 19, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working runner:usbip
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@robin-nitrokey