high CVSS 7.1

CVE-2024-41090·Kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: tap: add missing verification for short frame The cited commit missed to check against the validity of the frame length in the tap_get_user_xdp() path, which could cause a corrupted skb to be sent downstack. Even before the skb is transmitted, the tap_get_user_xdp()-->skb_set_network_header() may assume the size is more than ETH_HLEN. Once transmitted, this could either cause out-of-bound access beyond the actual length, or confuse the underlayer with incorrect or inconsistent header length in the skb metadata. In the alternative path, tap_get_user() already prohibits short frame which has the length less than Ethernet header size from being transmitted. This is to drop any frame shorter than the Ethernet header size just like how tap_get_user() does. CVE: CVE-2024-41090

Severity
high
Software
Kernel
Fixed in
6.10.2
Published
2024-07-29

Affected versions

From: 6.10

Until: 6.10.2

Fixed in: 6.10.2

How to fix this CVE

Update your Linux kernel to version 6.10.2 or later to patch the TAP device frame validation vulnerability. This update adds mandatory length checks in the tap_get_user_xdp() code path to prevent malformed network frames from corrupting the socket buffer. Systems running kernel versions 6.10 through 6.10.1 should prioritize this update, as the vulnerability could lead to memory access violations or network stack confusion during packet processing.

sudo dnf update kernel kernel-devel && sudo reboot

Defensia detects this vulnerability

How to check if you are affected

  1. Run `uname -r` to verify your current kernel version and confirm if it falls within the vulnerable range (6.10.0 to 6.10.1)
  2. Check if TAP networking is in use on your system by running `ip link show | grep tun` or `cat /proc/net/dev | grep tap`
  3. Search system logs for TAP-related errors using `sudo journalctl -u kernel | grep -i tap` or `sudo dmesg | grep -i tap` to identify if the vulnerability was triggered
  4. After applying the kernel update, verify the patch with `uname -r` and confirm the new version is 6.10.2 or higher

FAQ

What is CVE-2024-41090?

CVE-2024-41090 is a kernel vulnerability in the TAP virtual network device driver that fails to validate the minimum frame length before processing XDP packets. This can result in corrupted socket buffers being sent to lower network layers, potentially causing memory corruption or network stack inconsistencies.

Is CVE-2024-41090 being actively exploited?

No, CVE-2024-41090 is not currently being actively exploited according to CISA KEV data, and no public exploits have been released.

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

Kernel versions 6.10.0 through 6.10.1 are affected. The vulnerability was introduced in a preceding commit and fixed in kernel 6.10.2.

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

Run `uname -r` to display your kernel version. If the output shows version 6.10.0 or 6.10.1, your system is vulnerable and requires an immediate kernel update.

Does Defensia detect CVE-2024-41090?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Kernel is installed on a monitored server, CVE-2024-41090 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-41090. Free for 1 server.

Get started free