high CVSS 7.8

CVE-2022-48712·Kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: ext4: fix error handling in ext4_fc_record_modified_inode() Current code does not fully takes care of krealloc() error case, which could lead to silent memory corruption or a kernel bug. This patch fixes that. Also it cleans up some duplicated error handling logic from various functions in fast_commit.c file.

Severity
high
Software
Kernel
Fixed in
5.16.8
Published
2024-06-20

Affected versions

From: 5.16

Until: 5.16.8

Fixed in: 5.16.8

How to fix this CVE

Update the Linux kernel to version 5.16.8 or later to fix a memory corruption issue in the ext4 fast commit error handling routine. This vulnerability affects systems running kernel versions 5.16 through 5.16.7 where improper krealloc() error handling could lead to kernel instability or data corruption. Apply the security update immediately through your distribution's package manager.

sudo dnf update kernel kernel-devel

Defensia detects this vulnerability

How to check if you are affected

  1. Step 1: Check current kernel version with `uname -r` and verify it is 5.16.8 or newer
  2. Step 2: Confirm ext4 filesystem is in use with `mount | grep ext4` to identify vulnerable mount points
  3. Step 3: Search kernel logs for ext4 fast commit errors using `dmesg | grep -i 'ext4\|fast_commit\|krealloc'`
  4. Step 4: After patching, reboot and confirm new kernel version with `uname -r`, then verify no ext4 corruption warnings appear in `dmesg`

FAQ

What is CVE-2022-48712?

This vulnerability involves improper error handling in the Linux kernel's ext4 fast commit feature, specifically in the ext4_fc_record_modified_inode() function where failed memory reallocation could result in silent memory corruption or kernel crashes.

Is CVE-2022-48712 being actively exploited?

No, this vulnerability is not listed on the CISA KEV catalog and has no known public exploits. However, it poses a stability risk that warrants prompt patching.

What versions of Kernel are affected by CVE-2022-48712?

Kernel versions 5.16.0 through 5.16.7 are vulnerable; version 5.16.8 and later contain the fix.

How do I check if my server is vulnerable to CVE-2022-48712?

Run `uname -r` and compare the output against the vulnerable range 5.16.0-5.16.7; if your version falls within this range and uses ext4 filesystems, your system is vulnerable.

Does Defensia detect CVE-2022-48712?

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

Get started free