Vulnerabilities

Concrete CMS below 9.5.2 is vulnerable to PHP Object Injection via unserialize() calls in the Workflow, Form block, and File/Set components that lack the allowed_classes restriction. An unauthenticated attacker may trigger arbitrary PHP object instantiation if a malicious serialized payload has been placed in the database. Thanks XananasX7 and Sanjorn Keeratirungsan (dizconnect) for both independently reporting. The Concrete CMS security team gave this vulnerability a CVSS v.4.0 score of 8.4 with vector CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N.

Cross Site Scripting vulnerability in Koha 25.11 and before allows a remote attacker to execute arbitrary code via file upload function in Invoice features

Koha versions up to 25.11 contain a Server-Side Request Forgery (SSRF) vulnerability via the Z39.50/SRU server configuration. This allows authenticated attackers to perform internal network scanning and identify running services by analyzing server response times.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> coresight: tmc-etr: Fix race condition between sysfs and perf mode<br /> <br /> When trying to run perf and sysfs mode simultaneously, the WARN_ON()<br /> in tmc_etr_enable_hw() is triggered sometimes:<br /> <br /> WARNING: CPU: 42 PID: 3911571 at drivers/hwtracing/coresight/coresight-tmc-etr.c:1060 tmc_etr_enable_hw+0xc0/0xd8 [coresight_tmc]<br /> [..snip..]<br /> Call trace:<br /> tmc_etr_enable_hw+0xc0/0xd8 [coresight_tmc] (P)<br /> tmc_enable_etr_sink+0x11c/0x250 [coresight_tmc] (L)<br /> tmc_enable_etr_sink+0x11c/0x250 [coresight_tmc]<br /> coresight_enable_path+0x1c8/0x218 [coresight]<br /> coresight_enable_sysfs+0xa4/0x228 [coresight]<br /> enable_source_store+0x58/0xa8 [coresight]<br /> dev_attr_store+0x20/0x40<br /> sysfs_kf_write+0x4c/0x68<br /> kernfs_fop_write_iter+0x120/0x1b8<br /> vfs_write+0x2c8/0x388<br /> ksys_write+0x74/0x108<br /> __arm64_sys_write+0x24/0x38<br /> el0_svc_common.constprop.0+0x64/0x148<br /> do_el0_svc+0x24/0x38<br /> el0_svc+0x3c/0x130<br /> el0t_64_sync_handler+0xc8/0xd0<br /> el0t_64_sync+0x1ac/0x1b0<br /> ---[ end trace 0000000000000000 ]---<br /> <br /> Since the enablement of sysfs mode is separeted into two critical regions,<br /> one for sysfs buffer allocation and another for hardware enablement, it&amp;#39;s<br /> possible to race with the perf mode. Fix this by double check whether<br /> the perf mode&amp;#39;s been used before enabling the hardware in sysfs mode.<br /> <br /> mode:<br /> [sysfs mode] [perf mode]<br /> tmc_etr_get_sysfs_buffer()<br /> spin_lock(&amp;drvdata-&gt;spinlock)<br /> [sysfs buffer allocation]<br /> spin_unlock(&amp;drvdata-&gt;spinlock)<br /> spin_lock(&amp;drvdata-&gt;spinlock)<br /> tmc_etr_enable_hw()<br /> drvdata-&gt;etr_buf = etr_perf-&gt;etr_buf<br /> spin_unlock(&amp;drvdata-&gt;spinlock)<br /> spin_lock(&amp;drvdata-&gt;spinlock)<br /> tmc_etr_enable_hw()<br /> WARN_ON(drvdata-&gt;etr_buf) // WARN sicne etr_buf initialized at<br /> the perf side<br /> spin_unlock(&amp;drvdata-&gt;spinlock)<br /> <br /> With this fix, we retain the check for CS_MODE_PERF in get_etr_sysfs_buf.<br /> This ensures we verify whether the perf mode&amp;#39;s already running before we<br /> actually allocate the buffer. Then we can save the time of<br /> allocating/freeing the sysfs buffer if race with the perf mode.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> ibmveth: Disable GSO for packets with small MSS<br /> <br /> Some physical adapters on Power systems do not support segmentation<br /> offload when the MSS is less than 224 bytes. Attempting to send such<br /> packets causes the adapter to freeze, stopping all traffic until<br /> manually reset.<br /> <br /> Implement ndo_features_check to disable GSO for packets with small MSS<br /> values. The network stack will perform software segmentation instead.<br /> <br /> The 224-byte minimum matches ibmvnic<br /> commit ("ibmvnic: Enforce stronger sanity checks<br /> on GSO packets")<br /> which uses the same physical adapters in SEA configurations.<br /> <br /> The issue occurs specifically when the hardware attempts to perform<br /> segmentation (gso_segs &gt; 1) with a small MSS. Single-segment GSO packets<br /> (gso_segs == 1) do not trigger the problematic LSO code path and are<br /> transmitted normally without segmentation.<br /> <br /> Add an ndo_features_check callback to disable GSO when MSS

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> RDMA/hns: Fix WQ_MEM_RECLAIM warning<br /> <br /> When sunrpc is used, if a reset triggered, our wq may lead the<br /> following trace:<br /> <br /> workqueue: WQ_MEM_RECLAIM xprtiod:xprt_rdma_connect_worker [rpcrdma]<br /> is flushing !WQ_MEM_RECLAIM hns_roce_irq_workq:flush_work_handle<br /> [hns_roce_hw_v2]<br /> WARNING: CPU: 0 PID: 8250 at kernel/workqueue.c:2644 check_flush_dependency+0xe0/0x144<br /> Call trace:<br /> check_flush_dependency+0xe0/0x144<br /> start_flush_work.constprop.0+0x1d0/0x2f0<br /> __flush_work.isra.0+0x40/0xb0<br /> flush_work+0x14/0x30<br /> hns_roce_v2_destroy_qp+0xac/0x1e0 [hns_roce_hw_v2]<br /> ib_destroy_qp_user+0x9c/0x2b4<br /> rdma_destroy_qp+0x34/0xb0<br /> rpcrdma_ep_destroy+0x28/0xcc [rpcrdma]<br /> rpcrdma_ep_put+0x74/0xb4 [rpcrdma]<br /> rpcrdma_xprt_disconnect+0x1d8/0x260 [rpcrdma]<br /> xprt_rdma_connect_worker+0xc0/0x120 [rpcrdma]<br /> process_one_work+0x1cc/0x4d0<br /> worker_thread+0x154/0x414<br /> kthread+0x104/0x144<br /> ret_from_fork+0x10/0x18<br /> <br /> Since QP destruction frees memory, this wq should have the WQ_MEM_RECLAIM.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP<br /> <br /> Yizhou Zhao reported that simply having one RAW socket on protocol<br /> IPPROTO_RAW (255) was dangerous.<br /> <br /> socket(AF_INET, SOCK_RAW, 255);<br /> <br /> A malicious incoming ICMP packet can set the protocol field to 255<br /> and match this socket, leading to FNHE cache changes.<br /> <br /> inner = IP(src="192.168.2.1", dst="8.8.8.8", proto=255)/Raw("TEST")<br /> pkt = IP(src="192.168.1.1", dst="192.168.2.1")/ICMP(type=3, code=4, nexthopmtu=576)/inner<br /> <br /> "man 7 raw" states:<br /> <br /> A protocol of IPPROTO_RAW implies enabled IP_HDRINCL and is able<br /> to send any IP protocol that is specified in the passed header.<br /> Receiving of all IP protocols via IPPROTO_RAW is not possible<br /> using raw sockets.<br /> <br /> Make sure we drop these malicious packets.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> nfc: hci: shdlc: Stop timers and work before freeing context<br /> <br /> llc_shdlc_deinit() purges SHDLC skb queues and frees the llc_shdlc<br /> structure while its timers and state machine work may still be active.<br /> <br /> Timer callbacks can schedule sm_work, and sm_work accesses SHDLC state<br /> and the skb queues. If teardown happens in parallel with a queued/running<br /> work item, it can lead to UAF and other shutdown races.<br /> <br /> Stop all SHDLC timers and cancel sm_work synchronously before purging the<br /> queues and freeing the context.<br /> <br /> Found by Linux Verification Center (linuxtesting.org) with SVACE.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> PCI/P2PDMA: Fix p2pmem_alloc_mmap() warning condition<br /> <br /> Commit b7e282378773 has already changed the initial page refcount of<br /> p2pdma page from one to zero, however, in p2pmem_alloc_mmap() it uses<br /> "VM_WARN_ON_ONCE_PAGE(!page_ref_count(page))" to assert the initial page<br /> refcount should not be zero and the following will be reported when<br /> CONFIG_DEBUG_VM is enabled:<br /> <br /> page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x380400000<br /> flags: 0x20000000002000(reserved|node=0|zone=4)<br /> raw: 0020000000002000 ff1100015e3ab440 0000000000000000 0000000000000000<br /> raw: 0000000000000000 0000000000000000 00000000ffffffff 0000000000000000<br /> page dumped because: VM_WARN_ON_ONCE_PAGE(!page_ref_count(page))<br /> ------------[ cut here ]------------<br /> WARNING: CPU: 5 PID: 449 at drivers/pci/p2pdma.c:240 p2pmem_alloc_mmap+0x83a/0xa60<br /> <br /> Fix by using "page_ref_count(page)" as the assertion condition.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> pinctrl: canaan: k230: Fix NULL pointer dereference when parsing devicetree<br /> <br /> When probing the k230 pinctrl driver, the kernel triggers a NULL pointer<br /> dereference. The crash trace showed:<br /> [ 0.732084] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000068<br /> [ 0.740737] ...<br /> [ 0.776296] epc : k230_pinctrl_probe+0x1be/0x4fc<br /> <br /> In k230_pinctrl_parse_functions(), we attempt to retrieve the device<br /> pointer via info-&gt;pctl_dev-&gt;dev, but info-&gt;pctl_dev is only initialized<br /> after k230_pinctrl_parse_dt() completes.<br /> <br /> At the time of DT parsing, info-&gt;pctl_dev is still NULL, leading to<br /> the invalid dereference of info-&gt;pctl_dev-&gt;dev.<br /> <br /> Use the already available device pointer from platform_device<br /> instead of accessing through uninitialized pctl_dev.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> power: supply: rt9455: Fix use-after-free in power_supply_changed()<br /> <br /> Using the `devm_` variant for requesting IRQ _before_ the `devm_`<br /> variant for allocating/registering the `power_supply` handle, means that<br /> the `power_supply` handle will be deallocated/unregistered _before_ the<br /> interrupt handler (since `devm_` naturally deallocates in reverse<br /> allocation order). This means that during removal, there is a race<br /> condition where an interrupt can fire just _after_ the `power_supply`<br /> handle has been freed, *but* just _before_ the corresponding<br /> unregistration of the IRQ handler has run.<br /> <br /> This will lead to the IRQ handler calling `power_supply_changed()` with<br /> a freed `power_supply` handle. Which usually crashes the system or<br /> otherwise silently corrupts the memory...<br /> <br /> Note that there is a similar situation which can also happen during<br /> `probe()`; the possibility of an interrupt firing _before_ registering<br /> the `power_supply` handle. This would then lead to the nasty situation<br /> of using the `power_supply` handle *uninitialized* in<br /> `power_supply_changed()`.<br /> <br /> Fix this racy use-after-free by making sure the IRQ is requested _after_<br /> the registration of the `power_supply` handle.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> wifi: ath12k: do WoW offloads only on primary link<br /> <br /> In case of multi-link connection, WCN7850 firmware crashes due to WoW<br /> offloads enabled on both primary and secondary links.<br /> <br /> Change to do it only on primary link to fix it.<br /> <br /> Tested-on: WCN7850 hw2.0 PCI WLAN.HMT.1.1.c5-00284-QCAHMTSWPL_V1.0_V2.0_SILICONZ-1