Showing 25 vulnerabilities on this page for SCALANCE XCM-/XRM-/XCH-/XRH-300 family

Signals CISA KEV Ransomware Nuclei
Siemens vulnerability results
VulnerabilityTitle and contextCVSSEPSSPoCsSignalsSTIX action

fs/proc: fix softlockup in __read_vmcore (part 2)

In the Linux kernel, the following vulnerability has been resolved: fs/proc: fix softlockup in __read_vmcore (part 2) Since commit 5cbcb62dddf5 ("fs/proc: fix softlockup in __read_vmcore") the number of softlockups in __read_vmcore at kdump time have gone down, but they still happen sometimes. In a memory constrained environment like the kdump image, a softlockup is not just a harmless message, but it can interfere with things like RCU freeing memory, causing the crashdump to get stuck. The

Feb 12, 2025
CVSS5.5v3.1EPSS0.238%PoCs0SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

hrtimers: Handle CPU state correctly on hotplug

In the Linux kernel, the following vulnerability has been resolved: hrtimers: Handle CPU state correctly on hotplug Consider a scenario where a CPU transitions from CPUHP_ONLINE to halfway through a CPU hotunplug down to CPUHP_HRTIMERS_PREPARE, and then back to CPUHP_ONLINE: Since hrtimers_prepare_cpu() does not run, cpu_base.hres_active remains set to 1 throughout. However, during a CPU unplug operation, the tick and the clockevents are shut down at CPUHP_AP_TICK_DYING. On return to the onli

CWE-416Feb 12, 2025
CVSS7.8v3.1EPSS0.233%PoCs0SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

net: sched: fix ets qdisc OOB Indexing

In the Linux kernel, the following vulnerability has been resolved: net: sched: fix ets qdisc OOB Indexing Haowei Yan <g1042620637@gmail.com> found that ets_class_from_arg() can index an Out-Of-Bound class in ets_class_from_arg() when passed clid of 0. The overflow may cause local privilege escalation. [ 18.852298] ------------[ cut here ]------------ [ 18.853271] UBSAN: array-index-out-of-bounds in net/sched/sch_ets.c:93:20 [ 18.853743] index 18446744073709551615 is out of range for

CWE-129Feb 10, 2025
CVSS7.8v3.1EPSS0.611%PoCs1SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

fs: Fix uninitialized value issue in from_kuid and from_kgid

In the Linux kernel, the following vulnerability has been resolved: fs: Fix uninitialized value issue in from_kuid and from_kgid ocfs2_setattr() uses attr->ia_mode, attr->ia_uid and attr->ia_gid in a trace point even though ATTR_MODE, ATTR_UID and ATTR_GID aren't set. Initialize all fields of newattrs to avoid uninitialized variables, by checking if ATTR_MODE, ATTR_UID, ATTR_GID are initialized, otherwise 0.

CWE-908Nov 25, 2024
CVSS5.5v3.1EPSS0.248%PoCs0SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

wifi: iwlwifi: mvm: Fix response handling in iwl_mvm_send_recovery_cmd()

In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: Fix response handling in iwl_mvm_send_recovery_cmd() 1. The size of the response packet is not validated. 2. The response buffer is not freed. Resolve these issues by switching to iwl_mvm_send_cmd_status(), which handles both size validation and frees the buffer.

Nov 19, 2024
CVSS7.1v3.1EPSS0.398%PoCs0SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT

In the Linux kernel, the following vulnerability has been resolved: net/sched: stop qdisc_tree_reduce_backlog on TC_H_ROOT In qdisc_tree_reduce_backlog, Qdiscs with major handle ffff: are assumed to be either root or ingress. This assumption is bogus since it's valid to create egress qdiscs with major handle ffff: Budimir Markovic found that for qdiscs like DRR that maintain an active class list, it will cause a UAF with a dangling class pointer. In 066a3b5b2346, the concern was to avoid iter

CWE-416Nov 19, 2024
CVSS7.8v3.1EPSS0.292%PoCs0SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

