-
Notifications
You must be signed in to change notification settings - Fork 8
[FIPS 9.2] Bluetooth: L2CAP: Fix l2cap_global_chan_by_psm #95
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
[FIPS 9.2] Bluetooth: L2CAP: Fix l2cap_global_chan_by_psm #95
Conversation
jira VULN-211 cve CVE-2022-42896 commit-author Luiz Augusto von Dentz <[email protected]> commit f937b75 l2cap_global_chan_by_psm shall not return fixed channels as they are not meant to be connected by (S)PSM. Signed-off-by: Luiz Augusto von Dentz <[email protected]> Reviewed-by: Tedd Ho-Jeong An <[email protected]> (cherry picked from commit f937b75) Signed-off-by: Greg Rose <[email protected]>
Actually I take back the Could you pull this change in but also change it from |
I can do that! |
Done! |
Uh, wait... I did not do the pull_request_target -> pull_request change. Let me fix that up. |
Since we need to make sure external contributors code actually compiles prior to merging. To get access to the forked repos merge request we need to switch over our push/pull_request to pull_request_target. In addition we're fixing up some Naming Conventions, adding aarch64 to this branch and fixing the naming so that we can quickly identify if the CI is for x86_64 or aarch64. Removes pull request checker it is being rewritten and doesn't work as intented for fork merges.
a8f1a4d
to
61eb857
Compare
OK, now. |
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.
jira VULN-211
cve CVE-2022-42896
Builds and Loads
build.log
Kernel Selftests
No significant difference between the before and after kernel selftest log files - some flap in the raw_skew test but not related to our change so ignored.
kernel-selftests-before.log
kernel-selftests-after.log
Kernel Selftests with lockdep, kmemleak and stress
I ran the tests with additional kernel debugging and stressing the system - no panics or unexpected traces (the kernel selftests for locking always throw some traces).
kernel-selftests-ldp_stress_on.log
Similar to several other PRs in this line for CVE-2022-42896.