high CVSS 7.8

CVE-2024-43839·Kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: bna: adjust 'name' buf size of bna_tcb and bna_ccb structures To have enough space to write all possible sprintf() args. Currently 'name' size is 16, but the first '%s' specifier may already need at least 16 characters, since 'bnad->netdev->name' is used there. For '%d' specifiers, assume that they require: * 1 char for 'tx_id + tx_info->tcb[i]->id' sum, BNAD_MAX_TXQ_PER_TX is 8 * 2 chars for 'rx_id + rx_info->rx_ctrl[i].ccb->id', BNAD_MAX_RXP_PER_RX is 16 And replace sprintf with snprintf. Detected using the static analysis tool - Svace.

Severity
high
Software
Kernel
Fixed in
6.10.3
Published
2024-08-17

Affected versions

From: 6.7

Until: 6.10.3

Fixed in: 6.10.3

How to fix this CVE

Update your Linux kernel to version 6.10.3 or later to patch a buffer overflow vulnerability in the Broadcom BNA network driver. This vulnerability could allow local users with sufficient privileges to trigger memory corruption through improper string formatting in the driver's internal data structures. Apply the kernel update through your distribution's package manager and reboot the system to activate the fix.

sudo dnf update kernel kernel-devel

Defensia detects this vulnerability

How to check if you are affected

  1. Step 1: Check your current kernel version by running `uname -r` and verify if it falls within the vulnerable range (6.7 to 6.10.2)
  2. Step 2: Identify if the Broadcom BNA driver is loaded by running `lsmod | grep bna` or checking `ethtool -i <interface_name>` for BNA driver presence
  3. Step 3: Search system logs for BNA driver errors using `dmesg | grep -i bna` or `grep -i bna /var/log/kern.log` for any buffer-related warnings or memory corruption messages
  4. Step 4: After updating, verify the new kernel version with `uname -r` and confirm it is 6.10.3 or later, then validate the BNA driver loaded without errors using `dmesg | tail -20`

FAQ

What is CVE-2024-43839?

CVE-2024-43839 is a buffer overflow vulnerability in the Linux kernel's Broadcom BNA network driver where the name buffer in the bna_tcb and bna_ccb structures is too small to safely accommodate sprintf() string formatting operations, potentially leading to memory corruption.

Is CVE-2024-43839 being actively exploited?

No, CVE-2024-43839 is not currently listed in the CISA Known Exploited Vulnerabilities catalog and no public exploits are available, though local privilege escalation remains a concern.

What versions of Kernel are affected by CVE-2024-43839?

Linux kernel versions 6.7 through 6.10.2 are affected. The vulnerability is patched in kernel version 6.10.3 and later.

How do I check if my server is vulnerable to CVE-2024-43839?

Run `uname -r` to check your kernel version; if it outputs a version between 6.7 and 6.10.2 and you have a Broadcom BNA network interface (check with `ethtool -i eth0`), your system is vulnerable.

Does Defensia detect CVE-2024-43839?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2024-43839 will appear in your dashboard with remediation steps.

Related Kernel CVEs

CVE-2024-42256CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: cifs: Fix server re-repick on subrequest retry When a subrequest is marked for needing retry, netfs will call cifs_prepare_write() which will make cifs repick the server for the op before renegotiating credits; it then calls cifs_issue_write() which invokes smb2_async_writev() - which re-repicks the server. If a different server is then selected, this causes the increment of server->in_flight to happen against one record and the decrement to happen against another, leading to misaccounting. Fix this by just removing the repick code in smb2_async_writev(). As this is only called from netfslib-driven code, cifs_prepare_write() should always have been called first, and so server should never be NULL and the preparatory step is repeated in the event that we do a retry. The problem manifests as a warning looking something like: WARNING: CPU: 4 PID: 72896 at fs/smb/client/smb2ops.c:97 smb2_add_credits+0x3f0/0x9e0 [cifs] ... RIP: 0010:smb2_add_credits+0x3f0/0x9e0 [cifs] ... smb2_writev_callback+0x334/0x560 [cifs] cifs_demultiplex_thread+0x77a/0x11b0 [cifs] kthread+0x187/0x1d0 ret_from_fork+0x34/0x60 ret_from_fork_asm+0x1a/0x30 Which may be triggered by a number of different xfstests running against an Azure server in multichannel mode. generic/249 seems the most repeatable, but generic/215, generic/249 and generic/308 may also show it.
CVE-2024-36031CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: keys: Fix overwrite of key expiration on instantiation The expiry time of a key is unconditionally overwritten during instantiation, defaulting to turn it permanent. This causes a problem for DNS resolution as the expiration set by user-space is overwritten to TIME64_MAX, disabling further DNS updates. Fix this by restoring the condition that key_set_expiry is only called when the pre-parser sets a specific expiry.
CVE-2024-38612CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ipv6: sr: fix invalid unregister error path The error path of seg6_init() is wrong in case CONFIG_IPV6_SEG6_LWTUNNEL is not defined. In that case if seg6_hmac_init() fails, the genl_unregister_family() isn't called. This issue exist since commit 46738b1317e1 ("ipv6: sr: add option to control lwtunnel support"), and commit 5559cea2d5aa ("ipv6: sr: fix possible use-after-free and null-ptr-deref") replaced unregister_pernet_subsys() with genl_unregister_family() in this error path.
CVE-2024-38623CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Use variable length array instead of fixed size Should fix smatch warning: ntfs_set_label() error: __builtin_memcpy() 'uni->name' too small (20 vs 256)
CVE-2021-47548CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port() The if statement: if (port >= DSAF_GE_NUM) return; limits the value of port less than DSAF_GE_NUM (i.e., 8). However, if the value of port is 6 or 7, an array overflow could occur: port_rst_off = dsaf_dev->mac_cb[port]->port_rst_off; because the length of dsaf_dev->mac_cb is DSAF_MAX_PORT_NUM (i.e., 6). To fix this possible array overflow, we first check port and if it is greater than or equal to DSAF_MAX_PORT_NUM, the function returns.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-43839. Free for 1 server.

Get started free