HID: core: zero-initialize the report buffer

In the Linux kernel, the following vulnerability has been resolved: HID: core: zero-initialize the report buffer Since the report buffer is used by all kinds of drivers in various ways, let's zero-initialize it during allocation to make sure that it can't be ever used to leak kernel memory via specially-crafted report.

CWE-908Nov 19, 2024
CVSS5.5v3.1EPSS0.809%PoCs0SignalsListed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

security/keys: fix slab-out-of-bounds in key_task_permission

In the Linux kernel, the following vulnerability has been resolved: security/keys: fix slab-out-of-bounds in key_task_permission KASAN reports an out of bounds read: BUG: KASAN: slab-out-of-bounds in __kuid_val include/linux/uidgid.h:36 BUG: KASAN: slab-out-of-bounds in uid_eq include/linux/uidgid.h:63 [inline] BUG: KASAN: slab-out-of-bounds in key_task_permission+0x394/0x410 security/keys/permission.c:54 Read of size 4 at addr ffff88813c3ab618 by task stress-ng/4362 CPU: 2 PID: 4362 Comm: st

CWE-125Nov 19, 2024
CVSS7.8v3.1EPSS0.282%PoCs0SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

sctp: properly validate chunk size in sctp_sf_ootb()

In the Linux kernel, the following vulnerability has been resolved: sctp: properly validate chunk size in sctp_sf_ootb() A size validation fix similar to that in Commit 50619dbf8db7 ("sctp: add size validation when walking chunks") is also required in sctp_sf_ootb() to address a crash reported by syzbot: BUG: KMSAN: uninit-value in sctp_sf_ootb+0x7f5/0xce0 net/sctp/sm_statefuns.c:3712 sctp_sf_ootb+0x7f5/0xce0 net/sctp/sm_statefuns.c:3712 sctp_do_sm+0x181/0x93d0 net/sctp/sm_sideeffect.c:

CWE-908Nov 19, 2024
CVSS8.2v3.1EPSS0.622%PoCs0SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

bpf: Fix out-of-bounds write in trie_get_next_key()

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix out-of-bounds write in trie_get_next_key() trie_get_next_key() allocates a node stack with size trie->max_prefixlen, while it writes (trie->max_prefixlen + 1) nodes to the stack when it has full paths from the root to leaves. For example, consider a trie with max_prefixlen is 8, and the nodes with key 0x00/0, 0x00/1, 0x00/2, ... 0x00/8 inserted. Subsequent calls to trie_get_next_key with _key with .prefixlen = 8 make

CWE-787Nov 9, 2024
CVSS7.8v3.1EPSS0.267%PoCs0SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

netfilter: nft_payload: sanitize offset and length before calling skb_checksum()

In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_payload: sanitize offset and length before calling skb_checksum() If access to offset + length is larger than the skbuff length, then skb_checksum() triggers BUG_ON(). skb_checksum() internally subtracts the length parameter while iterating over skbuff, BUG_ON(len) at the end of it checks that the expected length to be included in the checksum calculation is fully consumed.

Nov 9, 2024
CVSS6.2v3.1EPSS0.529%PoCs1SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

net: phy: dp83869: fix memory corruption when enabling fiber

In the Linux kernel, the following vulnerability has been resolved: net: phy: dp83869: fix memory corruption when enabling fiber When configuring the fiber port, the DP83869 PHY driver incorrectly calls linkmode_set_bit() with a bit mask (1 << 10) rather than a bit number (10). This corrupts some other memory location -- in case of arm64 the priv pointer in the same structure. Since the advertising flags are updated from supported at the end of the function the incorrect line isn't needed at

Nov 8, 2024
CVSS7.8v3.1EPSS0.225%PoCs0SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

RDMA/mad: Improve handling of timed out WRs of mad agent

