In the Linux kernel, the following vulnerability has been resolved: i2c: i801: Fix block process call transactions According to the Intel datasheets, software must reset the block buffer index twice for block process call transactions: once before writing the outgoing data to the buffer, and once again before reading the incoming data from the buffer. The driver is currently missing the second reset, causing the wrong portion of the block buffer to be read.

The remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2024:2394 advisory.

  - kernel: Bluetooth BR/EDR PIN Pairing procedure is vulnerable to an impersonation attack (CVE-2020-26555)

  - kernel: memcg does not limit the number of POSIX file locks allowing memory exhaustion (CVE-2022-0480)

  - kernel: vmwgfx: NULL pointer dereference in vmw_cmd_dx_define_query (CVE-2022-38096)

  - kernel: integer overflow in l2cap_config_req() in net/bluetooth/l2cap_core.c (CVE-2022-45934)

  - kernel: use after free in vcs_read in drivers/tty/vt/vc_screen.c due to race (CVE-2023-3567)

  - kernel: cxgb4: use-after-free in ch_flower_stats_cb() (CVE-2023-4133)

  - kernel: netfilter: nf_tables: out-of-bounds access in nf_tables_newtable() (CVE-2023-6040)

  - kernel: NVMe: info leak due to out-of-bounds read in nvmet_ctrl_find_get (CVE-2023-6121)

  - kernel: local dos vulnerability in scatterwalk_copychunks (CVE-2023-6176)

  - kernel: GC's deletion of an SKB races with unix_stream_read_generic()  leading to UAF (CVE-2023-6531)

  - kernel: GSM multiplexing race condition leads to privilege escalation (CVE-2023-6546)

  - kernel: null pointer dereference vulnerability in nft_dynset_init() (CVE-2023-6622)

  - kernel: Null Pointer Dereference vulnerability in ida_free in lib/idr.c (CVE-2023-6915)

  - kernel: Out of boundary write in perf_read_group() as result of overflow a perf_event's read_size     (CVE-2023-6931)

  - kernel: use-after-free in IPv4 IGMP (CVE-2023-6932)

  - kernel: Bluetooth Forward and Future Secrecy Attacks and Defenses (CVE-2023-24023)

  - kernel: irdma: Improper access control (CVE-2023-25775)

  - Kernel: double free in hci_conn_cleanup of the bluetooth subsystem (CVE-2023-28464)

  - kernel: Bluetooth: HCI: global out-of-bounds access in net/bluetooth/hci_sync.c (CVE-2023-28866)

  - kernel: race condition between HCIUARTSETPROTO and HCIUARTGETPROTO in hci_uart_tty_ioctl (CVE-2023-31083)

  - kernel: usb: out-of-bounds read in read_descriptors (CVE-2023-37453)

  - kernel: netfilter: nftables out-of-bounds read in nf_osf_match_one() (CVE-2023-39189)

  - kernel: netfilter: xtables sctp out-of-bounds read in match_flags() (CVE-2023-39193)

  - kernel: xfrm: out-of-bounds read in __xfrm_state_filter_match() (CVE-2023-39194)

  - kernel: QXL: race condition leading to use-after-free in qxl_mode_dumb_create() (CVE-2023-39198)

  - kernel: ipv4: NULL pointer dereference in ipv4_send_dest_unreach() (CVE-2023-42754)

  - kernel: netfilter: race condition between IPSET_CMD_ADD and IPSET_CMD_SWAP (CVE-2023-42756)

  - kernel: lib/kobject.c vulnerable to fill_kobj_path out-of-bounds write (CVE-2023-45863)

  - kernel: NULL pointer dereference vulnerability in io_uring_show_fdinfo (CVE-2023-46862)

  - kernel: use-after-free during a race condition between a nonblocking atomic commit and a driver unload in     drivers/gpu/drm/drm_atomic.c (CVE-2023-51043)

  - kernel: bluetooth: bt_sock_ioctl race condition leads to use-after-free in bt_sock_recvmsg     (CVE-2023-51779)

  - kernel: use-after-free in net/atm/ioctl.c (CVE-2023-51780)

  - kernel: smb: client: fix potential OOBs in smb2_parse_contexts() (CVE-2023-52434)

  - kernel: gfs2: Fix kernel NULL pointer dereference in gfs2_rgrp_dump (CVE-2023-52448)

  - kernel: perf/x86/lbr: Filter vsyscall addresses (CVE-2023-52476)

  - kernel: mm/sparsemem: fix race in accessing memory_section->usage (CVE-2023-52489)

  - kernel: net: fix possible store tearing in neigh_periodic_work() (CVE-2023-52522)

  - kernel: HID: sony: Fix a potential memory leak in sony_probe() (CVE-2023-52529)

  - kernel: team: NULL pointer dereference when team device type is changed (CVE-2023-52574)

  - kernel: net: bridge: data races indata-races in br_handle_frame_finish() (CVE-2023-52578)

  - kernel: net/core: kernel crash in ETH_P_1588 flow dissector (CVE-2023-52580)

  - kernel: netfilter: nf_tables: memory leak when more than 255 elements expired (CVE-2023-52581)

  - kernel: net/sched: act_ct: fix skb leak and crash on ooo frags (CVE-2023-52610)

  - kernel: netfilter: nf_tables: disallow timeout for anonymous sets (CVE-2023-52620)

  - kernel: CIFS Filesystem Decryption Improper Input Validation Remote Code Execution Vulnerability in     function receive_encrypted_standard of client (CVE-2024-0565)

  - kernel: hugetlbfs: Null pointer dereference in hugetlbfs_fill_super function (CVE-2024-0841)

  - kernel: nf_tables: use-after-free vulnerability in the nft_setelem_catchall_deactivate() function     (CVE-2024-1085)

  - kernel: nf_tables: use-after-free vulnerability in the nft_verdict_init() function (CVE-2024-1086)

  - kernel: tls: use-after-free with partial reads and async decrypt (CVE-2024-26582)

  - kernel: tls: race between async notify and socket close (CVE-2024-26583)

  - kernel: tls: handle backlogging of crypto requests (CVE-2024-26584)

  - kernel: tls: race between tx work scheduling and socket close (CVE-2024-26585)

  - kernel: mlxsw: spectrum_acl_tcam: Fix stack corruption (CVE-2024-26586)

  - kernel: i2c: i801: Fix block process call transactions (CVE-2024-26593)

  - kernel: sched/membarrier: reduce the ability to hammer on sys_membarrier (CVE-2024-26602)

  - kernel: netfilter: nf_tables: reject QUEUE/DROP verdict parameters (CVE-2024-26609)

  - kernel: ip6_tunnel: fix NEXTHDR_FRAGMENT handling in ip6_tnl_parse_tlv_enc_lim() (CVE-2024-26633)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote CentOS Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the kernel-5.14.0-432.el9 build changelog.

  - In the Linux kernel, the following vulnerability has been resolved: i2c: Fix a potential use after free     Free the adap structure only after we are done using it. This patch just moves the put_device() down a bit     to avoid the use after free. [wsa: added comment to the code, added Fixes tag] (CVE-2019-25162)

  - In the Linux kernel, the following vulnerability has been resolved: powerpc/mm: Fix null-pointer     dereference in pgtable_cache_add kasprintf() returns a pointer to dynamically allocated memory which can     be NULL upon failure. Ensure the allocation was successful by checking the pointer validity.
    (CVE-2023-52607)

  - In the Linux kernel, the following vulnerability has been resolved: i2c: i801: Fix block process call     transactions According to the Intel datasheets, software must reset the block buffer index twice for block     process call transactions: once before writing the outgoing data to the buffer, and once again before     reading the incoming data from the buffer. The driver is currently missing the second reset, causing the     wrong portion of the block buffer to be read. (CVE-2024-26593)

  - In the Linux kernel, the following vulnerability has been resolved: sched/membarrier: reduce the ability     to hammer on sys_membarrier On some systems, sys_membarrier can be very expensive, causing overall     slowdowns for everything. So put a lock on the path in order to serialize the accesses to prevent the     ability for this to be called at too high of a frequency and saturate the machine. (CVE-2024-26602)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Fedora 38 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2024-71f0f16533 advisory.

  - Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
    (CVE-2023-52437)

  - In the Linux kernel, the following vulnerability has been resolved: tls: fix race between tx work     scheduling and socket close Similarly to previous commit, the submitting thread (recvmsg/sendmsg) may exit     as soon as the async crypto handler calls complete(). Reorder scheduling the work before calling     complete(). This seems more logical in the first place, as it's the inverse order of what the submitting     thread will do. (CVE-2024-26585)

  - In the Linux kernel, the following vulnerability has been resolved: net: tls: fix use-after-free with     partial reads and async decrypt tls_decrypt_sg doesn't take a reference on the pages from clear_skb, so     the put_page() in tls_decrypt_done releases them, and we trigger a use-after-free in process_rx_list when     we try to read from the partially-read skb. (CVE-2024-26582)

  - In the Linux kernel, the following vulnerability has been resolved: net: tls: handle backlogging of crypto     requests Since we're setting the CRYPTO_TFM_REQ_MAY_BACKLOG flag on our requests to the crypto API,     crypto_aead_{encrypt,decrypt} can return -EBUSY instead of -EINPROGRESS in valid situations. For example,     when the cryptd queue for AESNI is full (easy to trigger with an artificially low     cryptd.cryptd_max_cpu_qlen), requests will be enqueued to the backlog but still processed. In that case,     the async callback will also be called twice: first with err == -EINPROGRESS, which it seems we can just     ignore, then with err == 0. Compared to Sabrina's original patch this version uses the new     tls_*crypt_async_wait() helpers and converts the EBUSY to EINPROGRESS to avoid having to modify all the     error handling paths. The handling is identical. (CVE-2024-26584)

  - In the Linux kernel, the following vulnerability has been resolved: tls: fix race between async notify and     socket close The submitting thread (one which called recvmsg/sendmsg) may exit as soon as the async crypto     handler calls complete() so any code past that point risks touching already freed data. Try to avoid the     locking and extra flags altogether. Have the main thread hold an extra reference, this way we can depend     solely on the atomic ref counter for synchronization. Don't futz with reiniting the completion, either, we     are now tightly controlling when completion fires. (CVE-2024-26583)

  - In the Linux kernel, the following vulnerability has been resolved: i2c: i801: Fix block process call     transactions According to the Intel datasheets, software must reset the block buffer index twice for block     process call transactions: once before writing the outgoing data to the buffer, and once again before     reading the incoming data from the buffer. The driver is currently missing the second reset, causing the     wrong portion of the block buffer to be read. (CVE-2024-26593)

  - In the Linux kernel, the following vulnerability has been resolved: x86/fpu: Stop relying on userspace for     info to fault in xsave buffer Before this change, the expected size of the user space buffer was taken     from fx_sw->xstate_size. fx_sw->xstate_size can be changed from user-space, so it is possible construct a     sigreturn frame where: * fx_sw->xstate_size is smaller than the size required by valid bits in     fx_sw->xfeatures. * user-space unmaps parts of the sigrame fpu buffer so that not all of the buffer     required by xrstor is accessible. In this case, xrstor tries to restore and accesses the unmapped area     which results in a fault. But fault_in_readable succeeds because buf + fx_sw->xstate_size is within the     still mapped area, so it goes back and tries xrstor again. It will spin in this loop forever. Instead,     fault in the maximum size which can be touched by XRSTOR (taken from fpstate->user_size). [ dhansen: tweak     subject / changelog ] (CVE-2024-26603)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Fedora 39 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2024-d16d94b00d advisory.

  - In btrfs_get_root_ref in fs/btrfs/disk-io.c in the Linux kernel through 6.7.1, there can be an assertion     failure and crash because a subvolume can be read out too soon after its root item is inserted upon     subvolume creation. (CVE-2024-23850)

  - copy_params in drivers/md/dm-ioctl.c in the Linux kernel through 6.7.1 can attempt to allocate more than     INT_MAX bytes, and crash, because of a missing param_kernel->data_size check. This is related to     ctl_ioctl. (CVE-2024-23851)

  - Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
    (CVE-2023-52437)

  - In the Linux kernel, the following vulnerability has been resolved: tls: fix race between tx work     scheduling and socket close Similarly to previous commit, the submitting thread (recvmsg/sendmsg) may exit     as soon as the async crypto handler calls complete(). Reorder scheduling the work before calling     complete(). This seems more logical in the first place, as it's the inverse order of what the submitting     thread will do. (CVE-2024-26585)

  - In the Linux kernel, the following vulnerability has been resolved: net: tls: fix use-after-free with     partial reads and async decrypt tls_decrypt_sg doesn't take a reference on the pages from clear_skb, so     the put_page() in tls_decrypt_done releases them, and we trigger a use-after-free in process_rx_list when     we try to read from the partially-read skb. (CVE-2024-26582)

  - In the Linux kernel, the following vulnerability has been resolved: net: tls: handle backlogging of crypto     requests Since we're setting the CRYPTO_TFM_REQ_MAY_BACKLOG flag on our requests to the crypto API,     crypto_aead_{encrypt,decrypt} can return -EBUSY instead of -EINPROGRESS in valid situations. For example,     when the cryptd queue for AESNI is full (easy to trigger with an artificially low     cryptd.cryptd_max_cpu_qlen), requests will be enqueued to the backlog but still processed. In that case,     the async callback will also be called twice: first with err == -EINPROGRESS, which it seems we can just     ignore, then with err == 0. Compared to Sabrina's original patch this version uses the new     tls_*crypt_async_wait() helpers and converts the EBUSY to EINPROGRESS to avoid having to modify all the     error handling paths. The handling is identical. (CVE-2024-26584)

  - In the Linux kernel, the following vulnerability has been resolved: tls: fix race between async notify and     socket close The submitting thread (one which called recvmsg/sendmsg) may exit as soon as the async crypto     handler calls complete() so any code past that point risks touching already freed data. Try to avoid the     locking and extra flags altogether. Have the main thread hold an extra reference, this way we can depend     solely on the atomic ref counter for synchronization. Don't futz with reiniting the completion, either, we     are now tightly controlling when completion fires. (CVE-2024-26583)

  - In the Linux kernel, the following vulnerability has been resolved: i2c: i801: Fix block process call     transactions According to the Intel datasheets, software must reset the block buffer index twice for block     process call transactions: once before writing the outgoing data to the buffer, and once again before     reading the incoming data from the buffer. The driver is currently missing the second reset, causing the     wrong portion of the block buffer to be read. (CVE-2024-26593)

  - In the Linux kernel, the following vulnerability has been resolved: x86/fpu: Stop relying on userspace for     info to fault in xsave buffer Before this change, the expected size of the user space buffer was taken     from fx_sw->xstate_size. fx_sw->xstate_size can be changed from user-space, so it is possible construct a     sigreturn frame where: * fx_sw->xstate_size is smaller than the size required by valid bits in     fx_sw->xfeatures. * user-space unmaps parts of the sigrame fpu buffer so that not all of the buffer     required by xrstor is accessible. In this case, xrstor tries to restore and accesses the unmapped area     which results in a fault. But fault_in_readable succeeds because buf + fx_sw->xstate_size is within the     still mapped area, so it goes back and tries xrstor again. It will spin in this loop forever. Instead,     fault in the maximum size which can be touched by XRSTOR (taken from fpstate->user_size). [ dhansen: tweak     subject / changelog ] (CVE-2024-26603)

  - In the Linux kernel, the following vulnerability has been resolved: Revert kobject: Remove redundant     checks for whether ktype is NULL This reverts commit 1b28cb81dab7c1eedc6034206f4e8d644046ad31. It is     reported to cause problems, so revert it for now until the root cause can be found. (CVE-2024-26604)

  - In the Linux kernel, the following vulnerability has been resolved: binder: signal epoll threads of self-     work In (e)poll mode, threads often depend on I/O events to determine when data is ready for consumption.
    Within binder, a thread may initiate a command via BINDER_WRITE_READ without a read buffer and then make     use of epoll_wait() or similar to consume any responses afterwards. It is then crucial that epoll threads     are signaled via wakeup when they queue their own work. Otherwise, they risk waiting indefinitely for an     event leaving their work unhandled. What is worse, subsequent commands won't trigger a wakeup either as     the thread has pending work. (CVE-2024-26606)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
