Vulnerabilities

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> amdkfd: properly free gang_ctx_bo when failed to init user queue<br /> <br /> The destructor of a gtt bo is declared as<br /> void amdgpu_amdkfd_free_gtt_mem(struct amdgpu_device *adev, void **mem_obj);<br /> Which takes void** as the second parameter.<br /> <br /> GCC allows passing void* to the function because void* can be implicitly<br /> casted to any other types, so it can pass compiling.<br /> <br /> However, passing this void* parameter into the function&amp;#39;s<br /> execution process(which expects void** and dereferencing void**)<br /> will result in errors.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> cpufreq/amd-pstate: Fix cpufreq_policy ref counting<br /> <br /> amd_pstate_update_limits() takes a cpufreq_policy reference but doesn&amp;#39;t<br /> decrement the refcount in one of the exit paths, fix that.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> thermal/netlink: Prevent userspace segmentation fault by adjusting UAPI header<br /> <br /> The intel-lpmd tool [1], which uses the THERMAL_GENL_ATTR_CPU_CAPABILITY<br /> attribute to receive HFI events from kernel space, encounters a<br /> segmentation fault after commit 1773572863c4 ("thermal: netlink: Add the<br /> commands and the events for the thresholds").<br /> <br /> The issue arises because the THERMAL_GENL_ATTR_CPU_CAPABILITY raw value<br /> was changed while intel_lpmd still uses the old value.<br /> <br /> Although intel_lpmd can be updated to check the THERMAL_GENL_VERSION and<br /> use the appropriate THERMAL_GENL_ATTR_CPU_CAPABILITY value, the commit<br /> itself is questionable.<br /> <br /> The commit introduced a new element in the middle of enum thermal_genl_attr,<br /> which affects many existing attributes and introduces potential risks<br /> and unnecessary maintenance burdens for userspace thermal netlink event<br /> users.<br /> <br /> Solve the issue by moving the newly introduced<br /> THERMAL_GENL_ATTR_TZ_PREV_TEMP attribute to the end of the<br /> enum thermal_genl_attr. This ensures that all existing thermal generic<br /> netlink attributes remain unaffected.<br /> <br /> [ rjw: Subject edits ]

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> drm/panthor: avoid garbage value in panthor_ioctl_dev_query()<br /> <br /> &amp;#39;priorities_info&amp;#39; is uninitialized, and the uninitialized value is copied<br /> to user object when calling PANTHOR_UOBJ_SET(). Using memset to initialize<br /> &amp;#39;priorities_info&amp;#39; to avoid this garbage value problem.

The Eventer - WordPress Event &amp; Booking Manager Plugin plugin for WordPress is vulnerable to SQL Injection via the reg_id parameter in all versions up to, and including, 3.9.9.2 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

