Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
RHSA-2024:6206
No affected components available
Red Hat Security Advisory: kernel security update
The vulnerability requires local access to the device to be exploited. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability. The vulnerability can affect other systems as well, not just the initial system. There is a high impact on the availability of the system.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
Probability that this vulnerability will be exploited in the wild within the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
- CVE-2021-47069Upstream
- CVE-2021-47385Upstream
- CVE-2022-48743Upstream
- CVE-2022-48754Upstream
- CVE-2022-48757Upstream
- CVE-2023-52486Upstream
- CVE-2023-52619Upstream
- CVE-2023-52881Upstream
- CVE-2023-52883Upstream
- CVE-2024-21823Upstream
- CVE-2024-26720
In the Linux kernel, the following vulnerability has been resolved: mm/writeback: fix possible divide-by-zero in wb_dirty_limits(), again (struct dirty_throttle_control *)->thresh is an unsigned long, but is passed as the u32 divisor argument to div_u64(). On architectures where unsigned long is 64 bytes, the argument will be implicitly truncated. Use div64_u64() instead of div_u64() so that the value used in the "is this a safe division" check is the same as the divisor. Also, remove redundant cast of the numerator to u64, as that should happen implicitly. This would be difficult to exploit in memcg domain, given the ratio-based arithmetic domain_drity_limits() uses, but is much easier in global writeback domain with a BDI_CAP_STRICTLIMIT-backing device, using e.g. vm.dirty_bytes=(1<<32)*PAGE_SIZE so that dtc->thresh == (1<<32)
Upstream - CVE-2024-26810Upstream
- CVE-2024-26852Upstream
- CVE-2024-26853Upstream
- CVE-2024-26974Upstream
- CVE-2024-26993Upstream
- CVE-2024-33621Upstream
- CVE-2024-35789Upstream
- CVE-2024-35845Upstream
- CVE-2024-36017Upstream
- CVE-2024-36489Upstream
- CVE-2024-36883Upstream
- CVE-2024-36904Upstream
- CVE-2024-36941Upstream
- CVE-2024-36979Upstream
- CVE-2024-37356Upstream
- CVE-2024-38540Upstream
- CVE-2024-38570Upstream
- CVE-2024-38586Upstream
- CVE-2024-38596Upstream
- CVE-2024-39502Upstream
- CVE-2024-41076Upstream
- CVE-2024-41090Upstream
- CVE-2024-41091Upstream
- EUVD-2021-33717Upstream
- EUVD-2021-34390Upstream
- EUVD-2022-53622Upstream
- EUVD-2022-53633Upstream
- EUVD-2022-53636Upstream
- EUVD-2023-57111Upstream
- EUVD-2023-57243Upstream
- EUVD-2023-59594Upstream
- EUVD-2023-59596Upstream
- EUVD-2024-19435Upstream
- EUVD-2024-24072Upstream
- EUVD-2024-24114Upstream
- EUVD-2024-24115Upstream
- EUVD-2024-24236Upstream
- EUVD-2024-24255Upstream
- EUVD-2024-34580Upstream
- EUVD-2024-35544Upstream
- EUVD-2024-35782Upstream
- EUVD-2024-35827Upstream
- EUVD-2024-36122Upstream
- EUVD-2024-36235Upstream
- EUVD-2024-36255Upstream
- EUVD-2024-36291Upstream
- EUVD-2024-36329Upstream
- EUVD-2024-36980Upstream
- EUVD-2024-37403Upstream
- EUVD-2024-37433Upstream
- EUVD-2024-37449Upstream
- EUVD-2024-37459Upstream
- EUVD-2024-38028Upstream
- EUVD-2024-38873Upstream
- EUVD-2024-38887Upstream
- EUVD-2024-38888Upstream
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard