CVSS: -EPSS: 0%CPEs: 2EXPL: 0CVE-2024-40999 – net: ena: Add validation for completion descriptors consistency
https://notcve.org/view.php?id=CVE-2024-40999
In the Linux kernel, the following vulnerability has been resolved: net: ena: Add validation for completion descriptors consistency Validate that `first` flag is set only for the first descriptor in multi-buffer packets. In case of an invalid descriptor, a reset will occur. A new reset reason for RX data corruption has been added. • https://git.kernel.org/stable/c/42146ee5286f16f1674a84f7c274dcca65c6ff2e https://git.kernel.org/stable/c/b37b98a3a0c1198bafe8c2d9ce0bc845b4e7a9a7 •
CVSS: 5.5EPSS: 0%CPEs: 3EXPL: 0CVE-2024-40998 – ext4: fix uninitialized ratelimit_state->lock access in __ext4_fill_super()
https://notcve.org/view.php?id=CVE-2024-40998
In the Linux kernel, the following vulnerability has been resolved: ext4: fix uninitialized ratelimit_state->lock access in __ext4_fill_super() In the following concurrency we will access the uninitialized rs->lock: ext4_fill_super ext4_register_sysfs // sysfs registered msg_ratelimit_interval_ms // Other processes modify rs->interval to // non-zero via msg_ratelimit_interval_ms ext4_orphan_cleanup ext4_msg(sb, KERN_INFO, "Errors on filesystem, " __ext4_msg ___ratelimit(&(EXT4_SB(sb)->s_msg_ratelimit_state) if (! • https://git.kernel.org/stable/c/23afcd52af06880c6c913a0ad99022b8937b575c https://git.kernel.org/stable/c/645267906944a9aeec9d5c56ee24a9096a288798 https://git.kernel.org/stable/c/b4b4fda34e535756f9e774fb2d09c4537b7dfd1c https://access.redhat.com/security/cve/CVE-2024-40998 https://bugzilla.redhat.com/show_bug.cgi?id=2297582 •
CVSS: 5.1EPSS: 0%CPEs: 3EXPL: 0CVE-2024-40997 – cpufreq: amd-pstate: fix memory leak on CPU EPP exit
https://notcve.org/view.php?id=CVE-2024-40997
In the Linux kernel, the following vulnerability has been resolved: cpufreq: amd-pstate: fix memory leak on CPU EPP exit The cpudata memory from kzalloc() in amd_pstate_epp_cpu_init() is not freed in the analogous exit function, so fix that. [ rjw: Subject and changelog edits ] • https://git.kernel.org/stable/c/448efb7ea0bfa2c4e27c5a2eb5684fd225cd12cd https://git.kernel.org/stable/c/8015c17fe11a8608cc3eb83d0ab831e1845a9582 https://git.kernel.org/stable/c/cea04f3d9aeebda9d9c063c0dfa71e739c322c81 https://access.redhat.com/security/cve/CVE-2024-40997 https://bugzilla.redhat.com/show_bug.cgi?id=2297581 • CWE-402: Transmission of Private Resources into a New Sphere ('Resource Leak') •
CVSS: -EPSS: 0%CPEs: 5EXPL: 0CVE-2024-40996 – bpf: Avoid splat in pskb_pull_reason
https://notcve.org/view.php?id=CVE-2024-40996
In the Linux kernel, the following vulnerability has been resolved: bpf: Avoid splat in pskb_pull_reason syzkaller builds (CONFIG_DEBUG_NET=y) frequently trigger a debug hint in pskb_may_pull. We'd like to retain this debug check because it might hint at integer overflows and other issues (kernel code should pull headers, not huge value). In bpf case, this splat isn't interesting at all: such (nonsensical) bpf programs are typically generated by a fuzzer anyway. Do what Eric suggested and suppress such warning. For CONFIG_DEBUG_NET=n we don't need the extra check because pskb_may_pull will do the right thing: return an error without the WARN() backtrace. • https://git.kernel.org/stable/c/8af60bb2b215f478b886f1d6d302fefa7f0b917d https://git.kernel.org/stable/c/1b2b26595bb09febf14c5444c873ac4ec90a5a77 https://git.kernel.org/stable/c/219eee9c0d16f1b754a8b85275854ab17df0850a https://git.kernel.org/stable/c/fff05b2b004d9a8a2416d08647f3dc9068e357c8 https://git.kernel.org/stable/c/dacc15e9cb248d19e5fc63c54bef0b9b55007761 https://git.kernel.org/stable/c/7f9644782c559635bd676c12c59389a34ed7c866 https://git.kernel.org/stable/c/5e90258303a358e88737afb5048bee9113beea3a https://git.kernel.org/stable/c/2bbe3e5a2f4ef69d13be54f1cf895b465 •
CVSS: 5.5EPSS: 0%CPEs: 7EXPL: 0CVE-2024-40995 – net/sched: act_api: fix possible infinite loop in tcf_idr_check_alloc()
https://notcve.org/view.php?id=CVE-2024-40995
In the Linux kernel, the following vulnerability has been resolved: net/sched: act_api: fix possible infinite loop in tcf_idr_check_alloc() syzbot found hanging tasks waiting on rtnl_lock [1] A reproducer is available in the syzbot bug. When a request to add multiple actions with the same index is sent, the second request will block forever on the first request. • https://git.kernel.org/stable/c/0190c1d452a91c38a3462abdd81752be1b9006a8 https://git.kernel.org/stable/c/0d8a2d287c8a394c0d4653f0c6c7be4c688e5a74 https://git.kernel.org/stable/c/c6a7da65a296745535a964be1019ec7691b0cb90 https://git.kernel.org/stable/c/25987a97eec4d5f897cd04ee1b45170829c610da https://git.kernel.org/stable/c/6fc78d67f51aeb9a542d39a8714e16bc411582d4 https://git.kernel.org/stable/c/5f926aa96b08b6c47178fe1171e7ae331c695fc2 https://git.kernel.org/stable/c/7a0e497b597df7c4cf2b63fc6e9188b6cabe5335 https://git.kernel.org/stable/c/d864319871b05fadd153e0aede4811ca7 • CWE-833: Deadlock •