In the Linux kernel, the following vulnerability has been resolved: RDMA/mad: Improve handling of timed out WRs of mad agent Current timeout handler of mad agent acquires/releases mad_agent_priv lock for every timed out WRs. This causes heavy locking contention when higher no. of WRs are to be handled inside timeout handler. This leads to softlockup with below trace in some use cases where rdma-cm path is used to establish connection between peer nodes Trace: ----- BUG: soft lockup - CPU#4

Nov 5, 2024
CVSS7.5v3.1EPSS0.74%PoCs0SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

NFSv4: Prevent NULL-pointer dereference in nfs42_complete_copies()

In the Linux kernel, the following vulnerability has been resolved: NFSv4: Prevent NULL-pointer dereference in nfs42_complete_copies() On the node of an NFS client, some files saved in the mountpoint of the NFS server were copied to another location of the same NFS server. Accidentally, the nfs42_complete_copies() got a NULL-pointer dereference crash with the following syslog: [232064.838881] NFSv4: state recovery failed for open file nfs/pvc-12b5200d-cd0f-46a3-b9f0-af8f4fe0ef64.qcow2, error

CWE-476Oct 21, 2024
CVSS9.8v3.1EPSS0.58%PoCs0SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

netfilter: br_netfilter: fix panic with metadata_dst skb

In the Linux kernel, the following vulnerability has been resolved: netfilter: br_netfilter: fix panic with metadata_dst skb Fix a kernel panic in the br_netfilter module when sending untagged traffic via a VxLAN device. This happens during the check for fragmentation in br_nf_dev_queue_xmit. It is dependent on: 1) the br_netfilter module being loaded; 2) net.bridge.bridge-nf-call-iptables set to 1; 3) a bridge with a VxLAN (single-vxlan-device) netdevice as a bridge port; 4) untagged frames

CWE-476Oct 21, 2024
CVSS7.5v3.1EPSS0.609%PoCs0SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: FIX possible deadlock in rfcomm_sk_state_change rfcomm_sk_state_change attempts to use sock_lock so it must never be called with it locked but rfcomm_sock_ioctl always attempt to lock it causing the following trace: ====================================================== WARNING: possible circular locking dependency detected 6.8.0-syzkaller-08951-gfe46a7dd189e #0 Not tainted ---------------------------------

CWE-667Oct 21, 2024
CVSS3.3v3.1EPSS0.187%PoCs0SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

igb: Do not bring the device up after non-fatal error

In the Linux kernel, the following vulnerability has been resolved: igb: Do not bring the device up after non-fatal error Commit 004d25060c78 ("igb: Fix igb_down hung on surprise removal") changed igb_io_error_detected() to ignore non-fatal pcie errors in order to avoid hung task that can happen when igb_down() is called multiple times. This caused an issue when processing transient non-fatal errors. igb_io_resume(), which is called after igb_io_error_detected(), assumes that device is brought

Oct 21, 2024
CVSS5.5v3.1EPSS0.258%PoCs0SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

net/sched: accept TCA_STAB only for root qdisc

In the Linux kernel, the following vulnerability has been resolved: net/sched: accept TCA_STAB only for root qdisc Most qdiscs maintain their backlog using qdisc_pkt_len(skb) on the assumption it is invariant between the enqueue() and dequeue() handlers. Unfortunately syzbot can crash a host rather easily using a TBF + SFQ combination, with an STAB on SFQ [1] We can't support TCA_STAB on arbitrary level, this would require to maintain per-qdisc storage. [1] [ 88.796496] BUG: kernel NULL p

CWE-476Oct 21, 2024
CVSS7.8v3.1EPSS0.254%PoCs0SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

ppp: fix ppp_async_encode() illegal access

In the Linux kernel, the following vulnerability has been resolved: ppp: fix ppp_async_encode() illegal access syzbot reported an issue in ppp_async_encode() [1] In this case, pppoe_sendmsg() is called with a zero size. Then ppp_async_encode() is called with an empty skb. BUG: KMSAN: uninit-value in ppp_async_encode drivers/net/ppp/ppp_async.c:545 [inline] BUG: KMSAN: uninit-value in ppp_async_push+0xb4f/0x2660 drivers/net/ppp/ppp_async.c:675 ppp_async_encode drivers/net/ppp/ppp_async.c:5

