sync: cherry-pick for release/0.23.x#2766
Conversation
…ing due to integer overflow Add validation in ppm_cmsg_nxthdr to ensure cmsg_aligned_len is at least sizeof(ppm_cmsghdr) after alignment calculation. This prevents an infinite loop when malformed ancillary data contains cmsg_len = 0xFFFFFFFFFFFFFFFF, which causes integer overflow in PPM_CMSG_ALIGN macro, resulting in cmsg_aligned_len = 0 and preventing forward progress in the loop. Signed-off-by: Francesco Emmi <francesco.emmi@sysdig.com>
release 0.22.xrelease/0.22.x
Perf diff from master - unit testsHeap diff from master - unit testsHeap diff from master - scap fileBenchmarks diff from master |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2766 +/- ##
==========================================
- Coverage 74.57% 74.57% -0.01%
==========================================
Files 292 292
Lines 30025 30026 +1
Branches 4657 4658 +1
==========================================
Hits 22392 22392
- Misses 7633 7634 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deepskyblue86, ekoops, leogr The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
I don't know what happened here. I'm pretty sure I selected the right branch, but this appears to be merged on master. I'm gonna open another PR |
release/0.22.xrelease/0.23.x
What type of PR is this?
/kind sync
Any specific area of the project related to this PR?
/area libsinsp
Does this PR require a change in the driver versions?
What this PR does / why we need it:
This PR cherry-picks from master the content of the following merged PRs:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
/milestone 0.23.0
Does this PR introduce a user-facing change?: