high CVSS 7.8

CVE-2021-47458·Kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: ocfs2: mount fails with buffer overflow in strlen Starting with kernel 5.11 built with CONFIG_FORTIFY_SOURCE mouting an ocfs2 filesystem with either o2cb or pcmk cluster stack fails with the trace below. Problem seems to be that strings for cluster stack and cluster name are not guaranteed to be null terminated in the disk representation, while strlcpy assumes that the source string is always null terminated. This causes a read outside of the source string triggering the buffer overflow detection. detected buffer overflow in strlen ------------[ cut here ]------------ kernel BUG at lib/string.c:1149! invalid opcode: 0000 [#1] SMP PTI CPU: 1 PID: 910 Comm: mount.ocfs2 Not tainted 5.14.0-1-amd64 #1 Debian 5.14.6-2 RIP: 0010:fortify_panic+0xf/0x11 ... Call Trace: ocfs2_initialize_super.isra.0.cold+0xc/0x18 [ocfs2] ocfs2_fill_super+0x359/0x19b0 [ocfs2] mount_bdev+0x185/0x1b0 legacy_get_tree+0x27/0x40 vfs_get_tree+0x25/0xb0 path_mount+0x454/0xa20 __x64_sys_mount+0x103/0x140 do_syscall_64+0x3b/0xc0 entry_SYSCALL_64_after_hwframe+0x44/0xae

Severity
high
Software
Kernel
Fixed in
5.14.15
Published
2024-05-22

Affected versions

From: 5.11

Until: 5.14.15

Fixed in: 5.14.15

How to fix this CVE

Update your Linux kernel to version 5.14.15 or later to fix a buffer overflow vulnerability in OCFS2 filesystem mounting. This vulnerability affects systems running kernel versions 5.11 through 5.14.14 that are compiled with CONFIG_FORTIFY_SOURCE enabled. The issue occurs when mounting OCFS2 filesystems with o2cb or pcmk cluster stacks due to improper null-termination handling of cluster stack and cluster name strings, which can cause kernel panics during mount operations.

sudo dnf update kernel

Defensia detects this vulnerability

How to check if you are affected

  1. Step 1: Check your current kernel version by running: uname -r
  2. Step 2: Verify if CONFIG_FORTIFY_SOURCE is enabled in your kernel: cat /boot/config-$(uname -r) | grep CONFIG_FORTIFY_SOURCE
  3. Step 3: Check if OCFS2 is loaded on your system: lsmod | grep ocfs2
  4. Step 4: Review kernel logs for buffer overflow errors during OCFS2 mount attempts: sudo dmesg | grep -i 'buffer overflow\|ocfs2\|fortify_panic'
  5. Step 5: Verify the fix by confirming your kernel version is 5.14.15 or later: uname -r | grep -E '5\.1[5-9]|5\.2[0-9]|[6-9]\.[0-9]'

FAQ

What is CVE-2021-47458?

CVE-2021-47458 is a buffer overflow vulnerability in the Linux kernel's OCFS2 filesystem driver that occurs when mounting filesystems with o2cb or pcmk cluster stacks. The vulnerability is triggered because cluster stack and cluster name strings from disk are not properly null-terminated, causing fortified string functions to read beyond allocated buffer boundaries.

Is CVE-2021-47458 being actively exploited?

No, CVE-2021-47458 is not listed as actively exploited in the CISA Known Exploited Vulnerabilities catalog, and no public exploits are known to exist.

What versions of Kernel are affected by CVE-2021-47458?

Linux kernel versions 5.11 through 5.14.14 are affected when compiled with CONFIG_FORTIFY_SOURCE enabled.

How do I check if my server is vulnerable to CVE-2021-47458?

Run: uname -r to check your kernel version (if between 5.11-5.14.14), then verify CONFIG_FORTIFY_SOURCE is enabled with: cat /boot/config-$(uname -r) | grep CONFIG_FORTIFY_SOURCE

Does Defensia detect CVE-2021-47458?

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-2021-47458 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-39462CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: clk: bcm: dvp: Assign ->num before accessing ->hws Commit f316cdff8d67 ("clk: Annotate struct clk_hw_onecell_data with __counted_by") annotated the hws member of 'struct clk_hw_onecell_data' with __counted_by, which informs the bounds sanitizer about the number of elements in hws, so that it can warn when hws is accessed out of bounds. As noted in that change, the __counted_by member must be initialized with the number of elements before the first array access happens, otherwise there will be a warning from each access prior to the initialization because the number of elements is zero. This occurs in clk_dvp_probe() due to ->num being assigned after ->hws has been accessed: UBSAN: array-index-out-of-bounds in drivers/clk/bcm/clk-bcm2711-dvp.c:59:2 index 0 is out of range for type 'struct clk_hw *[] __counted_by(num)' (aka 'struct clk_hw *[]') Move the ->num initialization to before the first access of ->hws, which clears up the warning.
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-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-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-2021-47458. Free for 1 server.

Get started free