CVE-2022-49581·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: be2net: Fix buffer overflow in be_get_module_eeprom be_cmd_read_port_transceiver_data assumes that it is given a buffer that is at least PAGE_DATA_LEN long, or twice that if the module supports SFF 8472. However, this is not always the case. Fix this by passing the desired offset and length to be_cmd_read_port_transceiver_data so that we only copy the bytes once.
- Severity
- high
- Software
- Kernel
- Fixed in
- 5.18.15
- Published
- 2025-02-26
Affected versions
From: 5.16
Until: 5.18.15
Fixed in: 5.18.15
How to fix this CVE
Update your Linux kernel to version 5.18.15 or later to remediate this buffer overflow vulnerability in the be2net driver's module EEPROM reading function. The vulnerability allows a local privileged attacker to trigger memory corruption by requesting transceiver data without proper buffer boundary validation. Apply the kernel update immediately to all affected systems running kernel versions 5.16 through 5.18.14.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your current kernel version by running: uname -r
- Step 2: Verify if be2net driver is loaded on your system: lsmod | grep be2net
- Step 3: Search system logs for be_get_module_eeprom errors: grep -i 'be_get_module_eeprom\|be2net' /var/log/kern.log /var/log/messages
- Step 4: After patching, reboot and confirm the new kernel is running: uname -r (should show 5.18.15 or later)
FAQ
What is CVE-2022-49581?
This is a buffer overflow vulnerability in the Broadcom be2net network driver that occurs when the kernel reads module EEPROM data without properly validating buffer sizes, allowing local privileged users to cause memory corruption.
Is CVE-2022-49581 being actively exploited?
No, according to CISA KEV data, this vulnerability is not actively exploited in the wild. However, it requires local privilege to trigger, so patching remains important for systems with untrusted local users.
What versions of Kernel are affected by CVE-2022-49581?
Linux kernel versions 5.16 through 5.18.14 are vulnerable. Version 5.18.15 and later contain the fix.
How do I check if my server is vulnerable to CVE-2022-49581?
Run 'uname -r' to get your kernel version, then verify it is below 5.18.15. Additionally, confirm the be2net driver is present with 'lsmod | grep be2net' only on systems with Broadcom network adapters.
Does Defensia detect CVE-2022-49581?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2022-49581 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/18043da94c023f3ef09c15017bdb04e8f695ef10
- https://git.kernel.org/stable/c/665cbe91de2f7c97c51ca8fce39aae26477c1948
- https://git.kernel.org/stable/c/8ff4f9df73e5c551a72ee6034886c17e8de6596d
- https://git.kernel.org/stable/c/a5a8fc0679a8fd58d47aa2ebcfc5742631f753f9
- https://git.kernel.org/stable/c/a8569f76df7ec5b4b51155c57523a0b356db5741
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2022-49581. Free for 1 server.
Get started free