In the Linux kernel, the following vulnerability has been resolved:
net/mlx5e: Fix null deref accessing lag dev
It could be the lag dev is null so stop processing the event. In bond_enslave() the active/backup slave being set before setting the upper dev so first event is without an upper dev. After setting the upper dev with bond_master_upper_dev_link() there is a second event and in that event we have an upper dev.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Amazon Linux Ami 2 | — | Upgrade python-perfUpgrade kernel-toolsUpgrade bpftoolUpgrade kernel-debuginfo-common-x86_64Upgrade kernel-debuginfo-common-aarch64Upgrade perf-debuginfoUpgrade kernel-develUpgrade kernel-tools-debuginfoUpgrade python-perf-debuginfoUpgrade perfUpgrade kernelUpgrade kernel-headersUpgrade bpftool-debuginfoUpgrade kernel-tools-develUpgrade kernel-debuginfo | Aug 2, 2024 | Mar 25, 2024 |
| Debian | — | Upgrade linux | Jul 30, 2024 | Mar 25, 2024 |
| Redhat_linux | — | No solution exists | Jul 9, 2025 | Mar 25, 2024 |
| Suse | — | Upgrade kernel-docsUpgrade kernel-symsUpgrade kernel-64kbUpgrade kernel-sourceUpgrade kernel-zfcpdumpUpgrade kernel-default-develUpgrade kernel-preemptUpgrade kernel-macrosUpgrade kernel-obs-buildUpgrade kernel-64kb-develUpgrade kernel-develUpgrade kernel-default-baseUpgrade reiserfs-kmp-defaultUpgrade kernel-defaultUpgrade kernel-preempt-devel | Aug 9, 2024 | Mar 25, 2024 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub