high CVSS 7.8

CVE-2024-26739·Kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: net/sched: act_mirred: don't override retval if we already lost the skb If we're redirecting the skb, and haven't called tcf_mirred_forward(), yet, we need to tell the core to drop the skb by setting the retcode to SHOT. If we have called tcf_mirred_forward(), however, the skb is out of our hands and returning SHOT will lead to UaF. Move the retval override to the error path which actually need it.

Severity
high
Software
Kernel
Fixed in
6.7.7
Published
2024-04-03

Affected versions

From: 6.7

Until: 6.7.7

Fixed in: 6.7.7

How to fix this CVE

Update your Linux kernel to version 6.7.7 or later to resolve a use-after-free vulnerability in the traffic scheduling mirror action handler. This flaw could allow a local attacker with unprivileged access to cause a kernel crash or potentially execute arbitrary code. Apply the kernel update through your distribution's package manager and reboot your system to activate the patched version.

sudo dnf update kernel && sudo reboot

Defensia detects this vulnerability

How to check if you are affected

  1. Check your current kernel version: uname -r (vulnerable if output shows 6.7.0 through 6.7.6)
  2. Verify the affected component is in use by checking: cat /proc/sys/net/sched/act_mirred (if present, the qdisc mirror action is loaded)
  3. Search system logs for kernel panics related to the mirred scheduler: grep -i 'use.after.free\|uaf\|mirred' /var/log/kern.log /var/log/messages
  4. Confirm the fix is applied by running: uname -r (should show 6.7.7 or later after reboot)

FAQ

What is CVE-2024-26739?

This vulnerability exists in the Linux kernel's traffic control subsystem, specifically in the mirror action (act_mirred) handler. Under certain conditions, the kernel incorrectly manages memory references when redirecting network packets, leading to a use-after-free condition that can crash the kernel or allow local code execution.

Is CVE-2024-26739 being actively exploited?

No, this CVE is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits have been released. However, the high CVSS score (7.8) and local attack vector make it a priority for patching.

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

Linux kernel versions 6.7 through 6.7.6 are vulnerable. The fix is included in kernel 6.7.7 and all subsequent releases.

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

Run `uname -r` to display your kernel version. If the output shows a version between 6.7.0 and 6.7.6 inclusive, your system is vulnerable and requires an immediate kernel update.

Does Defensia detect CVE-2024-26739?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2024-26739 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-38541CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: of: module: add buffer overflow check in of_modalias() In of_modalias(), if the buffer happens to be too small even for the 1st snprintf() call, the len parameter will become negative and str parameter (if not NULL initially) will point beyond the buffer's end. Add the buffer overflow check after the 1st snprintf() call and fix such check after the strlen() call (accounting for the terminating NUL char).
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.
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-2022-48716CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: wcd938x: fix incorrect used of portid Mixer controls have the channel id in mixer->reg, which is not same as port id. port id should be derived from chan_info array. So fix this. Without this, its possible that we could corrupt struct wcd938x_sdw_priv by accessing port_map array out of range with channel id instead of port id.

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-26739. Free for 1 server.

Get started free