CWE-908Oct 21, 2024
CVSS7.1v3.1EPSS0.272%PoCs0SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

slip: make slhc_remember() more robust against malicious packets

In the Linux kernel, the following vulnerability has been resolved: slip: make slhc_remember() more robust against malicious packets syzbot found that slhc_remember() was missing checks against malicious packets [1]. slhc_remember() only checked the size of the packet was at least 20, which is not good enough. We need to make sure the packet includes the IPv4 and TCP header that are supposed to be carried. Add iph and th pointers to make the code more readable. [1] BUG: KMSAN: uninit-valu

CWE-908Oct 21, 2024
CVSS9.8v3.1EPSS0.785%PoCs0SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

ext4: dax: fix overflowing extents beyond inode size when partially writing

In the Linux kernel, the following vulnerability has been resolved: ext4: dax: fix overflowing extents beyond inode size when partially writing The dax_iomap_rw() does two things in each iteration: map written blocks and copy user data to blocks. If the process is killed by user(See signal handling in dax_iomap_iter()), the copied data will be returned and added on inode size, which means that the length of written extents may exceed the inode size, then fsck will fail. An example is given as:

Oct 21, 2024
CVSS5.5v3.1EPSS0.24%PoCs0SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_cmd_802_11_scan_ext()

In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_cmd_802_11_scan_ext() Replace one-element array with a flexible-array member in `struct host_cmd_ds_802_11_scan_ext`. With this, fix the following warning: elo 16 17:51:58 surfacebook kernel: ------------[ cut here ]------------ elo 16 17:51:58 surfacebook kernel: memcpy: detected field-spanning write (size 243) of single field "ext_scan->tlv_buffer" at driv

Oct 21, 2024
CVSS5.5v3.1EPSS0.247%PoCs0SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

ext4: fix i_data_sem unlock order in ext4_ind_migrate()

In the Linux kernel, the following vulnerability has been resolved: ext4: fix i_data_sem unlock order in ext4_ind_migrate() Fuzzing reports a possible deadlock in jbd2_log_wait_commit. This issue is triggered when an EXT4_IOC_MIGRATE ioctl is set to require synchronous updates because the file descriptor is opened with O_SYNC. This can lead to the jbd2_journal_stop() function calling jbd2_might_wait_for_commit(), potentially causing a deadlock if the EXT4_IOC_MIGRATE call races with a write(2

CWE-667Oct 21, 2024
CVSS4.7v3.1EPSS0.19%PoCs0SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

net/mlx5: Fix error path in multi-packet WQE transmit

In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Fix error path in multi-packet WQE transmit Remove the erroneous unmap in case no DMA mapping was established The multi-packet WQE transmit code attempts to obtain a DMA mapping for the skb. This could fail, e.g. under memory pressure, when the IOMMU driver just can't allocate more memory for page tables. While the code tries to handle this in the path below the err_unmap label it erroneously unmaps one entry from t

CWE-755Oct 21, 2024
CVSS7.8v3.1EPSS0.327%PoCs0SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX

net: ethernet: lantiq_etop: fix memory disclosure

In the Linux kernel, the following vulnerability has been resolved: net: ethernet: lantiq_etop: fix memory disclosure When applying padding, the buffer is not zeroed, which results in memory disclosure. The mentioned data is observed on the wire. This patch uses skb_put_padto() to pad Ethernet frames properly. The mentioned function zeroes the expanded buffer. In case the packet cannot be padded it is silently dropped. Statistics are also not incremented. This driver does not support statisti

CWE-212Oct 21, 2024
CVSS7.5v3.1EPSS1.06%PoCs0SignalsNot listed in CISA KEVNo known ransomware useNo Nuclei templatesSTIX