197517	Ubuntu 20.04 LTS / 22.04 LTS : Linux kernel (AWS) vulnerabilities (USN-6766-3)	Nessus	Ubuntu Local Security Checks	high
197101	Ubuntu 20.04 LTS / 22.04 LTS : Linux kernel vulnerabilities (USN-6766-2)	Nessus	Ubuntu Local Security Checks	high
196947	Ubuntu 20.04 LTS : Linux kernel (BlueField) vulnerabilities (USN-6767-2)	Nessus	Ubuntu Local Security Checks	high
195135	Ubuntu 18.04 LTS / 20.04 LTS : Linux kernel vulnerabilities (USN-6767-1)	Nessus	Ubuntu Local Security Checks	high
195134	Ubuntu 20.04 LTS / 22.04 LTS : Linux kernel vulnerabilities (USN-6766-1)	Nessus	Ubuntu Local Security Checks	high
195036	Oracle Linux 9 : kernel (ELSA-2024-2394)	Nessus	Oracle Linux Local Security Checks	critical
195025	Debian dsa-5681 : affs-modules-5.10.0-29-4kc-malta-di - security update	Nessus	Debian Local Security Checks	high
194794	RHEL 9 : kernel (RHSA-2024:2394)	Nessus	Red Hat Local Security Checks	critical
193933	CentOS 9 : kernel-5.14.0-432.el9	Nessus	CentOS Local Security Checks	high
193309	Debian dsa-5658 : affs-modules-6.1.0-11-4kc-malta-di - security update	Nessus	Debian Local Security Checks	high
192490	SUSE SLES15 Security Update : kernel (SUSE-SU-2024:0977-1)	Nessus	SuSE Local Security Checks	high
192487	SUSE SLES15 Security Update : kernel (SUSE-SU-2024:0926-1)	Nessus	SuSE Local Security Checks	high
192180	SUSE SLES15 / openSUSE 15 Security Update : kernel (SUSE-SU-2024:0910-1)	Nessus	SuSE Local Security Checks	high
192178	SUSE SLES15 Security Update : kernel (SUSE-SU-2024:0900-2)	Nessus	SuSE Local Security Checks	high
192141	SUSE SLES15 Security Update : kernel (SUSE-SU-2024:0900-1)	Nessus	SuSE Local Security Checks	high
192014	SUSE SLES15 Security Update : kernel (SUSE-SU-2024:0857-1)	Nessus	SuSE Local Security Checks	high
192011	SUSE SLED15 / SLES15 / openSUSE 15 Security Update : kernel (SUSE-SU-2024:0858-1)	Nessus	SuSE Local Security Checks	high
192006	SUSE SLES15 / openSUSE 15 Security Update : kernel (SUSE-SU-2024:0855-1)	Nessus	SuSE Local Security Checks	high
191083	Fedora 38 : kernel (2024-71f0f16533)	Nessus	Fedora Local Security Checks	high
191082	Fedora 39 : kernel (2024-d16d94b00d)	Nessus	Fedora Local Security Checks	high

Detections

Analytics

CVE-2024-26593

high

Tenable Plugins

high

high

high

high

high

critical

high

critical

high

high

high

high

high

high

high

high

high

high

high

high