The InWave Jobs plugin for WordPress is vulnerable to privilege escalation via password reset in all versions up to, and including, 3.5.1. This is due to the plugin not properly validating a user&amp;#39;s identity prior to updating their password. This makes it possible for unauthenticated attackers to change arbitrary user&amp;#39;s passwords, including administrators, and leverage that to gain access to their account.

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 /> usb: gadget: core: flush gadget workqueue after device removal<br /> <br /> device_del() can lead to new work being scheduled in gadget-&gt;work<br /> workqueue. This is observed, for example, with the dwc3 driver with the<br /> following call stack:<br /> device_del()<br /> gadget_unbind_driver()<br /> usb_gadget_disconnect_locked()<br /> dwc3_gadget_pullup()<br /> dwc3_gadget_soft_disconnect()<br /> usb_gadget_set_state()<br /> schedule_work(&amp;gadget-&gt;work)<br /> <br /> Move flush_work() after device_del() to ensure the workqueue is cleaned<br /> up.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> KVM: x86: Load DR6 with guest value only before entering .vcpu_run() loop<br /> <br /> Move the conditional loading of hardware DR6 with the guest&amp;#39;s DR6 value<br /> out of the core .vcpu_run() loop to fix a bug where KVM can load hardware<br /> with a stale vcpu-&gt;arch.dr6.<br /> <br /> When the guest accesses a DR and host userspace isn&amp;#39;t debugging the guest,<br /> KVM disables DR interception and loads the guest&amp;#39;s values into hardware on<br /> VM-Enter and saves them on VM-Exit. This allows the guest to access DRs<br /> at will, e.g. so that a sequence of DR accesses to configure a breakpoint<br /> only generates one VM-Exit.<br /> <br /> For DR0-DR3, the logic/behavior is identical between VMX and SVM, and also<br /> identical between KVM_DEBUGREG_BP_ENABLED (userspace debugging the guest)<br /> and KVM_DEBUGREG_WONT_EXIT (guest using DRs), and so KVM handles loading<br /> DR0-DR3 in common code, _outside_ of the core kvm_x86_ops.vcpu_run() loop.<br /> <br /> But for DR6, the guest&amp;#39;s value doesn&amp;#39;t need to be loaded into hardware for<br /> KVM_DEBUGREG_BP_ENABLED, and SVM provides a dedicated VMCB field whereas<br /> VMX requires software to manually load the guest value, and so loading the<br /> guest&amp;#39;s value into DR6 is handled by {svm,vmx}_vcpu_run(), i.e. is done<br /> _inside_ the core run loop.<br /> <br /> Unfortunately, saving the guest values on VM-Exit is initiated by common<br /> x86, again outside of the core run loop. If the guest modifies DR6 (in<br /> hardware, when DR interception is disabled), and then the next VM-Exit is<br /> a fastpath VM-Exit, KVM will reload hardware DR6 with vcpu-&gt;arch.dr6 and<br /> clobber the guest&amp;#39;s actual value.<br /> <br /> The bug shows up primarily with nested VMX because KVM handles the VMX<br /> preemption timer in the fastpath, and the window between hardware DR6<br /> being modified (in guest context) and DR6 being read by guest software is<br /> orders of magnitude larger in a nested setup. E.g. in non-nested, the<br /> VMX preemption timer would need to fire precisely between #DB injection<br /> and the #DB handler&amp;#39;s read of DR6, whereas with a KVM-on-KVM setup, the<br /> window where hardware DR6 is "dirty" extends all the way from L1 writing<br /> DR6 to VMRESUME (in L1).<br /> <br /> L1&amp;#39;s view:<br /> ==========<br /> <br /> CPU 0/KVM-7289 [023] d.... 2925.640961: kvm_entry: vcpu 0<br /> A: L1 Writes DR6<br /> CPU 0/KVM-7289 [023] d.... 2925.640963: : Set DRs, DR6 = 0xffff0ff1<br /> <br /> B: CPU 0/KVM-7289 [023] d.... 2925.640967: kvm_exit: vcpu 0 reason EXTERNAL_INTERRUPT intr_info 0x800000ec<br /> <br /> D: L1 reads DR6, arch.dr6 = 0<br /> CPU 0/KVM-7289 [023] d.... 2925.640969: : Sync DRs, DR6 = 0xffff0ff0<br /> <br /> CPU 0/KVM-7289 [023] d.... 2925.640976: kvm_entry: vcpu 0<br /> L2 reads DR6, L1 disables DR interception<br /> CPU 0/KVM-7289 [023] d.... 2925.640980: kvm_exit: vcpu 0 reason DR_ACCESS info1 0x0000000000000216<br /> CPU 0/KVM-7289 [023] d.... 2925.640983: kvm_entry: vcpu 0<br /> <br /> CPU 0/KVM-7289 [023] d.... 2925.640983: : Set DRs, DR6 = 0xffff0ff0<br /> <br /> L2 detects failure<br /> CPU 0/KVM-7289 [023] d.... 2925.640987: kvm_exit: vcpu 0 reason HLT<br /> L1 reads DR6 (confirms failure)<br /> CPU 0/KVM-7289 [023] d.... 2925.640990: : Sync DRs, DR6 = 0xffff0ff0<br /> <br /> L0&amp;#39;s view:<br /> ==========<br /> L2 reads DR6, arch.dr6 = 0<br /> CPU 23/KVM-5046 [001] d.... 3410.005610: kvm_exit: vcpu 23 reason DR_ACCESS info1 0x0000000000000216<br /> CPU 23/KVM-5046 [001] ..... 3410.005610: kvm_nested_vmexit: vcpu 23 reason DR_ACCESS info1 0x0000000000000216<br /> <br /> L2 =&gt; L1 nested VM-Exit<br /> CPU 23/KVM-5046 [001] ..... 3410.005610: kvm_nested_vmexit_inject: reason: DR_ACCESS ext_inf1: 0x0000000000000216<br /> <br /> CPU 23/KVM-5046 [001] d.... 3410.005610: kvm_entry: vcpu 23<br /> CPU 23/KVM-5046 [001] d.... 3410.005611: kvm_exit: vcpu 23 reason VMREAD<br /> CPU 23/KVM-5046 [001] d.... 3410.005611: kvm_entry: vcpu 23<br /> CPU 23/KVM-5046 [001] d.... 3410.<br /> ---truncated---

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> io_uring/kbuf: reallocate buf lists on upgrade<br /> <br /> IORING_REGISTER_PBUF_RING can reuse an old struct io_buffer_list if it<br /> was created for legacy selected buffer and has been emptied. It violates<br /> the requirement that most of the field should stay stable after publish.<br /> Always reallocate it instead.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> usb: gadget: f_midi: fix MIDI Streaming descriptor lengths<br /> <br /> While the MIDI jacks are configured correctly, and the MIDIStreaming<br /> endpoint descriptors are filled with the correct information,<br /> bNumEmbMIDIJack and bLength are set incorrectly in these descriptors.<br /> <br /> This does not matter when the numbers of in and out ports are equal, but<br /> when they differ the host will receive broken descriptors with<br /> uninitialized stack memory leaking into the descriptor for whichever<br /> value is smaller.<br /> <br /> The precise meaning of "in" and "out" in the port counts is not clearly<br /> defined and can be confusing. But elsewhere the driver consistently<br /> uses this to match the USB meaning of IN and OUT viewed from the host,<br /> so that "in" ports send data to the host and "out" ports receive data<br /> from it.

The School Management System for Wordpress plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the &amp;#39;mj_smgt_remove_feetype&amp;#39; and &amp;#39;mj_smgt_remove_category_new&amp;#39; AJAX actions in all versions up to, and including, 93.0.0. This makes it possible for unauthenticated attackers to delete arbitrary posts.