Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> enic: Validate length of nl attributes in enic_set_vf_port<br /> <br /> enic_set_vf_port assumes that the nl attribute IFLA_PORT_PROFILE<br /> is of length PORT_PROFILE_MAX and that the nl attributes<br /> IFLA_PORT_INSTANCE_UUID, IFLA_PORT_HOST_UUID are of length PORT_UUID_MAX.<br /> These attributes are validated (in the function do_setlink in rtnetlink.c)<br /> using the nla_policy ifla_port_policy. The policy defines IFLA_PORT_PROFILE<br /> as NLA_STRING, IFLA_PORT_INSTANCE_UUID as NLA_BINARY and<br /> IFLA_PORT_HOST_UUID as NLA_STRING. That means that the length validation<br /> using the policy is for the max size of the attributes and not on exact<br /> size so the length of these attributes might be less than the sizes that<br /> enic_set_vf_port expects. This might cause an out of bands<br /> read access in the memcpys of the data of these<br /> attributes in enic_set_vf_port.

Improper Input Validation vulnerability in ABB 800xA Base.<br /> An attacker who successfully exploited this <br /> vulnerability could cause services to crash by sending specifically crafted messages.<br /> This issue affects 800xA Base: from 6.0.0 through 6.1.1-2.

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/msm/dpu: Add callback function pointer check before its call<br /> <br /> In dpu_core_irq_callback_handler() callback function pointer is compared to NULL,<br /> but then callback function is unconditionally called by this pointer.<br /> Fix this bug by adding conditional return.<br /> <br /> Found by Linux Verification Center (linuxtesting.org) with SVACE.<br /> <br /> Patchwork: https://patchwork.freedesktop.org/patch/588237/

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> fs/ntfs3: Use variable length array instead of fixed size<br /> <br /> Should fix smatch warning:<br /> ntfs_set_label() error: __builtin_memcpy() &amp;#39;uni-&gt;name&amp;#39; too small (20 vs 256)

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> fs/ntfs3: Use 64 bit variable to avoid 32 bit overflow<br /> <br /> For example, in the expression:<br /> vbo = 2 * vbo + skip

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> fs/ntfs3: Check &amp;#39;folio&amp;#39; pointer for NULL<br /> <br /> It can be NULL if bmap is called.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> fuse: clear FR_SENT when re-adding requests into pending list<br /> <br /> The following warning was reported by lee bruce:<br /> <br /> ------------[ cut here ]------------<br /> WARNING: CPU: 0 PID: 8264 at fs/fuse/dev.c:300<br /> fuse_request_end+0x685/0x7e0 fs/fuse/dev.c:300<br /> Modules linked in:<br /> CPU: 0 PID: 8264 Comm: ab2 Not tainted 6.9.0-rc7<br /> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)<br /> RIP: 0010:fuse_request_end+0x685/0x7e0 fs/fuse/dev.c:300<br /> ......<br /> Call Trace:<br /> <br /> fuse_dev_do_read.constprop.0+0xd36/0x1dd0 fs/fuse/dev.c:1334<br /> fuse_dev_read+0x166/0x200 fs/fuse/dev.c:1367<br /> call_read_iter include/linux/fs.h:2104 [inline]<br /> new_sync_read fs/read_write.c:395 [inline]<br /> vfs_read+0x85b/0xba0 fs/read_write.c:476<br /> ksys_read+0x12f/0x260 fs/read_write.c:619<br /> do_syscall_x64 arch/x86/entry/common.c:52 [inline]<br /> do_syscall_64+0xce/0x260 arch/x86/entry/common.c:83<br /> entry_SYSCALL_64_after_hwframe+0x77/0x7f<br /> ......<br /> <br /> <br /> The warning is due to the FUSE_NOTIFY_RESEND notify sent by the write()<br /> syscall in the reproducer program and it happens as follows:<br /> <br /> (1) calls fuse_dev_read() to read the INIT request<br /> The read succeeds. During the read, bit FR_SENT will be set on the<br /> request.<br /> (2) calls fuse_dev_write() to send an USE_NOTIFY_RESEND notify<br /> The resend notify will resend all processing requests, so the INIT<br /> request is moved from processing list to pending list again.<br /> (3) calls fuse_dev_read() with an invalid output address<br /> fuse_dev_read() will try to copy the same INIT request to the output<br /> address, but it will fail due to the invalid address, so the INIT<br /> request is ended and triggers the warning in fuse_request_end().<br /> <br /> Fix it by clearing FR_SENT when re-adding requests into pending list.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> usb: gadget: u_audio: Fix race condition use of controls after free during gadget unbind.<br /> <br /> Hang on to the control IDs instead of pointers since those are correctly<br /> handled with locks.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> dmaengine: idxd: Avoid unnecessary destruction of file_ida<br /> <br /> file_ida is allocated during cdev open and is freed accordingly<br /> during cdev release. This sequence is guaranteed by driver file<br /> operations. Therefore, there is no need to destroy an already empty<br /> file_ida when the WQ cdev is removed.<br /> <br /> Worse, ida_free() in cdev release may happen after destruction of<br /> file_ida per WQ cdev. This can lead to accessing an id in file_ida<br /> after it has been destroyed, resulting in a kernel panic.<br /> <br /> Remove ida_destroy(&amp;file_ida) to address these issues.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> watchdog: cpu5wdt.c: Fix use-after-free bug caused by cpu5wdt_trigger<br /> <br /> When the cpu5wdt module is removing, the origin code uses del_timer() to<br /> de-activate the timer. If the timer handler is running, del_timer() could<br /> not stop it and will return directly. If the port region is released by<br /> release_region() and then the timer handler cpu5wdt_trigger() calls outb()<br /> to write into the region that is released, the use-after-free bug will<br /> happen.<br /> <br /> Change del_timer() to timer_shutdown_sync() in order that the timer handler<br /> could be finished before the port region is released.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> iio: adc: PAC1934: fix accessing out of bounds array index<br /> <br /> Fix accessing out of bounds array index for average<br /> current and voltage measurements. The device itself has<br /> only 4 channels, but in sysfs there are "fake"<br /> channels for the average voltages and currents too.