Improper Input Validation Affecting kernel-abi-whitelists package, versions *
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-CENTOS7-KERNELABIWHITELISTS-6301841
- published 28 Feb 2024
- disclosed 27 Feb 2024
Introduced: 27 Feb 2024
CVE-2021-46945 Open this link in a new tabHow to fix?
There is no fixed version for Centos:7
kernel-abi-whitelists
.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-abi-whitelists
package and not the kernel-abi-whitelists
package as distributed by Centos
.
See How to fix?
for Centos:7
relevant fixed versions and status.
In the Linux kernel, the following vulnerability has been resolved:
ext4: always panic when errors=panic is specified
Before commit 014c9caa29d3 ("ext4: make ext4_abort() use __ext4_error()"), the following series of commands would trigger a panic:
- mount /dev/sda -o ro,errors=panic test
- mount /dev/sda -o remount,abort test
After commit 014c9caa29d3, remounting a file system using the test mount option "abort" will no longer trigger a panic. This commit will restore the behaviour immediately before commit 014c9caa29d3. (However, note that the Linux kernel's behavior has not been consistent; some previous kernel versions, including 5.4 and 4.19 similarly did not panic after using the mount option "abort".)
This also makes a change to long-standing behaviour; namely, the following series commands will now cause a panic, when previously it did not:
- mount /dev/sda -o ro,errors=panic test
- echo test > /sys/fs/ext4/sda/trigger_fs_error
However, this makes ext4's behaviour much more consistent, so this is a good thing.