Incorrect Check of Function Return Value Affecting perf package, versions <0:4.18.0-372.118.1.el8_6
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-RHEL8-PERF-7684128
- published 14 Aug 2024
- disclosed 16 Jul 2024
Introduced: 16 Jul 2024
CVE-2022-48829 Open this link in a new tabHow to fix?
Upgrade RHEL:8 perf to version 0:4.18.0-372.118.1.el8_6 or higher.
This issue was patched in RHSA-2024:5281.
NVD Description
Note: Versions mentioned in the description apply only to the upstream perf package and not the perf package as distributed by RHEL.
See How to fix? for RHEL:8 relevant fixed versions and status.
In the Linux kernel, the following vulnerability has been resolved:
NFSD: Fix NFSv3 SETATTR/CREATE's handling of large file sizes
iattr::ia_size is a loff_t, so these NFSv3 procedures must be careful to deal with incoming client size values that are larger than s64_max without corrupting the value.
Silently capping the value results in storing a different value than the client passed in which is unexpected behavior, so remove the min_t() check in decode_sattr3().
Note that RFC 1813 permits only the WRITE procedure to return NFS3ERR_FBIG. We believe that NFSv3 reference implementations also return NFS3ERR_FBIG when ia_size is too large.
References
- https://access.redhat.com/security/cve/CVE-2022-48829
- https://git.kernel.org/stable/c/37f2d2cd8eadddbbd9c7bda327a9393399b2f89b
- https://git.kernel.org/stable/c/a231ae6bb50e7c0a9e9efd7b0d10687f1d71b3a3
- https://git.kernel.org/stable/c/a648fdeb7c0e17177a2280344d015dba3fbe3314
- https://git.kernel.org/stable/c/aa9051ddb4b378bd22e72a67bc77b9fc1482c5f0