high CVSS 7.8

CVE-2022-48801·Kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: iio: buffer: Fix file related error handling in IIO_BUFFER_GET_FD_IOCTL If we fail to copy the just created file descriptor to userland, we try to clean up by putting back 'fd' and freeing 'ib'. The code uses put_unused_fd() for the former which is wrong, as the file descriptor was already published by fd_install() which gets called internally by anon_inode_getfd(). This makes the error handling code leaving a half cleaned up file descriptor table around and a partially destructed 'file' object, allowing userland to play use-after-free tricks on us, by abusing the still usable fd and making the code operate on a dangling 'file->private_data' pointer. Instead of leaving the kernel in a partially corrupted state, don't attempt to explicitly clean up and leave this to the process exit path that'll release any still valid fds, including the one created by the previous call to anon_inode_getfd(). Simply return -EFAULT to indicate the error.

Severity
high
Software
Kernel
Fixed in
5.16.10
Published
2024-07-16

Affected versions

From: 5.16

Until: 5.16.10

Fixed in: 5.16.10

How to fix this CVE

Update your Linux kernel to version 5.16.10 or later to fix improper file descriptor cleanup in the IIO buffer subsystem. This vulnerability allows local users to trigger use-after-free conditions when the kernel fails to properly handle file descriptor creation errors. Prioritize patching systems where unprivileged users have local access, as exploitation requires local privilege level access.

sudo dnf update kernel kernel-devel

Defensia detects this vulnerability

How to check if you are affected

  1. Check current kernel version with: uname -r — compare output against vulnerable range 5.16.0 through 5.16.9
  2. Verify IIO subsystem is loaded with: lsmod | grep industrialio — if output is empty, the vulnerable component is not active
  3. Search kernel logs for IIO buffer errors with: sudo dmesg | grep -i 'iio.*buffer' or sudo journalctl -k | grep -i 'iio.*buffer'
  4. Confirm patch application by checking kernel build date with: uname -v — verify it matches or exceeds the fixed version timestamp from kernel.org

FAQ

What is CVE-2022-48801?

CVE-2022-48801 is a use-after-free vulnerability in the Linux kernel's Industrial I/O (IIO) buffer subsystem where improper error handling during file descriptor creation leaves the kernel in a partially corrupted state, potentially allowing local attackers to manipulate dangling file pointers.

Is CVE-2022-48801 being actively exploited?

No, CVE-2022-48801 is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are currently available, though the vulnerability's nature makes it a concern for systems with untrusted local users.

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

Linux kernel versions 5.16.0 through 5.16.9 are vulnerable; the fix was included in kernel 5.16.10 and later stable releases.

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

Run 'uname -r' and check if the output shows a kernel version between 5.16.0 and 5.16.9 inclusive. Additionally, verify the IIO subsystem is enabled with 'grep CONFIG_IIO /boot/config-$(uname -r)' — if it returns 'y' or 'm', your system is potentially vulnerable.

Does Defensia detect CVE-2022-48801?

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-2022-48801 will appear in your dashboard with remediation steps.

Related Kernel CVEs

CVE-2026-64439CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: crypto: krb5 - filter out async aead implementations at alloc krb5_aead_encrypt(), krb5_aead_decrypt() in rfc3961_simplified.c and rfc8009_encrypt(), rfc8009_decrypt() in rfc8009_aes2.c set a NULL completion callback and treat any negative return from crypto_aead_{encrypt,decrypt}() as terminal, falling through to kfree_sensitive(buffer). When the encrypt_name resolves to an async AEAD instance the request returns -EINPROGRESS, the buffer is freed while the backend's worker still holds a pointer, and the worker dereferences the freed slab on completion. KASAN report under UML+SLUB with a synthetic async aead backend bound to krb5->encrypt_name: BUG: KASAN: slab-use-after-free in t5_stub_complete+0x7d/0xc7 The helpers were written synchronously, so filter the async instances out at allocation time instead of plumbing crypto_wait_req() through every call site. Reachable via net/rxrpc/rxgk.c, fs/afs/cm_security.c and net/ceph/crypto.c on systems with an async AEAD provider bound to the krb5 enctype name.
CVE-2026-100075CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: RDMA/srpt: Fix srpt_alloc_rw_ctxs() unwind counters When srpt_alloc_rw_ctxs() fails partway through a multi-buffer indirect descriptor, the unwind path destroys RDMA contexts but leaves stale n_rw_ctx and n_rdma values (and a dangling rw_ctxs pointer). Later sq_wr_avail accounting in srpt_queue_response() or srpt_write_pending() can then subtract the wrong number of send queue credits. Reset the counters and clear rw_ctxs after freeing the heap allocation before returning an error.
CVE-2026-64383CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: smb: client: fix double-free in SMB2_flush() replay SMB2_flush() keeps its response buffer bookkeeping across replay attempts. If a replayable flush response is received and the retry then fails before cifs_send_recv() stores a replacement response, flush_exit will free the stale response pointer a second time. Reinitialize resp_buftype and rsp_iov at the top of the replay loop so cleanup only acts on response state produced by the current attempt. This fixes a double-free without changing replay handling for successful requests.
CVE-2026-64385CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: smb: client: fix double-free in SMB2_ioctl() replay A response-bearing attempt can return a replayable error and free its response buffer. If SMB2_ioctl_init() fails before the next send, cleanup retains the previous buffer type and frees that response again. Reset response bookkeeping before each attempt to prevent the stale free.
CVE-2026-64384CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: smb: client: fix change notify replay double-free A response-bearing attempt can return a replayable error and free its response buffer. If SMB2_notify_init() fails before the next send, cleanup retains the previous buffer type and frees that response again. Reset response bookkeeping before each attempt to prevent the stale free.

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

Get started free