Stack-based Buffer Overflow Affecting perf package, versions <0:4.18.0-553.27.1.el8_10
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-7595638
- published 5 Aug 2024
- disclosed 29 Jul 2024
Introduced: 29 Jul 2024
CVE-2024-41042 Open this link in a new tabHow to fix?
Upgrade RHEL:8 perf to version 0:4.18.0-553.27.1.el8_10 or higher.
This issue was patched in RHSA-2024:8856.
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:
netfilter: nf_tables: prefer nft_chain_validate
nft_chain_validate already performs loop detection because a cycle will result in a call stack overflow (ctx->level >= NFT_JUMP_STACK_SIZE).
It also follows maps via ->validate callback in nft_lookup, so there appears no reason to iterate the maps again.
nf_tables_check_loops() and all its helper functions can be removed. This improves ruleset load time significantly, from 23s down to 12s.
This also fixes a crash bug. Old loop detection code can result in unbounded recursion:
BUG: TASK stack guard page was hit at .... Oops: stack guard page: 0000 [#1] PREEMPT SMP KASAN CPU: 4 PID: 1539 Comm: nft Not tainted 6.10.0-rc5+ #1 [..]
with a suitable ruleset during validation of register stores.
I can't see any actual reason to attempt to check for this from nft_validate_register_store(), at this point the transaction is still in progress, so we don't have a full picture of the rule graph.
For nf-next it might make sense to either remove it or make this depend on table->validate_state in case we could catch an error earlier (for improved error reporting to userspace).
References
- https://access.redhat.com/security/cve/CVE-2024-41042
- https://git.kernel.org/stable/c/717c91c6ed73e248de6a15bc53adefb81446c9d0
- https://git.kernel.org/stable/c/b6b6e430470e1c3c5513311cb35a15a205595abe
- https://git.kernel.org/stable/c/1947e4c3346faa8ac7e343652c0fd3b3e394202f
- https://git.kernel.org/stable/c/31c35f9f89ef585f1edb53e17ac73a0ca4a9712b
- https://git.kernel.org/stable/c/8246b7466c8da49d0d9e85e26cbd69dd6d3e3d1e
- https://git.kernel.org/stable/c/cd4348e0a50286282c314ad6d2b0740e7c812c24
- https://git.kernel.org/stable/c/9df785aeb7dcc8efd1d4110bb27d26005298ebae
- https://git.kernel.org/stable/c/cff3bd012a9512ac5ed858d38e6ed65f6391008c