-
Notifications
You must be signed in to change notification settings - Fork 220
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.
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
Validate IOCTL header length #1256
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1256 +/- ##
==========================================
- Coverage 88.04% 88.04% -0.01%
==========================================
Files 101 101
Lines 17488 17546 +58
==========================================
+ Hits 15397 15448 +51
- Misses 2091 2098 +7
Continue to review full report at Codecov.
|
7c509f0
to
bd57c52
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not add safe add for the IOCTL processing as well?
I don't understand your question, can you elaborate? |
What I meant to ask is, is ebpf_safe_size_t_add/multiply not required in similar IOCTL processing code? Such as line 324 in ebpf_core.c ? |
@shankarseal that particular line does not need it because request->header.length is only 16 bits, so maxes out at 65535. That means |
935540e
to
57cc13f
Compare
Description
Validate the header.length passed to various requests.
Also add one test case that's part of #1139
Testing
Includes updated tests.
Documentation
No impact.